SAP Sales and Financial Process Management

The source provides an in-depth guide to configuring various organizational structures and master data within the SAP system, primarily focusing on Sales and Distribution (SD) and related Financial Accounting (FI) aspects. It meticulously outlines the creation and assignment of key entities such as companies, company codes, plants, sales organizations, sales offices, distribution channels, and divisions. Furthermore, the text explains the process for establishing financial variants like fiscal year and posting period variants, alongside chart of accounts and field status variants, crucial for financial reporting. Finally, it elaborates on master data creation, including material master and customer master, and details the Order-to-Cash (O2C) process with its pre-sales activities, sales order creation, and delivery procedures, illustrating each step with transaction codes and menu paths.

Navigating and Understanding SAP Access

SAP access refers to how users interact with and navigate the SAP system.

Here are some key aspects of SAP access:

• SAP Easy Access Screen: This is the main screen users see upon logging into SAP. It offers various options for navigation, allowing users to access different functionalities.
• No Free Version for Practice: SAP does not provide a free version for practice sessions. To practice SAP, users need to purchase an SAP license, even for educational purposes. This requires an ID and password to log in.
• Components of the SAP Screen: The main SAP screen typically includes:
• Menu Bar: Located at the top, it contains options like Menu, Edit, Favorites, Extras, System, and Help.
• Command Box: This is a crucial element where users can enter transaction codes (T-codes) to execute specific commands or navigate directly to a process. SAP uses a coding language, and commands are filled into this box.
• Favorites: Options to save frequently used transactions or paths for quick access.
• Integrated Site/Menu: This provides a structured way to navigate through different SAP modules and functionalities.
• Navigation Options: Beyond the command box, there are options for saving, backing up, logging off, closing windows, printing, searching (Find, Find Next), and navigating between pages (first, second, previous, next, last page). Users can also add windows.
• Navigation Methods:
• Transaction Codes (T-codes): These are specific codes (e.g., OX15 for company creation, OX02 for company code creation) that can be entered directly into the command box. This is often a quicker way to access specific functions. When a T-code is entered, SAP executes the command and takes the user to the corresponding process. If moving from one screen to another within SAP, a “slash n” (Slush N) prefix is often used before the T-code (e.g., Slush N OX02).
• Easy Access Path (Menu Path): Users can navigate through a hierarchical menu structure by opening various options to reach their desired function. For instance, to define a company, the path is Displaying Enterprise Structure > Definition > Financial Accounting > define company. This method is suitable for users who prefer not to use coding language or T-codes directly.
• Choosing a Method: Users can choose between using T-codes for time-saving or the SPRO (SAP Project Reference Object) path for a more guided, longer process.
• Organizational Structure and Access: The SAP Easy Access screen allows users to access and configure various organizational elements. For example, before starting SAP, defining the Company Creation (using T-code OX15 or the menu path) is a fundamental first step. Other organizational units like Company Codes, Plants, Sales Organizations, Distribution Channels, Sales Offices, Sales Groups, and Divisions are also configured through specific T-codes or menu paths accessed via the SAP screen.

SAP Company Creation: Defining the Enterprise Structure

In SAP, Company Creation is a fundamental step in setting up the organizational structure, particularly within the Sales and Distribution (SD) module.

Here’s a detailed discussion of Company Creation in SAP:

• Definition of a Company:
• A company represents a basic organization for which individual financial statements can be created to comply with relevant commercial law.
• It is considered for consolidating reporting.
• It is necessary to maintain for internal trading and intercompany transactions.
• A company can consist of one or more Company Codes.
• Transaction Code (T-code):
• The transaction code (T-code) to create a company in SAP is OX15.
• This T-code remains the same globally, regardless of the country.
• To use a T-code, you enter it into the command box on the SAP Easy Access screen. SAP accepts and processes this command, taking the user directly to the relevant process. If navigating from one screen to another within SAP using a T-code, a “slash n” (/n) prefix is often used before the T-code (e.g., /nOX15).
• Menu Path (Easy Access Path):
• Alternatively, users can navigate to company creation through a hierarchical menu path, which is suitable for those who prefer not to use T-codes.
• The menu path for company creation is: SPRO (SAP Project Reference Object) > SAP Reference IMG > Enterprise Structure > Definition > Financial Accounting > Define Company.
• Choosing between the T-code and the SPRO path depends on whether a user prioritizes time-saving (T-code) or a more guided process (SPRO path).
• Process of Company Creation:

1. Upon reaching the company creation screen (either via OX15 or the menu path), users select “New Entries”.
2. The system will prompt for details for the new company.
3. A five-digit code must be mentioned for the company.
4. Users must provide the company name, street (location), PO Box (Post Office Box), postal code (PIN code), and city.
5. The country must be mentioned (e.g., IN for India). SAP provides options for countries by double-clicking on their codes.
6. The language (e.g., EN for English) and currency (e.g., INR for Indian Rupees for India) also need to be specified. These can be searched and selected by double-clicking.
7. After filling in all the details, the data must be saved. This can be done by clicking the save icon or using the shortcut Control + S.
8. Upon saving, a description for the request (e.g., “Company Creation”) is usually entered, confirming that the data has been saved and the main company has been created.

• Relationship to Company Code:
• The company is the overarching entity, and it consists of one or more company codes.
• Company codes represent independent balancing legal accounting entities and are used for external purposes by a company with independent accounts within a corporate group. They can be thought of as branches of the main company.
• After creating the company, the next step in the organizational structure setup is often Company Code Creation (T-code OX02).

SAP Financial Structure: Core Components & Configuration

In SAP, the Financial Structure refers to the foundational setup of an organization’s financial accounting elements, which are crucial for managing financial transactions and reporting. This structure is closely related to the Financial Accounting (FI) module and integrates with other modules like Sales and Distribution (SD).

A key concept underpinning much of the financial structure configuration in SAP is the Variant Principle. This principle involves a three-step method for creating and managing variants:

1. Define: Creating the variant itself through a specific code.
2. Determine Value: Specifying the values or properties within that variant.
3. Assign: Linking the variant to the relevant organizational object, such as a company code. The advantage of using variants is that it simplifies the maintenance of common properties across various business objects.

The core components of the financial structure, often configured using this variant principle, include:

• Company
• Company Code
• Fiscal Year Variant
• Posting Period Variant
• Chart of Accounts (COA)
• GL Account Groups
• Field Status Variant
• Retained Earnings Account

Let’s discuss each of these in detail:

1. Company

A company represents a basic organization for which individual financial statements can be created to comply with commercial law. It is considered for consolidating reporting and is necessary for maintaining internal trading and intercompany transactions. A single company can consist of one or more Company Codes.

• Transaction Code (T-code): OX15. This T-code is globally consistent.
• Menu Path: SPRO > SAP Reference IMG > Enterprise Structure > Definition > Financial Accounting > Define Company.
• Key Configuration Steps:

1. Select “New Entries” on the company creation screen.
2. Provide a five-digit code for the company.
3. Enter the company name, street, PO Box, postal code, city, country (e.g., IN for India), language (e.g., EN for English), and currency (e.g., INR for Indian Rupees).
4. Save the data, typically by entering a description for the request (e.g., “Company Creation”).

2. Company Code

A company code represents an independent balancing legal accounting entity. It is used for external purposes by a company with independent accounts within a corporate group. Company codes can be thought of as branches of the main company. Financial statements required by law can be created at the company code level.

• Transaction Code (T-code): OX02. When navigating from another SAP screen, use /nOX02.
• Menu Path: SPRO > Display IMG > ENTERPRISE STRUCTURE > Definition > Financial Accounting > Edit Delete Check Company code.
• Key Configuration Steps:

1. Select “New Entries”.
2. Mention a four-digit code for the company code.
3. Provide the company name, city, country, currency, and language.
4. Save the data. Upon saving, further address details such as title, search term, street, house number, postal code, region (e.g., 07 for Haryana, India), and PO box are requested.

• Assignment to Company: After creating the company code, it must be assigned to a company.
• T-code: OX16.
• Menu Path: SPRO > SAP Reference IMG > Enterprise Structure > Assignment > Financial Accounting > Assign Company Code to Company.
• Process: Use the “Position” function to find the company code and enter the main company’s five-digit code for assignment. Save the request.

3. Fiscal Year Variant

The fiscal year variant relates to the financial year and is identified by a two-digit alphanumeric key. It defines how the financial year is structured for a company code.

• Transaction Code (T-code): OB29.
• Menu Path: Display IMG > Financial Accounting > Financial Counting Global Settings > Ledgers > Financial year end posting period > Maintained Physical Year Variants.
• Types of Fiscal Year:
• Year Independent: The number and dates for periods are the same every year (e.g., April 1st to March 31st in India). It can also be defined as a calendar year (January to December). Non-calendar year setups use +1 and -1 indicators for year shifts.
• Year Specific: Periods can vary from year to year, meaning the start and end dates of posting periods are not fixed.
• Key Configuration Steps (Three-Step Method):

1. Define Variant (OB29): Select “New Entry”. Provide a two-digit code and description (e.g., “April to March”). Specify if it’s a “Calendar year” or “Year Dependent”. Set the “Number of posting periods” (e.g., 12 for months) and “Number of special periods” (e.g., 4 for auditing purposes in India). Save.
2. Determine Value (Periods): Select the newly created variant and click “Periods”. Here, define each period by filling in the month, day, period number, and year shift (e.g., -1 for months like Jan-Mar that fall into the previous year for a fiscal year starting April 1st). Save.
3. Assign (Company Code to Fiscal Year Variant – OB37):

• T-code: OB37.
• Process: Use “Position” to find your company code and then enter the fiscal year variant code you created. Save the assignment.

4. Posting Period Variant

The posting period variant is denoted by a four-digit alphanumeric key. It controls which accounting periods are open for posting.

• T-code (Define Variant): OBBO.
• T-code (Define Open & Close Posting Period): OB52.
• T-code (Assign): OBBP.
• Key Configuration Steps (Three-Step Method):

1. Define Variant (OBBO): Select “New Entry”. Provide a four-digit code and a description (e.g., “Posting Period For Toyo”). Save.
2. Define Open & Close Posting Period (OB52): Enter the posting period variant code. Select “New Entry”. Specify the “Account” range (e.g., ‘+’ for all accounts, or specific account types like ‘A’ for assets, ‘D’ for customers, ‘K’ for vendors, ‘M’ for material, ‘S’ for GL Accounts). Define “From Period 1” (e.g., 1) and “To Period” (e.g., 12) with their respective years. For special periods, specify “From Period 2” (e.g., 13) and “To Period” (e.g., 16) with their year. Save.
3. Assign (Company Code to Posting Period Variant – OBBP):

• T-code: OBBP.
• Process: Use “Position” to find your company code and enter the posting period variant code. Save the assignment.

5. Chart of Accounts (COA)

The Chart of Accounts (COA) is the highest level of hierarchy for all journal accounts. It provides a structured list of all G/L (General Ledger) accounts used by one or more company codes to record financial transactions. A company might want one operative chart of accounts common across all company codes and country-specific charts of accounts for reporting.

• T-code (Create COA): OB13.
• T-code (Assign Company Code to COA): OB62.
• Menu Path (Create COA): Display IMG > Financial Accounting > General Ledger Accounting > Master Data > General Ledger Accounts > Preparations > Edit Chart of Accounts List.
• Menu Path (Assign Company Code to COA): Display IMG > Financial Accounting > General Ledger Accounting > Master Data > General Ledger Accounts > Preparations > Assign Company Code to Chart of Accounts.
• Types of Chart of Accounts:
• Operating Chart of Accounts: The main chart of accounts.
• Group Chart of Accounts: Used by multiple company codes for consolidated reporting.
• Country Chart of Account: Country-specific chart of accounts, used only once.
• Key Configuration Steps (Three-Step Method):

1. Create Variant (OB13): Select “New Entry”. Provide a four-character code for the COA and a description. Specify the language (e.g., English) and the length of the G/L account number (e.g., 6 digits). You can also mention a group code if creating account groups. Save.
2. Assign (Company Code to Chart of Accounts – OB62):

• T-code: OB62.
• Process: Use “Position” to find your company code and enter the COA code you just created. Save.

6. GL Account Groups

General Ledger Account Groups are created within the Chart of Accounts to organize G/L accounts based on their nature (e.g., assets, liabilities, expenses, revenues). These groups define the number range for the accounts and control the field status for G/L master data.

• T-code: OBD4.
• Menu Path: Display IMG > Financial Accounting > General Ledger Accounting > Master Data > General Ledger Accounts > Preparations > Define Account Group.
• Key Configuration Steps:

1. Select “New Entry”.
2. Specify the Chart of Account (the one created earlier).
3. Provide a four-digit Account Group code (e.g., for Assets, Liabilities, Expense, Revenue).
4. Enter a complete description for the account group.
5. Define the number range (“From Account” to “To Account”) for the accounts within this group, ensuring that number ranges do not overlap with other groups.
6. Repeat the process for all necessary account groups (e.g., Assets, Liabilities, Expenses, Revenue). Save.

7. Field Status Variant

The field status variant controls the fields of transactions at a line item level. It dictates whether a field is suppressed (hidden), displayed, required (mandatory entry), or optional for entry. If a field status variant is not maintained, all fields will be hidden by default.

• T-code (Define Field Status Variant): OBC4.
• T-code (Assign Company Code to Field Status Variant): OBC5.
• Menu Path (Define Field Status Variant): Display IMG > Financial Accounting > Financial Accounting Global Settings > Ledgers > Field > Define Field Status Variants.
• Menu Path (Assign Company Code to Field Status Variant): Display IMG > Financial Accounting > Financial Accounting Global Settings > Ledgers > Field > Assign Company Code to Field Status Variant.
• Key Configuration Steps (Three-Step Method):

1. Define Variant (OBC4): SAP provides predefined field status groups, which can be copied. It is common to copy the ‘0001’ variant (for General Ledger). Use “Position” to find ‘0001’, select it, and click “Copy”. Enter a new four-digit alphanumeric key (e.g., ‘TOYO’) and description for your variant. Choose “Copy All” to copy all associated entries (e.g., 46 or 47 entries). Save.
2. Determine Value (Field Status Groups): Select your newly created variant. Click “Field Status Groups”. Select ‘G001’ (General Ledger). Go to “Field Status” and adjust the settings for different field categories (e.g., General Data, Assignments, Payment Transactions) from suppressed to optional or required as per business needs. Save.
3. Assign (Company Code to Field Status Variant – OBC5):

• T-code: OBC5.
• Process: Use “Position” to find your company code and enter the field status variant code. Save the assignment.

8. Retained Earnings Account

The Retained Earnings Account is a profit and loss statement account where the balance is carried forward during year-end closing to calculate the company’s result and set the profit and loss statement to zero. It is created as a liability side of the balance sheet and is reported in the shareholders’ equity section. A plus key is typically assigned to the account to facilitate balance sheet carry-forward.

• T-code: OB53.
• Menu Path: Display IMG > Financial Accounting > General Ledger Accounting > Master Data > General Ledger Accounts > Preparations > Define Retained Earnings Account.
• Key Configuration Steps:

1. Enter the Chart of Account.
2. For the profit and loss statement, typically enter a star (‘*’).
3. Enter an account number (e.g., 1 lakh) for the retained earnings account.
4. Save the changes.

These components together form the bedrock of the financial structure in SAP, enabling accurate financial record-keeping, reporting, and integration across various business processes.

SAP Sales and Distribution: Order to Cash Process

The Sales Process in SAP, often referred to as the Order to Cash (O2C) process, encompasses the entire sales cycle from the initial customer order to the receipt of cash. This process is managed within the SAP Sales and Distribution (SD) module. The SD module focuses on maintaining proper relationships with customers and managing the sale, shipping, billing, and transportation of a company’s products and services.

The O2C sales cycle typically involves several key steps:

• Pre-sales Activities:
• Inquiry: This is the first step where a customer asks about material availability, price, quantity, expiry dates, or seeks a quotation.
• Purpose: To gather information from the customer’s initial interest.
• Transaction Code (T-code): VA11 is used to create an inquiry.
• Process: When creating an inquiry, you specify the inquiry type (e.g., IN for Inquiry), sales organization, distribution channel, division, sales office, sold-to party (customer), customer reference, validity period (Valid From/To), material, and quantity.
• Management: Inquiries can be displayed using T-code VA13, changed with VA12, and a report of inquiries can be checked using VA15. The VA15 report can also be used to check for expired inquiries by specifying the validity period.
• Quotation: After an inquiry, a quotation is prepared to provide the customer with details like material, quantity, price, quality, and delivery dates, making them ready for a deal.
• Purpose: To formalize the proposed terms of sale based on the inquiry.
• T-code: VA21 is used to create a quotation.
• Process: Similar to inquiries, creating a quotation involves mentioning the quotation type (e.g., QT), customer details, reference, valid to date, material, and order quantity.
• Management: Quotations can be edited or changed using VA22, displayed with VA23, and a report of prepared quotations can be viewed via VA25. Changes made to a quotation can be tracked by selecting the quotation, going to “Environment,” then “Changes” to view old versus new values.
• Sales Order Creation:
• Purpose: Once the customer is satisfied with the quotation, a sales order is created to confirm the specific materials, quantities, and required delivery dates.
• T-code: VA01 is used to create a sales order.
• Order Types: Different order types exist, such as ST (Sales Order), OR (Standard Order), and RO (Rush Order).
• Process: Details like sold-to party, customer references, delivery plant, material, and ordered quantity are entered. The system might show errors if item categories are not properly assigned, which can be resolved by assigning the appropriate item category (e.g., OR1 for standard orders).
• Management: Sales orders can be changed using VA02 and displayed using VA03.
• Rush Order: A special type of sales order where creating it automatically triggers both the delivery and the invoice in the background. This process requires an Immediate Shipping Point.
• Availability Check:
• This step confirms if the requested products are available in stock. The source notes that delivery cannot proceed if stock is unavailable. If stock is unavailable, the production team might be contacted to prepare the product, or vendors might be contacted if raw material is not available.
• Delivery:
• Purpose: After the sales order is created and availability is confirmed, the delivery process starts, which involves shipping the goods to the customer.
• T-code: VL01 is used to create a delivery.
• Process: Requires specifying the shipping point, selection date, and the sales order number.
• Billing/Invoice:
• Purpose: The final step in the sales cycle where an invoice is generated and sent to the customer for payment.
• T-code: VF01 is used to create an invoice.
• Process: Details include the billing type (e.g., related to delivery), billing date, pricing date, and the document number from the delivery. An invoice cannot be created if stock was unavailable for delivery.

Key Concepts and Organizational Elements in the Sales Process:

• Customer: A person or organization that purchases goods and services in exchange for money or other value.
• Creation: T-code XD01. Involves entering general data (address, contact, identification), control data, payment transactions, and sales & distribution data (sales organization, distribution channel, division, sales district, customer group, sales office, shipping conditions, delivery priority, plant, billing terms, pricing group, accounting assessment group).
• Management: XD02 for changes, XD03 for display.
• Material Master: The central source of material-specific data in SAP, essential for SD operations as it integrates with modules like SD, MM, PP, and FI. It affects the delivery process and pricing.
• Creation: MM01. Involves specifying material type (e.g., ROH for raw, HALB for semi-finished, FERT for finished), material group, and other organizational data like plant and sales organization.
• Management: MM02 for changes, MM03 for display.
• Sales Organization: Groups a company according to its sales and distribution requirements.
• Purpose: Main responsibilities include selling and distributing services and materials. Can be national or regional.
• Creation: T-code OVX5.
• Assignment: Needs to be assigned to the company code (T-code OVX3).
• Distribution Channel: Represents the shipping strategy for distributing products and services. A single sales organization can have multiple distribution channels (e.g., wholesale, retail, internet trade).
• Creation: T-code OVX1.
• Assignment: Needs to be assigned to the sales organization (T-code OVXK).
• Division: Represents a product line (e.g., mobile, laptop).
• Creation: T-code OVXB.
• Assignment: Needs to be assigned to the sales organization (T-code OVXA).
• Sales Area: A combination of the sales organization, distribution channel, and division. It can only be created after these three elements are established.
• Creation: T-code OVXG.
• Assignment: Can be assigned to a sales office (T-code OVXM).
• Sales Office: Set up apart from headquarters to reach the market in depth. Sales reporting can be executed with this organizational unit to analyze performance.
• Creation: T-code OVX1.
• Sales Group: Employees belonging to a certain sales office can be referred to as a sales group. It is a subset of the sales office and is assigned to its respective sales office.
• Creation: T-code OVX4.
• Shipping Point: A location within a plant where goods are loaded or unloaded for dispatch to customers or receipt from vendors.
• Types: Manual (requires labor for loading/unloading, e.g., luxury items), Automatic (uses machines for heavy products), and Immediate (for urgent delivery requirements like medicines or military supplies).
• Creation: T-code OVL2.
• Determination: OVL2 is also used for shipping point determination, requiring shipping conditions, loading group, and plant code.
• Storage Location: A physical location within a plant where goods (semi-finished, finished, or raw material) are stored.
• Creation: T-code OX092.

SAP Material Management: Master Data and Operations

Material Management (MM) in SAP is a crucial module that integrates closely with other SAP modules like Sales and Distribution (SD), Production Planning (PP), and Financial Accounting (FI). It is central to managing material-specific data and affects various logistics processes, including delivery and pricing. The sources emphasize that Material Management is a key aspect of the “Order to Cash (O2C)” process within SAP SD, as it involves the creation and management of materials that are sold to customers.

The discussion of Material Management primarily revolves around three essential concepts: Material Type, Material Group, and Material Master Creation.

Here’s a breakdown of Material Management concepts as described in the sources:

• Material Master (Creation, Change, Display):
• The Material Master is the central source of material-specific data in SAP.
• It is essential for SD operations as it integrates with multiple modules such as SD, MM, PP, & FI.
• Not maintaining the sales organization and plant properly during material master creation can significantly impact the delivery and pricing processes. Therefore, sales organization data and plant organization data need to be integrated.
• Creation T-code: MM01.
• The process involves selecting industry type, material type, and ticking the organization level in default settings to ensure integration with sales organization, storage location, plant, and distribution channel.
• Details such as material description (e.g., “Plastic bottle”), unit (e.g., “pieces”), material group (e.g., “plastic”), division, gross weight, and net weight are entered.
• Further views like Basic Data One, Basic Data Two, Classification, Sales Organization Data One, Sales Organizational Data Two, Sales General/Plant Data, Purchasing, and MRP are selected and details like item category group and MRP type (e.g., PD for MRP) are filled.
• Change T-code: MM02. This allows users to make changes to existing material master data.
• Display T-code: MM03. This allows users to view material master details but no changes can be made, as the screen appears blurred for editing.
• Material Type:
• Definition: Material Type is a classification of material based on its business use. It categorizes material based on its characteristics and purpose.
• Control: It controls views, number ranges, valuation class, price control, etc., and is defined at the configuration level.
• Types: The sources identify three main types of materials:
• Raw Material (ROH): Material that includes only raw components, used to first prepare semi-finished products, then finished products (e.g., milk, flour, sugar for biscuits).
• Semi-finished Material (HALB): Partially processed material (half raw, half cooked) that needs further conversion to become finished (e.g., a powder containing mixed ingredients for biscuits).
• Finished Material (FERT): Directly created/ripe product that only requires packing and can then be sold (e.g., baked biscuits).
• Creation T-code: OMS2.
• The process involves searching for existing material types (e.g., ROH for raw material), selecting it, and copying it to create a new personal code (e.g., “RAW1”) with a description (e.g., “Raw material for Toyo”).
• After creation, the “Quantity and Value Updating” for all valuation areas must be activated for the material type. This can be done by selecting the material type, clicking on “Quantity and Value Updating,” and activating all valuation areas, then saving. The same process is followed for Semi-finished (HALB) and Finished (FERT) material types.
• Material Group:
• Definition: Used to group together items with similar attributes, such as all metals or different grades of plastic. It allows for the creation of many different materials from a single group (e.g., plastic can be used for toys, chairs, tables; iron for pipes, boxes, plates; steel for utensils, pipes, plates).
• Creation T-code: OMSF.
• The process involves going to “New Entries,” providing a four-digit code (e.g., “1234”), a material group description (e.g., “Plastic”), and a description to K (e.g., “Plastic”), then saving. Multiple material groups can be created following this process.

Beyond the core material creation, other organizational elements are crucial for managing materials:

• Storage Location:
• Definition: A physical location within a plant where goods are stored. This can include semi-finished, finished, or raw materials. It is essentially a warehouse for storing goods.
• Creation T-code: OX092.
• Creating a storage location requires entering the plant code, a four-digit code for the storage location, and a description (e.g., “Storage location”).
• Shipping Point:
• Definition: A location within a plant where goods are loaded or unloaded for dispatch to customers or receipt from vendors.
• Types:
• Manual Shipping Point: Requires labor for loading and unloading (e.g., luxury items, glass products).
• Automatic Shipping Point: Uses machines for loading and unloading (e.g., heavy products).
• Immediate Shipping Point: For urgent delivery requirements, where delivery needs to be done very quickly (e.g., medicines, military supplies). Creating a Rush Order automatically triggers delivery and invoice in the background and requires an Immediate Shipping Point.
• Creation T-code: OVL2.
• Shipping point determination requires specifying shipping conditions (e.g., “001” for standard), loading group (e.g., “01”), and the plant code.

By Amjad Izhar
Contact: amjad.izhar@gmail.com
https://amjadizhar.blog

Affiliate Disclosure: This blog may contain affiliate links, which means I may earn a small commission if you click on the link and make a purchase. This comes at no additional cost to you. I only recommend products or services that I believe will add value to my readers. Your support helps keep this blog running and allows me to continue providing you with quality content. Thank you for your support!