A Rare Guide To SAP SD

A
Rare Guide to SAP SD & Basic IS-Oil

Knowing the rare

Faizullah Khan
Table of Contents
SAP Methodology
ASAP Methodology of Project Implementation
SAP Project Management Reports
SD Configuration
Business Blueprint Document
SD Configuration Template
Fields in Customer Master
Pricing in SAP SD
SD Shipping and Transportation
SD Configuration Smmarised
Cross Modular Configuration
SD Batch Management
Sales and Operation Planning [SOP]
Sales and Operation [SOP] Configuration
Testing and Training
SAP UAT Template
Cut over Plan
SAP Training Development
SAP Training Module
Sales Information System
Sales Information System SIS Setup
Standard SD Reports
SAP Configuration Template
SD Month End Closing
SAP SD Transaction Codes
Entering SAP Community
SAP Consulting Skills
SD Interview Tips
SD Certification
Recommended Books
SAP IS OIL
Oil and Gas Industry
IS Oil TD Master Data
TSW Overview
TSW Master Data
TSW Nomination
Silo Management
User Exits in IS Oil
SAP IS Oil Configuration
IS Oil Transaction Codes
IS OIL Training Resource Plan
Appendix
1. MM Purchasing Organisational Structure
2. MM Purchasing Configuration
3. SAP Physical Inventory
4. WM Organisational Hierarchy
5. Third Party Order Processing
SAP Methodology
ASAP Methodology of Project Implementation
SAP recommends that you use ASAP as a standard methodology for implementation
planning and for implementing SAP software. The ASAP Roadmap provides a step-bystep guide to implementation. During the five phases of an ASAP project, the results of
each phase are recorded in specific documents. This is particularly important in Phase
2. The ASAP Roadmap is infact Accelerated SAP Roadmap consisting of 5 phases.

Phase 1: Project Preparation

The primary focus of Phase 1 is getting the project started, identifying team members and
developing a high-level plan. The formation of a Project steering committee consisting of
members from both the SAP Client and the SAP Implementation Team or Consulting
Companys team performed during this phase.

Phase 2: Business Blueprint

The primary focus of Phase 2 is to understand the business goals of the enterprise and to
determine the business requirements needed to support these goals. A detailed document
called the Business Blueprint document consisting of both the AS IS situation of the
Client Business processes and the proposed TO BE mapping in the SAP system is
documented in this document. The document is duly signed by the Clients Business
Processes Owners [BPO].

Phase 3: Realization

The purpose of this phase is to implement all the business and process requirements
identified in the Business Blueprint. You configure the system step-by-step in the Baseline
Configuration and Final Configuration.

Phase 4: Final Preparation

The purpose of this phase is to complete testing, end-user training, system management
and cutover activities. Critical open issues are resolved. When you have successfully
completed this phase, you will be ready to run your business in your production system.

Phase 5: Go Live and Support

Transition from a project-oriented, pre-production environment to a successful and live
production environment.
Details of SAP Project using ASAP Methodology

Once you become a part of an SAP implementation, you need to know precisely the
milestones during each phase of the implementation as in most of the cases these
milestones have deadlines and are part of SAP team deliverables from the Client side
failing which the project schedule is disturbed due to a war of nerves during the project.

Phase 1: Project Preparation
During this phase, our team will prepare and conduct a project kick-off meeting with the
Project
Team of Client. We will execute an initial project planning and preparation for the ERP
implementation.

Milestones:

Project Planning

Project Kick-off

Software Installation

Quality Check

Phase 2: Business Blueprint
During the second phase, our team will conduct a requirements workshop with various
key managers and officials of Client to define project objectives, scope, and schedule. In
addition, the relevant business process scenarios will be defined. In order to document the
results gathered during the business requirement workshops, we will create a Business
Blueprint (Implementation Document). It is the Client responsibility to give written
feedback and schedule workshops on BBP. If the Client does not respond within 10 days
of BBP submission, it shall be then considered as approved. Any changes from the
approved BBP shall be charged as per the agreed customization rate.

Milestones:

Gather Business Requirements

.Collect Configuration Needs

Collect Reporting Requirements

Business Blueprint

Phase 3: Project Realization
In the third phase, our team will implement all business process requirements of client
based on the Business Blueprint. Other key focal areas of this phase will include
conducting all integration tests and drawing up end user documentation. It is Client
responsibility to provide all relevant Master Data in prescribed form on the date
mutually agreed in the project plan. Any deviation/delay in hand over of Master Data will
be charged at as per agreed customization rate. Client shall be responsible for Data
Cleansing and Preparation Activity.

Milestones:

Validate Business Requirements

Implementation of Business Requirements

Integration & Acceptance Testing

Plan End User Training

Phase 4: Final Preparation

In the fourth phase of implementation, we will complete the preparation (including user &

Administrator training, system management and cutover activities) to finalize go-live
readiness.

Milestones:

Administrator & User Training

Final Preparation

Execute Cutover

Resolve Critical Issues

Phase 5: Go-Live and Support

During the last phase, our team will finalize the project from a pre-production
environment to live operation. Go-Live means day on which first transaction is added into
the system. The most important elements of this phase will include setting up system
support, monitoring system transactions and optimizing overall system performance.
Milestones:

Go-Live

Support Operation

Handover Administration

Support Plan

SAP Project Management Reports

I had the opportunity of reading stuff on SAP Project Management Reports when I became
the team lead for an implementation. I found the material important and added with it
my practical SAP experience. This helped me to execute the module reporting efficiently.
The following is the crux of my SAP experience briefly.
SAP Project Management Reports consists of a set of reports and of the deliverables that
are submitted to the SAP client on behalf of the team. It consists of Periodic reports w.r.t.
the Project Deliverables and the final report.

Periodic Reports

Periodic reports are required and must be submitted at the end of each reporting period.
These reports contains:

1- An overview of the activities carried out during the reporting period related to SAP
implementation,
2- Describes the progress w.r.t project objectives,
3- The progress towards the milestones [Accelerated SAP Roadmap- also called ASAP
Roadmap in SAP Project],
4- Deliverables set for the period and
5- Executive summary.

The frequently submitted reports or periodic management reports also include:

1- A detailed justification of the costs incurred and of the
2- Resources deployed by each contractor linking them to activities implemented and
justification of their necessity in the project,
3- The financial statements from each contractor and
4- A summary financial report consolidating the costs of the contractors.
5- Schedule of deliverables has to be submitted to the Client. They are approved normally
with the periodic reviews of project progress.

Final Report

The Project manager has to submit the final report to the SAP Client after the end of the
project. The final report summarises the projects activities during its full duration. A final
activity report, covers main aspects of the work, objectives, results and results of final plan
according to the ASAP Roadmap for using and disseminating the knowledge.

Executive Summary

Executive summary is normally a separate document but submitted with the final report;
it is normally not more than four to five pages and has quality to enable direct publication
by the Client. It should include

1-a summary description of project objectives,
2-contractors involved,
3-co-ordinator contact details,
4-jobs performed,
5-results achieved so far and expected end results,
6- Knowledge Transfer Details.

You need to include if available diagrams or photos illustrating the work of the project, a
project logo and a reference to the project public website.

SD Configuration
Business Blueprint Document
The following is the structure of a practical Business Blueprint Document. You can copy
paste it into the document template of your Business Blueprint document and just enter the
date. It will give you a professional Business Blueprint document that just needs to be
signed by the Client.

Module Name:

Release:

Prepared By:

Date:

1. Blueprint Agreement

Signing this document records your agreement to the contents of the Blueprint, and
confirms that the remaining project can proceed.
Name

Position

Date

Signature

2. Legend

The following describes the symbols used in the process map:

High-level process activity.

Decision

Activity step

Document

System

Continuation of the process map to a different page

3.1 Organisational Structure
Process Definition

Organization Element on SAP R/3

Organizational Element

Definition

Organization Structure Diagram in detail complete and full

Enclose your org structure diagram for Project

Process description

Configuration data in sap

Integration with other modules

Write sap enhancement if required
Master Data Maintenance

Master data For Project
Enclose a Diagram or Flow chart
Process description
Configuration data in SAP
SAP Enhancement
Enhancement if any required for Master Data
Enclosure of all Master data samples with Process Definition and with flow charts

Description
Process description


Business Process Overview
Enclose your TO BE Flow chart Complete
Process description

Flow Process
Process Definition
Please enclose your flow diagrams wherever required.
Process description
Write SAP enhancement if required
Explanation of second stage
Enclose all your flow chart s and description if you have any.
Process Description

Reporting Requirement
Write complete details of Reports to be submitted to Project

Authorisation and roles
Outstanding items
Enclose if any outstanding
SD Configuration Template
For those interested to know about the order and constituents of SAP SD Configuration
Steps in the Implementation Management Guide [IMG] of the Standard SAP, This is just a
quick Reference. If you are a new entrant into SAP or a junior consultant you will have to
refer to IMG a lot as each screen you see on the SAP System screen is configured and
controlled from the IMG. Moreover, this reference will help you know the practical
concepts helpful in configuring the SAP SD successfully. Just reading the standard
documentation from the Help portal of SAP [help.sap.com] is quite boring and needs a lot
of time.

Sales and Distribution

Master Data
Define Common Distribution Channels
Define Common Divisions
Business Partners

Customers
Customer Hierarchy

Define Hierarchy Types

Set Partner Determination for Hierarchy Categories

Assign Account Groups

Assign Sales Areas

Assign Hierarchy Type for Pricing by Sales Document Type

Marketing

Define Industry Sector for Customers

Define Customer Classifications

Project XYZ Configuration Guide

< Define Customer Classifications >

Specifies a classification of the customer (for example, classifies the customer as a bulk
purchaser).

Purpose

The classifications are freely definable according to the needs of your organization.

Purpose of the Configuration

To define customer classifications.

Type of Configuration

Master data

Prerequisites

N/A

Procedure

1) IMG -> Sales and Distribution -> Master data -> Business Partners->Customers->
Marketing -> Define customer classifications

2) Define customer classifications.

3) Maintain the Description.

4) Save.

Result

A new customer classification is created.

Example

A - A class customer.

Reference

Refer to SD BUSINESS BLUEPRINT

Define Nielsen ID

Define Industry Sector Codes

Define Legal Statuses

Sales

Define Customer Groups

Project Configuration Guide
< Define Customer group >

Identifies a particular group of customers (for example, wholesale or retail) for the
purpose of pricing or generating statistics.

Purpose

You can freely define customer groups according to the needs of your organization. You
assign a customer group to an individual customer either in the customer master record of
the sold-to-party or in the sales document. In SD Customizing, you can create a condition
type that lets you create pricing records for customer groups. Additionally, when you want
to generate sales statistics, you can use customer groups as one of the selection criteria.


To define customer groups.


Master data

Prerequisites

N/A

Procedure

1) IMG -> Sales and Distribution ->Master data -> Business Partners -> Customers ->
Sales -> Define customer groups

2) Define customer groups

3) Maintain the Description.

4) Save.

Result

A new customer group is created.

Example

HP Hospitals

Reference


Define Sales Districts

Project Configuration Guide

< Define Sales Districts >

Each customer can be assigned to a sales district. You can use sales districts to apply
pricing conditions. When you want to generate sales statistics, you can use sales districts
as selection criteria.

Purpose

To define Sales districts in sales view of the Customer master.


To define Sales district in sales view of the customer master.


Master Data

Prerequisites

None

Procedure

1) IMG -> Sales and Distribution ->Master Data -> Business Partners -> Customers ->
Sales -> Define Sales Districts

2) Define Sales Districts

3) Save.

Result

A new Sales district is created.

Example

00001 South London

Reference


Maintain Reserve Fields In Customer Master

Shipping

Define Delivery Priorities

Define Customer Calendars

Define Goods Receiving Hours

Billing Document

Define Billing Schedule
Define Terms of Payment

Define Incoterms

Contact Person
Define Standard Departments
Define Contact Person Functions

Define Decision Authorities

Define Call Frequency

Define Buying Habits

Define VIP Indicator
Define Attributes

Use Sales Employee without HR

Item Proposal
Define Item Proposal Types

Define Number Ranges for Item Proposals
Fields in Customer Master

Creating customised reports for a client is an essential part of any SAP implementation as
the Standard SD reports are usually not sufficient for mapping their business processes in
to the system. For SD implementation, the knowledge of certain master data helps in
giving the functional specifications of the reports to the ABAPers [programmers]. In the
Sales and Distribution Module, Customer Master is the main master data, along with
Condition Master, Credit Master and Sales Employee. The following is a list of important
field mapping of Customer Master along with their type [C or DYMD or CURR] and
length of each field as well as whether they are marked Mandatory in the IMG.
Customer Master
Field Name Description
Type Length Mandatory
KUNNR Customer No
C 10
KTOKD Customer Account Group C
4
COUNTRY Country Key
C 3
REGION Region C
3
TITLE_MEDI Title C
15
NAME1 Name 1 C
35
NAME2 Name 2 C
35
NAME3 Name 3 C
35
NAME4 Name 4 C
35
CITY1 City
C 35
PO_BOX P.O.Box. C
10
POST_CODE2 Postal code
C 10
SORT1 Search Term C
20
LANGU Language Key C
1
STREET Street
C 35
TEL_NUMBER First telephone number
C 16
FAX_NUMBER Fax number
CURR 31
HOUSE_NUM1 House number C 7
TEL_EXTENS Ext
CURR 10
FAX_EXTENS Ext Ext
CURR 10
SMTP_ADDR Email 1
C 53
REMARK Notes 1 C
53
SMTP_ADDR Email 2
C 53
REMARK Notes 2 C
53
SMTP_ADDR Email 3
C 53
REMARK Notes 3 C
53
SMTP_ADDR Email 4
C 53
REMARK Notes 4 C
53
ANRED Form of Addr C
30
NAME1 Name Contact Person C
28
NAMEV First Name Contact Person C
35
NAME_LAST Last Name Contact Person
C 28
TEL_NUMBER Telephone No Contact Person
CURR 16
TEL_EXTENS Ext Contact Person
CURR 7
MOB_NUMBER Mobile No Contact Person
CURR 24
FAX_NUMBER Fax number Contact Person
CURR 31
FAX_EXTENS Ext Contact Person
CURR 10
ABTNR Dept. Contact Person
CURR 4
VTEXT Description
C 20
PAFKT Function
CURR 2
VTEXT Description
C 20

Accounting View
BUKRS Company code
C 4
ZUAWA Key for sorting according to assignment numbers
C 3
BUSAB Accounting clerk
C 2
AKONT Reconciliation Account in General Ledger
C 10
KNRZE Head office account number (in branch accounts)
C 10
ZTERM Terms of payment key
C 4
VZSKZ Interest calculation indicator
C 2
ZINDT Key date of the last interest calculation
DYMD 8
ZINRT Interest calculation frequency in months
C 2
EIKTO Our account number at customer
C 12
ZSABE User at customer
C 15
KVERM Memo
C 30
FDGRV Planning group
C 10
XAUSZ Indicator for periodic account statements
C 1
DATLZ Date of last interest calculation run
DYMD 8
XZVER Indicator: Record Payment History ?
C 1
ALTKN Previous Master Record Number
C 10
MGRUP Key for dunning notice grouping
C 2
TLFXS Accounting clerks fax number at the
customer/vendor C 31
PERNR Personnel Number
C 8
INTAD Internet address of partner company clerk
C 130
MABER Dunning area
C 2
MAHNA Dunning procedure
C 4
MADAT Last dunned on
DYMD 8
MAHNS Dunning level
C 1

Sales View
VKORG Sales Organization C
4
VTWEG Distribution channel C 2
SPART Division C 2
VERSG Customer statistics group C 1
KALKS Pricing procedure assigned to this customer C 1

KDGRP Customer group C 2
BZIRK Sales district C
6
AUTLF Complete delivery defined for each sales order. C 1
ANTLF Maximum number of partial deliveries allowed per item C 1
KZTLF Partial delivery at item level C 1

KZAZU Order combination indicator C
1
VSBED Shipping conditions C
2
VWERK Delivering plant C 4

VKBUR Sales office C
4
KKBER Credit control area C 4

PARVW1 Bill to party C 10
PARVW2 Ship to party C 10
PARVW3 Payer C 10
PARVW4 Main customer C
10
PARVW5 Sales employee C

10
KUKLA Customer Class C 2
WAERS Currency CURR
3

Pricing in SAP SD
SAP Pricing is considered one of its strengths. It is used in multiple applications in
Configuration of both SD and MM. The Multinationals and ex- CMM Level 5 companies
use a complicated pricing schema in their business that cannot be handled by ordinary
ERP solutions in the market. SAP does the job efficiently. However, for SAP Consultants
it is one of the challenges as during the UAT they have to satisfy both the management and
Super Users with practical demonstration. The following gives an introduction about
Pricing to the SD Consultants.
Applications of Condition Technique:

Following are the applications of condition techniques

1. Pricing

2. Account Determination

3. Output Determination

4. Batch Determination

Pricing Elements : Price, Discount/Surcharge, Freight and Tax are called Pricing
Elements
Pricing Procedure : It is used to determine valid condition record
Pricing Procedure Determination: Sales Area, Customer Pricing Procedure, Sales Doc
Pricing Procedure

Header Conditions : Header conditions are automatically distributed among Items.
1. Header Conditions has to be marked as Group Condition in order to be distributed
among Items

2. Header conditions are distributed among Items based on Value, Volume and Weight

3. The basis of distribution of header condition among Items is set in Base Formula
field in Pricing

Procedure in the IMG

Pricing in Billing : Pricing can be done again at billing level using following
Pricing Types

A: pricing Elements copied from Reference document and updated according to scales

B: Pricing is carried out again

C: Manual Pricing Elements are adopted & pricing is carried out again for remaining
pricing elements

D: Pricing Elements are copied from Reference document

G: Pricing Elements are copied from Reference document and Tax re-determined

H: Pricing Elements are copied from Reference document and Freight re-determined
Condition Exclusion : Condition exclusion can be used to determine the Best Price
1. Condition exclusion is performed using Exclusion group

2. Exclusion group is a combination of condition types

3. During Pricing the conditions which give best price are selected from the exclusion
group and

The others are de-activated

4. The cumulative value of a condition can be tracked and displayed in a condition
record
Condition Supplements: These condition types are added to the condition record e.g.
1. HM00 : Manual Header condition to enter Order value
2. AMIW : Min Order Value, Statistical group condition whose value is distributed
among items
3. DIFF : Group Condition to calculate diff b/w the rounded value & Net order
value.

4. PN00 : Net Prince for Item,

5. PMIN : Min price for the material

6. PR02 : Prices with scales [scale type=D]

7. KF00 : Freight Surcharge
8. HD00 : Manual Freight Surcharge
Note: Rounding Unit is maintained in Table OO1R for each company code and currency

SD Shipping and Transportation

Shipment Processing consists of the following

1. GR for Inbound or GI for Outbound
2. Create Shipment document
3. Process Shipment document [Planning]
4. Monitor Shipment document [Reporting]

Info in Shipment document : It consists of the following

Inbound or Outbound deliveries

Shipment types [Individual or Collective Shipment]

Mode of Transport [Aeroplane, Ship, Truck]

Service Agent [Vendor]

Deadlines [Transportation Planning]

Shipment Stages

Shipment Output

Partner
Delivery and Shipment : The relation is as follows

Delivery Shipping Point Plant

Shipment Transportation Planning Point Company Code

Transportation Planning Point : A Location or a group of people

Shipment Costing : It consists of following

1. Create Shipment Cost Document
2. Calculate Shipment Cost
3. Settle Shipment cost with Service Agents

4. Bill Shipment Cost to Customer
Shipment Cost Deter Proc : It consists of following

1. Transportation Planning Point

2. Shipping Type

3. Service Agent/ Forwarding Agent
4. Shipment Cost Item Category
Settlement of Shipment Cost : It consists of following

1. Shipment Cost is posted in FI as Accruals
2. Shipments cost is assigned to a Cost Object
3. Payable is posted in FI to cancel Accruals
Note: Shipment Cost is added to the material as Delivery Cost for Inbound Shipments
Payment to Service Agents : It is made by
1. Creating credit memos and sending them periodically
2. Receiving Invoices from service agents and posting them as invoices in FI

SD Configuration Smmarised
Organization Units
Company Code
Smallest organizational unit for which individual financial statements can be drawn
up according to the relevant commercial law. This includes entry of all
accountable transactions and the creation of all proofs for a legally required individual
account closing, such as the balance sheets and the profit and loss statement.
Sales Organization
The sales organization is an organizational unit in Logistics that groups the enterprise
according to the requirements of sales and distribution. A sales organization is responsible
for distributing goods and services.
A sales organization is uniquely assigned to a company code. More than one sales
organization can be assigned to a company code. If you use the Sales and Distribution
module, you need at least one sales organization.
You maintain own master data for a sales organization. In the sales statistics, the sales
organization is the highest summation level. All items in a sales and distribution
document, that is, all items of an order, an outbound delivery or a billing document,
belong to a sales organization.
Distribution Channel
A distribution channel is a means through which saleable materials or services reach the
customer.
Several distribution channels can be assigned to a sales organization. If you use the Sales
and Distribution module, you need at least one distribution channel. For example, it is
used to
Define responsibilities.
Achieve flexible pricing.
Division
A division is used to group materials and services.
A sales organization can have several divisions assigned to it, for which it is responsible.
If you use the Sales and Distribution module, you will need at least one division.
A division can, for example, represent a product group. Therefore, you can, for example,
restrict price agreements with a customer to a certain division. You can also conduct
statistical analysis by division.
Sales Office
A physical location (for example, a branch office) that has responsibility for the sale of
certain products or services within a given geographical area.
Master Data
Customer Master Data
A customer is a business partner with whom the company exchange goods and services.
In sales and distribution, products are sold to business partners or services are performed
for them. Data about the products and services as well as about the business partners is the
basis for sales processing. Sales processing with the SAP R/3 System require that the
master data has been stored in the system.
In addition to sales and distribution, other departments of the company such as accounting
access the master data.
The processing of business transactions in sales and distribution is based on the master
data. In the SAP R/3 System, business transactions are stored in the form of documents.
These sales and distribution documents are structured according to certain criteria so that
all necessary information in the document is stored in a systematic way.
In SAP, there are several terminologies to maintain business partner at the system:

Business Partner Description
Sold To Party
Person or company that places an order for

goods or services. The sold-to party can
also perform the functions of the payer,
bill-to party, or ship-to party.
Ship To Party
Person or company to where we deliver

the goods or services. The ship-to party
can also perform the functions of the
payer, bill-to party or sold-to party.
Bill To Party
Person or company to where we send the

invoice document for goods or services.
The bill to party can also perform the
functions of the payer, ship-to party or
sold-to party.
Payer
Person or company who pay the

transaction. The payer can also perform
the functions of the sold to, ship-to party
or bill-to party.
Main Customer
The main customer is a logical parent

customer of all customer codes represent
one physical customer.
Employee
The employee is responsible for

processing the business transaction.

It is advisable to store as much data as possible in master records in the R/3 System. This
will save you time during order entry and help you to avoid incorrect entries.
The customer master groups data into categories:
General data
Company Code Data and
Sales area data
The General data is relevant for sales and distribution and for accounting. It is valid for all
organizational units within a client.
The Company Code Data is relevant for accounting. It is valid for the respective company
code.
The Sales Area Data is relevant for sales and distribution. It is valid for the respective
sales area (sales organization, distribution channel, division).
Activities for customer master data maintenance include:
Customer Groups: can be maintained in Sales area data
Customer Classes: - can be maintained in General data (Marketing View)
Sales District: - can be maintained in Sales Area Data in Sales tab
Customers are maintained via Regions in our case we have different regions in each sales
office.
One-time customers
Business partners who have a business transaction with you only once are called one-time
customers. You do not have to maintain master record for one-time customers because you
do not need this master record after the business transaction.
The account group can restrict the number of screens accessed in the master record for
one-time customers.
Pricing Master Data

Condition Types
Identify the characteristics of a condition. For example, in pricing, different

condition types are used to distinguish between a discount that refers to a net
price and a discount that refers to a gross price .
Condition Record
The values in a condition record (price, surcharge, and discount) can be maintained
according to a scale. You can specify an unlimited number of levels in a scale if required.
You can specify an upper and lower limit for each condition record. Manual changes to
pricing elements determined by the system can be made only within these limits. (For
example, making a discount that could only be changed within the range of 1% to 3%).
The prices, surcharges, and discounts determined automatically by the system can be
changed manually if required.
You can change or create conditions on the condition screen.
Conditions can also be entered at the document header level. These are known as header
conditions and are valid for all items. Condition can also be entered at the item level there
are known as item conditions.
These header conditions are automatically distributed among the items based on net value.
Order Processing
The sales order is a document between a sales organization and a sold-to party about
delivering products or providing a service for defined prices, quantities and times.
In the sales order, we record the customer number, the product customer ordered and the
delivery date if necessary. Then the system automatically proposes data from the relevant
master records:
From the customer master record of the sold-to party, the system proposes sales data such
as internal organizational element assigned to the customer, shipping data such as default
delivering plant, and billing data such as term of payment. In addition, the system copies
customer-specific master data about texts, partners, and contact people at the customer
site.
For each material in the sales order, the system automatically proposes data from the
relevant material master records, such as availability check, tax determination, and weight
and volume determination.
The data proposed by the system can be used as a basis data for sales order. We can
modify this data manually or add new data. For example, we can branch in the sales order
to a number of different screens where we can display and modify data, such as terms of
payment and delivery data.
Shipping Processing
Shipping is defined as The act or business of transporting goods.
In shipping processing, all delivery procedure decisions can be made at the start of the
process.
There is several SAP terminology created on the system for shipping process:
Plant
Plant is Organizational unit within Logistics that serving to company according to
production, procurement, maintenance, and materials planning. A plant is a place where

either material is produced, or goods and services are provided.
Shipping Point
Shipping points are organizational units that are linked to a plant and represent the point of
departure or receipt of material. In SAP, a plant may have many shipping points; a
delivery is created from one shipping point.
Storage location
Storage location is a location, where the stocks are kept within a plant and need to be
differentiated for reporting purposes from other locations. For detail of number storage
location created on the system, see Material Management Blueprint.
Delivery Processing
In its role as central object of the goods issue process, the outbound delivery supports all
shipping activities including picking, transportation, and goods issue. During the outbound
delivery process, shipping-planning information is recorded, status of shipping activities is
monitored, and data accumulated during shipping processing is documented. When the
outbound delivery is created, the shipping activities, such as picking or delivery
scheduling, are initiated, and data that is generated during shipping processing is included
in the delivery.
Partial Delivery and Complete Delivery
A customer may specify that he or she will only accept complete delivery of an order.
However, the customer may also agree to accept several partial deliveries for an order or
an order item.
You enter the appropriate indicator in the customer master record to control this. The
indicator is copied into the order. You can change the indicator there. You can also enter
the indicator manually in an order. When you process an order or create a delivery, the
system checks this indicator to determine whether complete delivery is required or
whether partial delivery is permitted.
Creating Outbound Deliveries
You can create a single outbound delivery for exactly one order, if you know the order
number. Only the order items from this order that are due for shipment will be included in
the delivery. You can make changes to the shipping data, if necessary.
Goods issue
Posting goods issue for an outbound delivery completes shipping activities.
Posting goods issue requires that all mandatory shipping activities have been performed.
Goods issue can be posted by changing a single outbound delivery. Alternatively, you can
use the collective processing function in order to select all deliveries for which goods
issue is due to be posted, and then post the goods issue for them. You can also use the
outbound delivery monitor to do this.
You can also post the goods issue when the picking is confirmed.
Effects of goods issue
After the goods issue has been posted, there is limited scope for changing the outbound
delivery. In particular, no changes can be made to the quantities. At this point in
processing, the delivery document has to reflect the actual physical delivery.
Goods issue:
Reduces warehouse stock
Posts the value change to the stock accounts in inventory accounting
Reduces delivery requirements
Enters status information in the outbound delivery is stored in the document flow
Creates a work list for billing
Cancel goods issue
If goods issue for an outbound delivery is cancelled, the goods issue posting is reset. The
system copies the quantities and values from the original goods issue document and
carries out an inventory posting based on these quantities and values with a reversed +/sign.
If you cancel goods issue, this affects the entire outbound delivery.
The cancellation document created during cancellation is entered in the document flow for
the outbound delivery.
After goods issue has been cancelled, the goods movement status of the outbound delivery
is reset to Not yet started. This allows you to further process the outbound delivery as
usual. The delivery requirements are also recreated.
Cancelling goods issue comprises two steps if the outbound delivery has been billed. In
this case, you must first cancel the billing document. Then you can cancel goods issue.
Outbound Delivery
Outbound deliveries are normally created w.e.t Sales Order.
Billing Document
Invoice is a legal document used to bill a customer for goods delivery. Deliveries and
services that are carried out based on sales orders are invoiced to the customer. Billing
represents the final processing stage for a business transaction in Sales and Distribution.
Information on billing is available at every stage of order processing and delivery
processing.
Create Billing Document
When you create a billing document, data is copied from the sales order and the delivery
document to the billing document.
Delivery items as well as order items can be references for the billing document.
The billing document serves several important functions:
It is the sales and distribution document that helps you to generate invoices.
The billing document serves as a data source for financial accounting (FI) to help you to
monitor and process customer payments.
When you create a billing document, the G/L accounts will normally be updated
automatically.
During this process, the R/3 system carries out
A debit posting on the customer receivables account and
A credit posting on the revenue account.
Special Considerations/Enhancements/Authorization Requirement/Notes
Invoice should include batch numbers and expiry dates.
Revenue and discount should be posted separately to GL account.
Credit and Debit Memo
Credit or Debit Memo is a document created at the system based on a customer
complaint/customer claim and correction process for any error on invoice transaction.
Credit Memo reduces receivables in Financial Accounting; meanwhile Debit Memo
increases receivables in Financial Accounting. Prior to precede Credit or Debit Memo, a
request can be created as reference document for billing.
Sometimes the customer need to return some valid items due to many reasons like closing
account, Reallocation etc.
This process will take another few steps to do it. Customer will inform the sales
representative that he want to return this item. Sales rep. will check the validity period off
the goods.
Credit manager will approve this process as well as the field force manager. Once it is
approved from both of them, it will go to sales manager for approval. Then this document
will be send to the warehouse to accept the return process.
According to the returned quantity delivery note will be created to update the stock
Otherwise, stock will not be updated.
Finally, credit not will create for this in coming delivery.
Return Order Process

Sometimes the customer need to return some valid items due to many reasons like closing
account, Reallocation etc.
This process will take another few steps to do it. Customer will inform the sales
representative that he want to return this item. Sales rep. will check the validity period off
the goods.
Credit manager will approve this process as well as the field force manager. Once it is
approved from both of them, it will go to sales manager for approval. Then this document
will be send to the warehouse to accept the return process.
According to the returned quantity delivery note will be created to update the stock
Otherwise, stock will not be updated.
Finally, credit not will create for this in coming delivery.
Return Order Type
The following order type is used to process customer returns:
Return Delivery Type
The return delivery type is used to process customer return delivery.
Return Billing Type
The return billing type is used to process customer return billing document.
Credit Management
Credit management is a process in which system calls up information about the current
credit status of a customer. The credit limit will be checked automatically, if a customer
has exceeded his credit limit or is having any problem with other credit management
checks, system blocks the sales order for that customer. Credit manager will check
customer credit status and release sales order if possible.
Different Types of Credit Checks
Static Credit Limit Check
The customers credit exposure may not exceed the established credit limit. The credit
exposure is the total combined value of the following documents:
Open orders
Open deliveries
Open billing documents
Open items (accounts receivable)
The open order value is the value of the order items that have not yet been delivered. The
open delivery value is the value of the delivery items that have not yet been invoiced. The
open invoice value is the value of the billing document items that have not yet been
forwarded to accounting. The open items represent documents that have been forwarded to
accounting but not settled by the customer.
Maximum Document Value
The sales order or delivery value may not exceed a specific value that is defined in the
credit check. The value is stored in the currency of the credit control area. This check is
useful if the credit limit has not yet been defined for a new customer. It is initiated by a
risk category that is defined specifically for new customers.
Critical Fields
The credit check is triggered by changes made in the document to values in any of the
credit-sensitive fields. According to your Customizing settings, the system runs a check
credit between changes or differences in the sales order data against the default values in
the customer master record. Examples of such fields are terms of payment and fixed value
dates.
Oldest Open Item
The oldest open item may not be more than a specified number of days overdue.
You can define any of the previous credit checks for various combinations of credit
control area, risk category, and document credit group
Credit control area and document credit group
These two parameters will be determined automatically by the system during credit
management check based on sales area information for the sales order and order type.
Risk Category
Enables the credit manager to classify customers according to commercial risk, along with
the document type, the risk category helps to determine which kind of credit check the
system automatically carries out.
Sales and Operation Planning

Sales & Operations Planning (SOP) is a flexible forecasting and planning tool with which
sales, production, and other supply chain targets can be set on the basis of historical,
existing, and estimated future data. Rough-cut planning can also be carried out to
determine the amounts of the capacities and other resources required to meet these targets.
Use SOP to streamline and consolidate your companys sales and production operations.
SOP is particularly suitable for long- and medium-term planning.
Cross Modular Configuration

SD Batch Management
The following information is very useful in case you have to configure the functionality of
Batch Management in your organization.

User Exits used to Maintain No. Range Assignments in Batch Master

1. EXIT_SAPLV01Z_001




Standard Characteristics for Classification in Batch Master Record:

1. LOBM_ZUSTD : Status

2. LOBM_LVORM : Deletion Flag

3. LOBM_VFDAT : Expiration Date

4. LOBM_VERAB : Availability Date

5. LOBM_LFDAT : Delivery Date

6. LOBM_RLZ : Remaining Shelf Life
Batch Tables

1. MCHA

2. MCH1

EXIT_SAPLMHD1_001 Used to Calculate and Check SLED
EXIT_SAPLCHVW_001 Used for Batch where-used list.
Batch master record

Logistics > Central Functions > Batch Management > Batch >
Create|Change|Display
or
Logistics > Materials Management > Material Master > Batch >
Create|Change|Display

Class

Logistics > Central Functions > Classification > Master Data Classes or

Logistics > Central Functions > Batch Management >Environment >
Classification System

Master Data > Classes

Characteristic

Logistics > Central Functions > Classification > Master Data > Characteristics
or

Logistics > Central Functions > Batch Management > Environment
>Classification System > Master Data >Characteristics

Customizing related to Batch Management

Activity

Menu Path

Tools > Accelerated SAP > Customizing > Edit Project

Implementation Projects > SAP Implementation Guide (IMG)

Main menu paths for setting up Batch Management

Logistics - General > Batch Management > Specify Batch Level and Activate
Status Management

Logistics - General > Batch Management > Batch Number Assignment

Logistics - General > Batch Management > Creation of New Batches

Logistics - General > Batch Management > Batch Valuation

Logistics - General > Batch Management > Batch Status Management

Logistics - General > Batch Management > Batch Where-Used List

Logistics - General > Batch Management > Batch-Specific Material Units of
Measure

Batch Determination

Logistics - General > Batch Management > Batch Determination and Batch Check
> Condition Tables

> Access Sequences

> Strategy Types

> Batch Search Procedure Definition

> Batch Search Procedure Allocation and Check Activation

> Activate Automatic Batch Determination in SD

> Define Selection Classes

> Define Sort Rules

> Maintain Batch Allocation Strategy Number Ranges

Sales and Operation Planning [SOP]

Sales & Operations Planning (SOP) is a flexible forecasting and planning tool with which
sales, production, and other supply chain targets can be set on the basis of historical,
existing, and estimated future data.

The tools streamlines and consolidate the Sales and Production operations of a company.

Integration with PP
SOP is particularly suitable for long- and medium-term planning.
SOP constitutes the planning functionality of the LIS information systems.
You pass on SOP plans to Demand Management [PP-MP-DEM] in the form of
independent requirements. In turn, this data is fed to Master Production Scheduling [PPMP-MPS] and Material Requirements Planning. [PP-MRP].

Interface with CO-PA
An interface with Profitability Analysis allows you to use CO-PA data as the basis for
sales planning in SOP. You can also pass on the results of SOP to Profitability Analysis
(CO-PA), Cost Center Accounting and Activity-Based Costing.

SOP is made up of two application components. Standard and Flexible

Flexible Planning offers options for customized configuration: you can plan on any
organizational level, and define the content and the layout of the planning screens. You
can process your planning data from the standpoint of almost any organizational unit (for
example, sales organization, material group, production plant, and product group,
material) and even from the standpoint of the entire enterprise.

The planning table in which you work resembles a spreadsheet. You have enormous scope
to track previous planning data, anticipate market demand, run analyses, and perform
what-if simulations. A series of mass processing functions automate the planning of large
volumes of data.

Scope of SOP
SOP is suitable for the planning of finished materials, but not for the planning of the
materials component parts. The one exception is Characteristics Planning.

Info Structure in SOP

The Sales & Operations Planning (SOP) application is based on information structures. An
information structure is a statistics file containing operational data. This can be either
planning data you anticipate will happen or actual data that happened. An
information structure contains three kinds of information: characteristics, key figures,
and a period unit. Information structures are used for data evaluation, projection, and
analysis in all the logistics information systems.

The SOP application is offered in two menus: Standard SOP menu and Flexible Planning
menu. With Standard SOP, you work with just one organizational unit, the product group
hierarchy, and plan redefined key figures in a planning table with a set layout.
The Info Structure SO76
All plans in Standard SOP are based on the standard info structure S076. Planning carried
out in Flexible Planning, on the other hand, can be based on any information structure of
your choice, either a self-defined information structure or a standard information
structure. This means you can plan any combination of organizational units and any key
figures. In addition, you can design your own planning table layouts, known as planning
types. You can also maintain plans using the Planning menu in the logistics information
systems.

Planning Methods in SOP
Planning method applied to the information structure is of key importance in SOP. The
planning method determines how data is distributed to different corporate units. You
define your planning methods in Customizing (in Set parameters for info structures and
key figures).

Three planning methods are available:

1. Consistent planning

2. Level-by-level planning

3. Delta planning

Sales and Operation [SOP] Configuration

In one of the implementations in my career, we had to map the Sales and
Operation Planning requirement of the company into SAP and give them the future
projection. A Pharmaceutical company had multiple Pharmacies across the country.
Hence, it was extremely important for them. We worked over the functionality so much in
the test client that we remembered all the steps along with transaction codes by heart.
The following is a list of those Transaction codes along with Stepwise procedure that will
help you in SOP functionality.
The Structure MCVBRP is appended by ABAPer to include the required Key Figures used
in the Planning table for the Client.

1-Field Catalog for Key Figures and Characteristics (MC19)

2-Create Info Structure (MC21)

3-Update Info Structure (OMO1)

4-Set Planning Parameters for Info Structure (MC7F)

5-Create Planning Type (MC8A)

6- Create Plan in Flexible Planning (MC93)
Master Data for SOP:

Create Planning Hierarchy (MC61)

Revise Planning Hierarchy (MC59)

Testing and Training

SAP UAT Template
UAT stands for User Acceptance Test. UAT is an important activity in the ASAP
Methodology used for SAP Implementation. It is a very tense and intense activity as the
key users and some experienced end users mostly raise their objections on the TO BE
Design agreed upon in the Business Blueprint. It often witnesses unpleasant moments
between the Implementation Team and the Client.

The script for the scenario is prepared tested and then given to the key users to test along
with their observations. Mostly the reason of conflict is the lack of complete knowledge of
the Business process owners while explaining their business requirements and deep
transactional knowledge of the Key users due to their experience in running the business.
The following Template will help you to visualize and learn more about the Test scenarios
used in the UAT.

Test Scenario No. TS-SD-0051 Sales Order (Complete Cycle)
Case Description

Create a Sales Order

Reference to customer PO

Issue Bonus for two order lines

Create two lines without bonus

Do the manual allocation for two lines and automatic allocation for rest of the lines

Create a delivery note

Create Invoice

Setup Data To be entered by Key Users

Special Requirements Unique or specific requirements that need to be emphasized for
configuration. One to two line description of the requirement. Reference can be made
back to the Business Blueprint for further detail

Okay? Yes No

Check Credit limit for customer

Okay? Yes No

Check Stock Availability

Okay? Yes No

Batch determination based on first expiry first out

Okay? Yes No

Okay? Yes No

Okay? Yes No

Expected Results

Explanation of Unexpected Results

1 Financial and Controlling entries should be created by the system

2 Stock should be reduced

Organizational involvement:

FI CO SD MM PP ____________ (Specify)
Approval

Date

Signed By

1-

2

Comments

Configuration Section - To be filled by Project Team

Evaluation

Overall fit with company requirements

Low Medium High

Gaps (not identified within Business Blueprint) If Yes, explain:

Missing Data If Yes, explain:

Missing Documents or Reports If Yes, explain:

Missing Functionality If Yes, explain:

Missing Interface If Yes, explain:

System Mods (screens, tables or data) If Yes, explain:

Other yes, explain:

Future Enhancements If Yes, explain:

Approval Date by

Comments

Cut over Plan

This is an example of a Cutover Plan from a live SAP implementation:

Preparation for Cutover

During the time of cutover and migration to SAP, system will not available for almost a
week. It is essential from business point to inform all the business partners about the down
time in advance. Therefore as a part of preparation, it is recommended to send this
information in advance to all the customers and vendors.
Prepare Production Environment

In this step, production machine will be prepared and tested in advance for all the
application components. Since production machine will be connected to client network, it
is necessary to test this connectivity in advance. In addition, all printers will also be
installed and checked in this step.
Setup Application
In this step SAP, application will be setup on Production system, after taking all the
transports to production SAP AG will verify the system is ready to go live.

Convert and Verify Data
In this step, data will be downloaded from legacy system and converted into required
format to upload into SAP. After verification, data will be loaded into SAP.
Verify production readiness

This is the final step before Go Live, in this step final review for cutover will be done to
make sure all activities related to Go Live have been performed and system is ready to go
in Production.
Support after Go Live
To support the users after Go Live, helpdesk will be established. All the calls from users
will be received by helpdesk at Tel No: 99999999, issues will be categorized into HIGH,
MEDIUM or LOW. After creating the ticket support desk will assigned it to the respective
team (FI, CO, MM, SD, and BW) for the solution. Support team will then base on priority
look into the issue.

SAP Training Development

With the start of EUT in the Final Preparation Phase [Phase 4 in the ASAP Methodology]
Consultant have the develop training material and training exercises with test data taken
from the copy of QA Client into the Training Client so that the End Users can practice the
new transactions in the SAP system. The Training Client is usually refreshed after a
certain interval when the data is consumed in case the number of End Users is huge and all
have to be trained using the data.

Training Data Source

1- It is normally an excel sheet in having the values of all those variables which are used
in the raining exercise.

When the document is, merged Word takes the values of the variables from this data
source and creates a merged document. The data created in the source data document is
normally created using CATTs [Computer Aided Test Tool] in SAP.

2- Note that the headings of the columns are infact the variables used in the training
document.
This data source contains data for 6 sets of data in total. So the merged document will
have 6 data sets namely Instructor, Trainee01 to Trainee05.

3- This is the product of the merger of the training document and the data source
document.
It is supposed to be a big document depending upon the number of copies needed. It is
recommended to divide this document into smaller sets to utilize less memory resources of
computer and hence fast editing or of the document.

4- It is also recommended not to include the table of contents specially is DDS toolbar is
being used in the Merged document. It can always be added later on.

Training Exercise

1- It is the real source document of SAP training material to be created in bulk for the end
users during the training delivery phase of a project.
2- It is created in such a manner that when it is merged the fields with variable values
acquire their values from the source document where the data to be popped is stored.

3- The variables fields are inserted using the Merge feature in MS Word.

4- The three steps in the Merge process are (depending upon the version):
(Tools Mail Merge)

a) Create Main document:

It is the main merged document in letter or legal format.

b) Get Data source:

It is an excel sheet having the values for the variable fields in the training exercise.

c) Merge the data with the element:

5- It is the final product where the variable fields are replaced by their respective values
from the excel sheet.
6- Note: In later version of MS word, the merge functionality is performed using a
wizard that has 6 steps. Following is an example of a Training Exercise.

Practical Example

Enter an Inventory Recount LI11N
This transaction is the same transaction used to perform the Inventory count. The only
difference is that this count is for a different version of the original inventory document.

1. To enter an inventory count, follow the menu path given below from the initial R/3
screen, double clicking on the last item:

Logistics > Logistics Execution > Internal Whse Processes >Physical Inventory
> In Warehouse Management > Count Results > Enter

2. Enter the Warehouse number 100.

3. Enter the Inventory record wminvrec.

Note: The Count date should default to todays date.

4. Enter the Recount version 01.

5. Click on the Enter button

6. Enter the Quantity recounted 270.

7. Click on the Enter button

8. Record the message at the bottom of the screen

9. Click on the Enter button to confirm the message at the bottom of the screen.

10. Click on the Save button

11. Record the message at the bottom of the screen

12. Click on the Exit button until the initial R/3 screen is displayed.

How to use CATT in SAP

CATT is a useful tool to create Master data as well as record repetitive functions in SAP.
The following Procedure explains how it is done in the system.

Procedure

1) Enter the transaction code SCAT in the command field or follow the menu path given
below:
System Services Catt Record

2) Enter the name of the CATT in the test case field and press Enter. In this example, we
will use Z_SCM_MM01

Legend: Z = all test cases normally start with Z, SCM = the area in which you are
creating the CATT,
MM01= the transaction code used to create a material master.

3) Click on the TCD button

4) Enter MM01 in the pop up window and press Enter

5) Enter Industry Sector and Material type and press enter.

6) Select the views and organizational structure and press enter.

7) A window will pop up asking for ending the transaction. Click on the Stop
transaction button.

8) Click on the Save button.

9) Another window will pop up. Click on the local object button after deleting any
value in the development class.

10) Click on the back button.

11) Click on the Change button now.

12) Double click on the TCD button.

13) Click on the Field List.

14) Click on the Next Screen button until you reach the required filed for which you want
to have variable values. In this example, we want to create multiple material with different
descriptions so we select the description to be the variable field.

15) Enter &description in the description field.

16) Click on the back button.

17) A window pops up with the same name that has been given to the variable field (in
this case description), just prefix the variable name with & (in this case it will become
&description) and press enter.

18) Another window will pop up for maintain default value for the variable just delete
any
value in the Default value filed and press enter.

19) Press the back button until the system asks you to Save the CATT. Save the test case
(CATT) that you have created.

20) On the main CATT screen now follow the menu path: Goto >- Variants >Export

21) A window will pop up asking you to enter the place where you want to export the
file that will have the values for the variable you just created in your test case
(Z_SCM_MM01). You can change the directory of the local file having the values
otherwise its always stored in SAPworkdir by default.

22) Click on the Transfer button

23) Now open the text file. Move the cursor to the row just below the last line.

24) Press Tab button on the keyboard twice.

25) In this column now enter all the values for the variable (in this case &description) for
as many sets as needed. Please note that the values should be in the same column and not
in any other column.

26) Save the local file after entering all the values.

27) Go again to transaction SCAT and select your test case and click Execute.

28) Select Long radio button under the Log type section.

29) Select Background radio button under the Processing Mode section.

30) Select external from file radio button under the Variants section.

31) Click on the Choose button. Select the text file from the local disk and press Enter.

32) Click on the Execute button.

33) SAP will give you the new material created individually after running the CATT in
the background and now these materials are ready for use. If there is an error then the
result is, be a Red color for that material otherwise Green color shows that the CATT was
executed successfully.
SAP Training Module

1- It is a detailed document about a transaction or a group of transactions used in the
business.
2- It is based on the Business Process Script. It explains every minute details in non-ASAP
methodical form. It is scenario dependent and not a general document for the transaction
e.g. we might have one module for Goods receipts without reference (MB1C) but another
module for into Goods Receipt for Purchase Order or Delivery (MIGO) and even one
module for a couple of similar reports like LB10, LB11, LB12.

3- The module transaction has to have the business scenario as well as detailed SAP
screen shots for every step.
Example of a Training Module:
Display Material Bill of Material (BOM) CS03
Performance Objectives

Upon completion of this training module, participants will be able to perform transaction
CS03 to display a material bill of material (BOM).

Business Procedure

A bill of materials (BOM) is a complete, formally structured list of components that makes
up a product or assembly. The list contains the object number of each component,
together with the quantity and unit of measure. The components are known as BOM
items. The Material Standardization Division (MSD) creates bOMs.

BOMs are used in their different forms in various situations where a finished product is
assembled from several component parts or materials. They contain important basic data
and essential master data for integrated materials management. In, BOMs will only be
used for Plant Maintenance.

The following BOMs can be created in SAP:

Material BOMs

Equipment BOMs

Functional location BOMs

Document structures

Work breakdown structure (WBS) BOM

This transaction is used to display a BOM. All fields are display only no data can be
changed.
Step By Step

1. A material BOM has been created.

2. The need arises to display the BOM to check the components.

3. Run the transaction to view the BOM.

Display Material BOM CS03

To display a material BOM, follow the menu path given below from the initial R/3 screen,
double clicking on the last item:
Logistics > Production > Master Data > Bills of Material > Bill of Material >
Material BOM > Display

Field descriptions for SAP or required fields are labeled below in boldface type. Optional
fields are
labeled in ordinary type.
Fields not listed below should not be used.

Fields displayed in gray on the terminal screen cannot be changed.

Note: The Plant field should not be entered, as BOMs will always be group BOMs.
Click on the Enter button.

To select a line item, click on the button to the left of the line item, and click
on the Item button.

Note: To display further information, click on the following tabs: Status/Ing text,
Purch., Adm. Data, Document assignment.

If more than one item was selected on the previous screen, click on the Next screen
button to view the data for the other components.

After all necessary data has been viewed, click on the Header button.
Note: To display further information, click on the following tabs: Further data,
Admin. data, Doc. assignment.

To exit this transaction, click on the Exit button until the initial R/3 screen is displayed.
Sales Information System

Sales Information System SIS Setup
In order to enable postings in SIS for Info Structure S430, the following steps are carried
out:
Activate Update

IMG -> Logistics - General -> Logistics Information System (LIS) -> Logistics Data
Warehouse -> Updating -> Updating Control -> Activate Update,

Select option Sales and Distribution from the popup menu,

Select info structure S430,

set update parameter to Synchronous updating (1) or Asynchronous updating (2); note
that there is no option to set the reporting period split for S430, because it records statistics
by document item, there is no aggregation within reporting periods.

Check SIS settings for statistics groups

Warehouse -> Updating -> Updating Control -> Settings: Sales -> Statistics groups,

Check here which statistics groups are available for use and assign the appropriate
statistics groups to document type and item category (for sales documents).
Check item level update groups

Warehouse -> Updating -> Updating Control -> Settings: Sales -> Update group -> Assign
update group on item level
Check here that update group 00001 (SIS: Sales Document, Delivery, Billing Document)
is set for the required combinations of sales area, customer statistics group, material
statistics group, document statistics group and item category.

Check header level update group

Warehouse -> Updating -> Updating Control -> Settings: Sales -> Update group -> Assign
update group on header level,

Check that update group 00001 (SIS: Sales Document, Delivery, Billing Document) is
set for the required combinations of sales area, customer statistics group and document
statistics group.

Update of S430

To carry out a successful update of S430 the following is required:

Document sold-to party must have a statistics group (KNVV-VERSG) for which a valid
update group assignment has been made.

Document item material must have a statistics group (MVKE-VERSG) for which a valid
update group assignment has been made if item level update group assignment is used.

Document type must have a statistics group set via customizing step

IMG -> Logistics - General -> Logistics Information System (LIS) -> Logistics
Data Warehouse -> Updating -> Updating Control -> Settings: Sales -> Statistics groups >Assign statistics group for each sales document type for which a valid update group
assignment has been made.

Item category must have a statistics group set via customizing step

Warehouse -> Updating -> Updating Control -> Settings: Sales -> Statistics groups >Assign statistics group for each sales document item type for which a valid update group
assignment has been made.
Standard SD Reports
The following are Standard SAP SD Reports used in Sales and Distribution
Incoming Order Report
To run this report, use one of the following access options:
Logistics > Sales and distribution > Sales information system> Standard analyses
> Customer / Material / Sales Organization / Sales Employee / Sales office

In the Command field, enter transaction (see table below) and choose Enter.

Choose one of the following options:
Transaction code Standard Analyses

MCTA Customer

MCTC Material

MCTE Sales organization

MCTI Sales employee

MCTG Sales office

Incomplete Sales Documents

Logistics > Sales and distribution > Sales > Information Systems > Orders >
Incomplete Orders in the Command field, enter transaction V.02 and choose Enter.
1. Under Incompleteness, select all types of incompleteness.
2. Under Organizational data, enter Sales Organization.

3. For this example, no SD transactions need to be entered. For a list of transactions, click
on the SD transaction field to reveal a possible entries list.

4. Choose Execute.
5. To edit a document, select the checkbox to the left of the desired SD document (for
example, Choose Display to navigate to details of the incompleteness.

6. Choose Edit Incompletion to see the details of the incompleteness.

7. Choose Complete Data, to edit this sales document.

8. The Cursor automatically leads to the incomplete data column Fill in the Information
(Purchase Order Number) and save the document.

List of All / Open Billing Documents
Logistics > Sales and distribution > billing > Information System > billing
documents > List billing documents
In the Command field, enter transaction VF05 and choose Enter.
1. Enter a valid pay-to party number in Payer
2. Choose the document date range based on the billing date

3. Select all billing docs.
4. Optional: Choose Display Variants to change the variant. You can also do this from the
output screen.
5. Optional: Choose further sel. criteria to select additional selection criteria.

6. Choose Enter.

List of All / Open Deliveries

Logistics > Sales and distribution > Shipping and Transportation > Outbound
Deliveries > Lists and Logs > Outbound Delivery Monitor In the Command field,
enter transaction VL06O and choose Enter.

1. Select List Outbound Deliveries.
2. Enter Sales Organization. Alternatively, you could enter a valid Shipping Point.

3. Under Planned Goods Movement Date, enter a date range the delivery date is the date
on which the delivery should be made.

4. Select Check at item Level Picking Data Selection criteria.
5. Choose Execute.
You may choose Filter, or Display variant to change the layout. From within the report,
you may change the layout by choosing Setting> Display variant. The fields on the left
side of the screen are those that are to be displayed.

SAP Configuration Template

We used this SAP Configuration Template for the SD Module during multiple
implementations and Go Live instances. I hope it is of some help to those who need to
document their Configuration activities.
Configuration document

<Module Name>

Release My SAP ECC5.0

Prepared By:

<Consultant/s Name>

Date: Month [MM] Day [MM] Year [YYYY]
Table of Contents

1.
2.
3.
4.
5.
Document Control
General Settings
Enterprise Structure
Document Number Ranges Overview
Business Transactions

Document Control

General Settings

The configurations can be made in this menu path:

Example:

Sales Org path in IMG

Enterprise Structure

The configurations can be made in menu path:

Example:
Definition, Assignments in Imp path

Document Number Ranges Overview

Example:

Document > Document Number Ranges > Overview

Number range object Accounting Document:

Company Code 1000

No 01

Year 2006

From number 1020100001

To number 1020199999

External

Business Transactions

Maintain number ranges for orders

Example:

Order Master Data > Maintain number ranges for Orders

Order Type

From Number

To Number

SD Month End Closing

Month End Closing is the first litmus test of successful Go Live in an SAP Project. Most
modules and especially SD, MM and FI are involved in this intense practice, as the figures
in the reports should be reconciled to give an accurate picture of results. After one month
of post implementation, the client as per their business practice to reconcile figures in
Sales and FI, for example and the SAP SD month end closing activities start in full swing
announces support, when the month ends a certain date. Subject to the business practices
of the SAP Customer, the following steps are recommended as SAP SD month-end closing
Activities:

1) All those deliveries for which Goods Issues has been posted should be invoiced.

2) Use SAP Solution of Billing Due List (Transaction code: VF04) to display all
the outbound deliveries for which PGI has been done but Billing is pending.
3) All Credit Memos (Return Billing Documents) should be created w.r.t Return Orders.

4) Warehouse Personnel should confirm Picking for Open Deliveries.
5) The Open deliveries, for which Stock was allocated but by mistake Stock transfer
has been done, should be reversed so that PGI can be done for those open deliveries. Note
that the reversal of Stock transfers should be done by MM.

6) Deliveries should be created for Open Orders.

7) SD-FI reconciliation should be performed by comparing SIS and FIS figures.

SAP SD Transaction Codes

Whether it is configuration or Training during an SAP implementation, you need to
remember some tables and transaction in order to ease your job. There is some logic
behind these transaction codes too and with experience you know them if you are a keen
observer. The following is a list of such transaction that will help you appreciate SAP
logic and help you remember the transaction codes by heart.

SD Transactional Menus

VS00 Master Data

VA00 Sales

VL00 Delivery

VT00 Transportation

VF00 Billing

VX00 Foreign Trade

Configuration Transaction Codes

Account Group - OBD2 [In FI IMG]

Customer Material Info VD53

Define Common Distribution Channel VOR1

Define Customer Group OVS9

Define Sales Districts OVR0

Customer Master Tables - KNA1, KNB1, KNVV, KNKK, KNVP

Assign Sales Office to Sales Area OVXM

Assign Sales Group to Sales Office OVXJ

SD Tables

Table to Find any Transaction TSTC
User Settings Local Data History [Enables the History of Transactions]
Material Master Data Tables - MARA, MBEW [Valuation], MARC, MARD,
MVKE
SO Tables - VBAK [Header], VBAP [Item]
Billing Tables - VBRP, VBRK
Shipping Tables- LIKP [Header], LIPS [Item], VBEP [Schedule Line], VBUK
[Header Status],
VBUP [Item Status]
Partner Functions - SP [Ag in German], SH [We in German], BP [Re in German],
PY [RG in German]

Entering SAP Community

SAP Consulting Skills

Consulting skills include Analytical skills, Communications skills, interpersonal skills and
documentation skills.
Analytical skills helps you to analyses business processes and business scenarios
systematically and the ability to translate them into the SAP framework.
Training Skills include presentation skills, language skills and knowledge of third party
training development tools like Resite, DDS, SnagIt etc.
Interpersonal skills are a tool to work in a team as SAP is an integrated solution and
consultants work closely with each other to implement the system for a client.
Communication skill is probably the most important skill a consultant needs whether it is
required in discussing and analysing the business or facing the client after implementation.
It helps in the correct and effective knowledge transfer to the end users of the system.
Support Skills include strong troubleshooting and/or debugging skills coupled with
knowledge of tools like SolMan [Solution Manager] in addition to working under pressure
to meet ticket resolution deadlines.
Knowhow of Tele-commuting Technologies is an asset when a consultant needs to work
from a remote location via phone, mobile, skype or video conferencing etc. A consultant is
supposed to know these state of the art technologies to offer his/her services to the client
to get required info from the client, any other team member or perform the required
knowledge transfer [KT, as we call it] to the client.

Example An SAP Presentation
I had the opportunity of delivering a presentation at a seminar and used the
following Seminar Agenda for the participants. I thought it might be helpful for some
consultants in case they have to introduce SAP in a presentation seminar so am sharing it
with SAP community. Just the Agenda is given below for those who are experts in SAP
but cannot integrate their knowledge in an orderly form.

Brief Professional Introduction of Consultant

Introduction of ERP Technology

ERP Solutions in the Market

Introduction of SAP R/3 as Business Solution

Modules of SAP

Clentbase of SAP

Methodology of SAP

ASAP Roadmap

SAP Consulting Career

Human Resource for SAP Project

SAP Consulting Positions

Scope of SAP

SAP Partner Academy Courses

Remote System Access

Question Answer Session

SD Interview Tips
Sales Order [VOV8]:
Doc type, No Range, Del type, Imm Delivery, Order/ Del rel Billing [F1/F2]

Item Category [VOV7]:

Item Category Group, Doc Type, Usage, Higher-level Item Cat

Schd Line Cat. [VOV6]:

Item Category + MRP type

Sales Doc Types:

Standard Order, Cash Sales, Rush Order, Return Order, FOC Delivery

Goods Issue:

COGS Debited, Inventory Credited

Billing:

Customer Debited, Revenue, Tax, Freight Credited

Incoming Payment:

Bank Debited, Customer Credited

Availability Check:

Determines Material Availability date,

Does delivery-scheduling back from required delivery date?

Run at the end of Replenishment lead time

Scope [Avail. Check]:

Current Stock, Inward Stock Movement, Outward Stock Movement

Inbound Process:

Purchase. Req Pur. Order Inb. Del T.O T.O Confirmation G.R

Outbound Process:

Sales Order Outbound Del T.O T.O Confirmation G.I

Free Goods Processing

Master Data:

Condition Record [VBN1] Sales Document

Free Conditions:

Condition Type= NA00, Item Category Usage= FREE, Item Category = TANN

Rebate Processing

Rebate Agreement Sales Doc Billing Document Post Accrual

Rebate Agreement:

Settlement Run Credit Memo Request Remove Block Credit Memo

Rebate Condition:

Condition Type: B002 [added to Pricing Proc in the Sales Document]

Credit Management

Credit Control Area [CCA] can accommodate multiple Company Codes
Static Credit Check:

Checks Open Order + Open Deliveries + Open Billing Documents

Dynamic Credit Check:

Checks Credit Horizon [date]

All Credit Checks:

Static Check, Dynamic Check, Max Doc Value, Oldest Open Item

Cross Modular

VOFM: Transaction to create and process Routines. Routines are programs used for
defining Copy

Requirements and Copy Controls

Batch Determination: The following steps defines Batch determination process in SD

> Batch Determination Procedure

> Strategy types

> Access Sequence

> Condition Tables

> Assign Batch Determination Procedure

> Automatic Batch Determination for [Sales / Delivery] Item Categories

> Define Selection Rules

> Define Sort Rules

Flexible SOP: It is used for Planning of Finished Goods

> Append MCVBRP to include required Characteristics and Key Figures

> Edit Field Catalogue to select Characteristics and Key Figures

> Create Info Structure [MC21]

> Update Info Structure [OMO1]

> Set Planning Parameters [MC7F]

> Create Planning Type [MC8A]

> Create Planning Hierarchy [MC59]

> Maintain Planning Hierarchy [MC61]

> Create SOP Plan [MC93]

Condition Technique

Acct Detr Proc. [VKOA]:

Chart of Accts, Sales Org, Cust Acct Asgmnt grp, Mat A.A.G, AcctKey

Applications of Condition Technique:

> Pricing

> Account Determination

> Output Determination

> Batch Determination

> Text Determination

Pricing

Pricing Elements:

1-Price, 2-Discount/Surcharge, 3-Freight and 4-Tax

Pricing Procedure:

It is used to determine valid condition record

Pric. Proc. Detr [OVKK]:

Sales Area, Sales Doc [Doc Pic.Proc.], Sold-to [Cust Pric. Proc]

Header Conditions:

Header conditions are automatically distributed among Items.

> Header Conditions has to be marked as Group Condition in order to be distributed
among Items

> Header conditions are distributed among Items on the basis of Value, Volume and
Weight

> The basis of distribution of header condition among Items is set in Base Formula field
in Pricing

Procedure in the IMG

Pricing in Billing:

Pricing can be done again at billing level using following Pricing Types

A: Pricing Elements copied from Reference document and updated according to scales

B: Pricing is carried out again

C: Manual Pricing Elements are adopted & pricing is carried out again for remaining
pricing elements

D: Pricing Elements are copied from Reference document

G: Pricing Elements are copied from Reference document and Tax re-determined

H: Pricing Elements are copied from Reference document and Freight re-determined

Condition Exclusion:

Condition exclusion can be used to determine the Best Price

> Condition exclusion is performed using Exclusion group

> Exclusion group is a combination of condition types

> During Pricing the conditions which give best price are selected from the exclusion
group and the

others are de-activated

> The cumulative value of a condition can be tracked and displayed in a condition
record

Condition Supplements:

The condition types which are added to the condition record

Condition Types:

Following are important condition types.

> HM00: Manual Header condition to enter Order value

> AMIW: Min Order Value, Statistical group condition whose value is distributed
among items

> DIFF: Group Condition to calculate diff b/w the rounded value & Net order value.

> PN00: Net Price for Item

> PMIN: Min price for the material

> PR02: Prices with scales [scale type=D]

> KF00: Freight Surcharge

> HD00: Manual Freight Surcharge

Note: Rounding Unit is maintained in Table OO1R for each company code and currency

Shipping

Shipment Processing:

It consists of the following

> GR for Inbound or GI for Outbound

> Create Shipment document

> Process Shipment document [Planning]

> Monitor Shipment document [Reporting]

Shipment document:

It contains the following info

> Inbound or Outbound deliveries

> Shipment types [Individual or Collective Shipment]

> Mode of Transport [Aero-plane, Ship, Truck]

> Service Agent [Vendor]

> Deadlines [Transportation Planning]

> Shipment Stages

> Shipment Output

> Partner

Delivery and Shipment:

The difference is as follows

> Delivery Shipping Point Plant

> Shipment Transportation Planning Point Company Code

Transportation
Transportation Planning Point:

A Location or a group of people

Shipment Costing:

It consists of following

> Create Shipment Cost Document

> Calculate Shipment Cost

> Settle Shipment cost with Service Agents

> Bill Shipment Cost to Customer

Shipment Cost Deter Proc:


> Transportation Planning Point

> Shipping Type

> Service Agent/ Forwarding Agent

> Shipment Cost Item Category

Settlement of Shipment Cost:


> Shipment Cost is posted in FI as Accruals

> Shipments cost is assigned to a Cost Object

> Payable is posted in FI to cancel Accruals

Note: Shipment Cost is added to the material as Delivery Cost for Inbound Shipments

Payment to Service Agents:

It is made by

> Creating credit memos and sending them periodically

> Receiving Invoices from service agents and posting them as invoices in FI
SD Certification
This is a sample of SAP SD Certification Exam. All those who are preparing for the
Certification might find it useful and orient their study on the lines that could enable them
to answer the MCQs correctly.
# Question # Correct Answer
In the customer order cycle inventory is reduced during:

A Sales
1 B Picking
C Delivery
D Goods Issue
E Billing
The following happens at post Goods Issue:

A Billing Doc created
2 B FI Doc created
C Billing doc due list performed automatically
D Sales doc status are updated
E Delivery requests and inventory updated
Which of the following are true of a Sales Organization:

A Can be assigned to one or more plants
3 B Can be assigned to one controlling area
C Can be assigned to only one company code
D Can be assigned to many shipping points
E Is part of the Sales Area

Standard Customer order management process consists of:

A Sales order, delivery, billing, complaints
4 B Sales order, GI, billing, complaints
C Sales order, Delivery, complaints
D Sales order, delivery, billing, payment
E Quote, Sales order, delivery
Which of the following are true of Customer Master Data A Bill to party, payer, ship to
party, sold to party
5 B Exists in a Sales Area
C Exists in a Plant
D Critical to the customer order management cycle
E Not Critical to the customer order management cycle
A plant in the Sales Order is proposed in the sequence: A Customer, Material, Customer
material info record
6 B Material, Customer, Customer material info record
C Customer material info record, customer, material
D Customer material info record, material, customer
E Customer, customer material info record, material
The following happens when customer master data is changed

A All existing Sales Orders are updated
7 B Only open Sales Orders are updated
C All existing Invoices are updated

D Only open Invoices are updated
E None of the above
Sales between company code A and company code B is called:

A Sales area
8 B Intra-company Sales
C Inter Company Sales
D Indirect Sales
E Third Party Sales
The shipping process supports the following:

A Creation of delivery documents
9 B Billing
C Returns order
D Packing
E Goods Issue
The following are true about a Sales Order:

A Contains customer and material data
10 B Only contains header and item
C Contains header, item and schedule lines
D Created in a Sales Area
E Allows revenue posting of documents to FI
Linked documents are called:

A Customer order management process
11 B Goods Issue
C Document Flow
D Copy Control
E Sales Order
The following are true about Schedule Lines:

A Are assigned to a sales document type
12 B Are assigned to an item category
C Contain the movement type
D Controls transfer of requirements and ATP checks
E Contains delivery dates and quantity
Schedule lines are created during the creation of:

A Sales Order
13 B Delivery
C Transportation
D Billing
E Goods Issue
The following are true about the Item Category:

A have pricing relevancy
14 B have billing relevancy
C Item number counter

D Schedule lines
E Delivery relevance
Item Category determination is done using:

A Order type, Item category usage, Item category group, item category
15 B Order type, MRP type
C Order type, Item category group, Item usage, High level item
D Item category, Item category group, High level item
E Item category, MRP type
Schedule Line determination is done using:

A Order type, Item category group, Item Category
16 B Order type, MRP type
C Order type, Item category group
D Item Category, Item Category group
E Item Category, MRP type

The Sales document type controls the following:

A Plant determination
17 B Number assignment
C Relevancy for picking
D Default billing document type
E Default delivery document type
Which of the following statements are TRUE:

A A sales office can only be assigned to one sales area
18 B A plant can be assigned to only one company code
C A distribution channel is assigned to many sales organisations
D Customer master data is only created for SD
E A sales document type can only have an internal number range
A movement type is assigned to:

A Sales Document
19 B Item Category
C Schedule Line
D Delivery
E Goods Issue
In a Sales Order a delivery block can be assigned to:

A Sales Document
20 B Item Category
C Schedule Line
D Delivery
E Goods Issue

Recommended Books
Though for a complicated and humungous system like SAP books are good but not
sufficient to be consulted but those books which are written by Industry experts and
experienced Consultants are really worth buying as the purchase serves as an investment
into your SAP Career.

With growing competition and recession trends in International markets most of the SAP
gurus as well as ambitious and bright SAP consultants are trying to invest into these areas
in addition to one or more core module.
Based on my interaction with consultants of versatile experience and expertise and my
own experience in SD, LE modules too, I would recommended some Recommended SAP
SD Books. These books are either read by me or recommended by SAP professionals with
expertise in the relevant modules bases on their practical experience in live projects.
The Recommended SAP SD Books could be purchased either from world renowned
Amazon or any other site of your choice. However, at Amazon you can have used editions
in discounted prices too.
The list of the books is as follows:

Implementing SAP ERP Sales & Distribution

Review: A very good resource for SD Consultants, I have personally read and benefitted
from it that too right in the middle of live project in resolving live issues.

Configuring SAP ERP Sales and Distribution

Review: Another nice book focused on Configuration- A key skill whose in depth
knowledge is required by every SD consultant.

SAP SD Interview Questions, Answers, and Explanations

Review: Good for the ones who are desirous of seeking a position in an SAP project.
Equally good for preparing Certification also.

Warehouse Management with SAP ERP: Functionality and Technical Configuration

Review: Very good resource book for WM.

SAP Implementation Unleashed: A Business and Technical Roadmap to Deploying SAP

Review: A very good resource for Project management in SAP.
SAP IS OIL

Oil and Gas Industry

The oil industry consists of finding, producing, and delivering oil to the end consumer in
the desired form gasoline / kerosene / aviation fuel / naphtha / lubes etc. The industry is
capital-intensive as it takes huge funds to find the raw materials, produce, and distribute
the various oil products.

Classification of Oil Industry:
The oil business is divided into two categories: upstream, and downstream. The upstream
refers to the grassroots of the oil business, the process of exploring for oil and extracting
it. The downstream refers to refining of the oil to subsequent products and the commercial
side of the business, in terms of sales and marketing of these products.

Upstream Process:
Upstream activities are closer to the source, and downstream activities, such as refining
and marketing, are closer to the consumer. This entire operational/business process in the
oil industry can be classified as:

1 Area identification

2 Geological/seismic surveys

3 Reservoir data [collection, analysis, mapping ]

4 Drilling processes

5 Transportation

6 Storage [Silos, terminals, tanks]

7 Refining

8 Post production.

Downstream Business Processes:

Petroleum downstream business processes are more closely related to standard
manufacturing and distribution industries or networks.

1 Oil company traders acquire crude oil (purchase feed stocks),

2 Refineries process the feedstock into refined products (manufacturing),

3 Pipelines, barges and vessels transport the product to terminals (primary
distribution) and

4 Tanker trucks transport the product to service stations (secondary distribution).

Service stations sell the fuel to consumers.

Practical Facts in Oil and Gas Industry
Oil and gas are two of the most heavily traded commodities in the world, and transporting
them is always a critical business action because of their value.

1- An Oil tanker may carry 2 Million Barrels or more of crude oil worth USD 80 million.
2- Using massive marine tankers, barges, and pipelines, midstream and primary supply
traders and schedulers move huge bulk quantities of oil and gas every day.

3- Crude oil and natural gas are moved from production fields to refineries and refined
products from refineries to storage terminals.

4- Oil shipments can last many weeks and involve hundreds of thousands even millions
of barrels of oil products.

5- A lot of partners and activities are involved in successfully coordinating a voyage
which means all bulk movements, regardless of mode of transport.
6- Each shipment requires detailed planning and scheduling. This involves loadings,
multiple unloading, shared resources, and multiple trades.
7- The schedulers should be aware of the current activity and status of each voyage.

8- The long lead times, the duration of movements, and the huge money involved requires
flexibility to make changes at any stage.
9- SAP developed SAP TSW [Traders and Schedulers Workbench] to enable the high
level of flexibility

IS Oil TD Master Data

In IS Oil TD [Transportation and Distribution] Configuration , Master data has to be
configured carefully as Oil Business is about millions of dollars and any mistake might
result in a technical hurdle in the operation. Let me share the Configuration of the TD
Master Data.
Define Mode of transport

1. Access the SAP implementation guide (Check if the entry already exists)

Transaction
code

SPRO
Menu
TD TD Master Data Define Routes

Define mode of transport

2. In Change view Mode of transport: Overview screen, make a new entry as
follows

Field name
Entry
Shty
10
Description

TSW Pipeline

3. Save it.

Define Shipping type

1. Access the SAP implementation guide

Transaction
code
SPRO
Menu
TD TD Master Data
Define Shipping type
Define routes

2. In Change view Shipping Type: Overview screen, make a new entry as follows

Field name
Entry
PT
30
Description
Pipeline TSW
MdTr
10
STPG
STS3

3. Save it.
Maintain TD bulk shipment type

1. Access the SAP implementation guide

Transaction
code

SPRO
Menu
TD TD Bulk Shipment
type
Define bulk shipment

2. In Change view TD Shipment Type: Overview screen, make a new entry as
follows

Field name
Entry
Bulk shipment
type
SAN TSW PIPELINE
No. range Int.
01
No range Ext.
02
Mode/transport
Pipeline
Compartment
loadId
Multiple materials per compartment
In transit post
group
PU (Pipeline untaxed)
Confirm balance No balancing required

load

Vehicle close
Gain/loss at
close

Partial del. Conf X

Veh. Cust check
No compatibility check
Prod. comp.
check
No compatibility check
UoM ID
Volume
Weight UoM
TO
Nr. Decimals
Volume UoM
BBL
Nr. Decimals
Event def. Group PIP

Header
Shipment cost
type
PIPE
Vol UoM (amb.)
BBL
Vehicle
Shipping type
30
Vol UoM (corr.)
BB6
Leg
Load transfer pt
Border cross pt
Del fulfillment
No assignment possible

Create Transport unit type

1. Access the transaction as follows:

Transaction
code
SPRO
Menu
SAP IMG Industry Solution Oil & Gas

(Downstream) TD (Transportation and
Distribution) TD Master Data Define transport
unit types
Field name
Entry
TU Type
TSWM (TSW Marine)
MoT
3 (Marine)
Type
3 (Single Unit with engine and loading

capacity)
Weigth UoM
TO
Vol. UoM
MB
TU type Txt
TSW Marine (Marine Single Unit)

2. Press Back

3. Save

Create Vehicle type


Transaction
code
SPRO
Menu
SAP IMG Industry Solution Oil & Gas

(Downstream) TD (Transportation and
Distribution) TD Master Data Define vehicle
types
Field name
Entry
Veh. Type
TSWM (TSW Marine)
MoT
3 (Marine)
Weigth UoM
TO
Vol. UoM
MB
TU type Txt
TSW Marine (Marine Single Unit)

2. Press Back
3. Save

Create Transport unit


Transaction
code
O4C1
Menu
SAP Menu Logistics Sales and

Distribution Bulk Transportation
Data Transport Unit Create
Master

4. In the create transportation unit: Initial screen enter the following and press
<Enter>

Field name
Entry
Transportation
Unit
Sea Giant
TU Type
TSWM

5. In the Create transport unit : details screen, enter the following

Field name
Entry
Transportation
Unit text
Omer
Volume UoM
MB
Weight UoM
TO
Maximum
weight
200.000

6. Press Compartments button and enter the following

Field name
Entry
Max Volume
1200

7. Press Back

8. Save

Create Vehicle


Transaction
code
O4V1
Menu
SAP Menu Logistics Sales and

Distribution Bulk Transportation
Data Vehicle Create
Master

2. In the create vehicle: Initial screen enter the following and press <Enter>

Field name
Entry
Vehicle Number
Omer
Vehicle Type
TSWM (TSW Marine)

3. In the Create vehicle: details screen, enter the following

Field name
Entry
Vehicle text
Omer
TrspPlanPt
GTP1
Volume UoM
MB
Weight UoM
TO
Maximum
Weight
360.000

4. Press Transport unit button and enter the following

Field name
Entry
Trans. Unit
Omer

5. Press <Enter>

6. Press Back

9. Press Save
TSW Overview
SAP Traders and Schedulers Workbench (T.S.W) is used to monitor current and future
supply chain activity, including all trading, inventory, and scheduled movements.

1- TSW helps you manage the supply, demand, and transportation requirements in the
midstream (crude, feedstocks, and gas transmission) and primary distribution (refined
products) sectors for all bulk transports. It also helps you manage them throughout the
complete process life cycle from deal to cash, including planning, scheduling, and
execution.
2- TSW integrates market demand information, planned and nominated bulk movements,
production data, consumption forecasts, and replenishment forecasts. Open interfaces
allow you to communicate nominations and confirmations in both directions with external
partners, such as pipeline operators and customers.

3- SAP TSW incorporates a set of tools that work together and use the same master data.

4- Technically part of the SAP for Oil & Gas solution portfolio, TSW is completely
integrated with the mySAP ERP solution and the SAP Advanced Planning & Optimization
(SAP APO) component. This integration means your planning, scheduling, and execution
processes all run in the same landscape, guaranteeing data reliability, real-time data
availability, data transparency, and the absence of data redundancy.
5- With TSW as a communication platform for you and your business partners, you create
a foundation for collaboration all along the supply chain. Many different transaction
screens and functions enable schedulers and others involved in supply chain operations to
view and manage all relevant activities. They can also look ahead to build plans for the
future and look back into the past to analyze history. This provides key decision-support
capabilities for managing future operations.

6- TSW touches all aspects of the schedulers workflow, and it provides
various integration and interface points to communicate with both internal and external
systems and parties. All tools from nomination to scheduling to freight contracts and
ticketing are integrated with one another, so you only have to enter data once. Because
of the intuitive configuration of SAP Traders and Schedulers Workbench and its master
data settings, some data does not have to be entered at all because it can be inferred by the
software. In addition, all information is fully transparent and made available in numerous
formats across the full range of scheduling and shipping transactions.

TSW Master Data

TSW Master Data consists of:

Locations, such as regions, terminals, bulk plants, refineries and other such facilities
where products are typically stored;
Transport systems, which may represent physical means of transportation such as
pipelines or more logical ones such as marine routes; and

Partners, effectively a means of identifying the actual business partners who are active
throughout the supply network, whatever their role may be in any given circumstance
(roles include receiver, supplier, carrier, shipper, inspector etc.).

All of the above are fully integrated with standard SAP R/3 objects such as customers,
vendors and plants, and thus complete consistency is maintained throughout the whole
process cycle from planning to settlement.

Recent additions to master data include mass maintenance transactions to enable fast
modeling of complex supply chains, the ability to define and maintain location hierarchies
of as many levels as desired and the flexible assignment of partners, for example where
these are global or regional in nature.
TSW Nomination
TSW is one of the strongest tools used in SAP IS Oil. It uses planning which defines what
should or could be done within any supply chain management situation. It also has the
feature of Scheduling that is the process of managing the necessary activities to enable the
ultimate execution of actions.
In Scheduling, Nomination is used to notify to and make requests from supply chain
partners.
Supply chain partners could represent trading partners like customers & suppliers and
service partners like carriers and inspectors.
Scheduled items and Nominations can be changed for any number of reasons like.
Availability of vessel, trading partners changing their requests, production shutdowns etc.
Each schedule line in a nomination describes a single movement activity like a load /
injection or a discharge.
In all cases, it is possible to define the document generation routine to use any referenced
document, the schedule line and the ticket posting to generate complete document flows
up to and including goods movement postings, with the option to include TD shipments
for those movements where transport was a consideration (as opposed to book transfers
where transport is not relevant) and this is all automated into a background process.
The nomination transaction and screen supports three main processes:
Creation and maintenance of logical collections of scheduled movements as they relate to
a carrier nomination process.
Communication and tracking of status of outputs to carriers and their responses.
Providing sufficient information to subsequent R/3 processes to support the automatic
execution routines.
Each nomination and the schedule lines within it are tracked using statuses that are used to
both generate alerts to the scheduler as well as control the execution of subsequent steps.
For example, the schedule lines are in status Planned whilst they remain internal to the
oil company, and then become Scheduled once the nomination that contains them has
been transmitted to the carrier.
The updating of the schedule lines to status Confirmed can be achieved via an inbound
interface (Inbound nomination BAPI), or manually based upon a paper or verbal update
from the carrier, or by a so-called quick confirm function, where scheduling (sending)
and confirmation occurs in one step.
Once confirmation has been achieved, the nomination schedule items are then enabled for
execution (i.e. actualization via the ticket process).
Throughout the scheduling and nomination process, events can be defined and updated for
each schedule line to track progress (e.g. planned loading time, actual loading time etc.).
Other types of events can be also defined, for example to record references to other
service partner and associated contracts (e.g. inspectors) as well as free-form text entries.
Recent enhancements to the TSW nomination include a new screen layout, enabling more
schedule information to be visible at one time, and new interface links to APO the links to
contracts, and functions to allow speedy confirmation status updates at time of scheduling.

Silo Management
Deals with the measurement of oil in Tanks in terms of dips in volumetric units.
1. Tanks in IS-OIL Hierarchy

2. Master data for Tanks

3. Dips

4. Worklist

5. Integration of SM with Stock

Tanks in IS-Oil Hierarchy:

Tanks come under storage locations. The storage locations used in SM are called Tank
Storage Locations.
Plant >- Storage Location >- Tank/Tanks

One or multiple Tanks can be assigned to a storage location.

Master Data for Tanks

SOC

The characteristics of Tanks are called Storage Object Characteristics (SOC).

SOC have to be assigned to a tank. Following is a list of SOC:

1) Batch
2) Valuation type
3) Material assignment
4) Sloc assignment
To assign SOC to a tank use transaction code O402.

Dips:

In order to calculate the quantity of material moved in and out of a tank the concept of dip
reading is used.
Innage

The volume occupied by the material in Tank

Ullage

The empty space in the tank

Types of dips:

There are two types of dips:

Opening and Closing Dips

The Opening dip is the height in cm/mm of material in tank prior to the movement of a
material.
The closing dip is the height in cm/mm of a material after the movement of a material into
or from the Tank.

The opening dip as well as closing dip corresponds to a certain volume in m3.

The volume of the material moved in or out of the Tank can be calculated using the
formula:

V (2-1) = V2 V1/ (H2-H1)

V (2-1) = the difference of material volume moved in or out of Tank

V2 = the volume at height 2 of a material in Tank

V1= the volume at height 1 of the material in Tank

H2= the closing height in tank

H1= the starting or opening height in tank

Entering any dip in the SAP is a posting and hence created a material document.

The transaction code to post opening or closing or both dips is O4_TIGER.

Strapping Table:

It is a table that has entries related to the volume of material corresponding to a specific
height at a specific temperature of the material.

Concept of Stop Gauge:

Shipping Accounting people to tell the Tank people when they have to stop perform the
opening dip in the stop gauge in O4TEN. The calculation of stop gauge has to be
performed in the transaction after posting the opening dip. After the actual qty is issued
from the tank, the tank people tell the shipping accounting people the closing dip and the
shipping people perform the closing dip.

QCI:

Quantity conversion Interface deals with the conversion of one unit into another in SM. A
third party product called Quantity ware supports it.

Units of Measure

There are three important units of measure used in SM:

BBL: BARRELS at 15 Degrees FAH

BB6: BARRELS AT 60 Degrees FAH

LIT: LITRES
TON: TON

Conversion:

1 BBL= 569 LITRES
1 BB6= 570 LITRES

Pumping Sheet

It is the sheet in which the users at the refinery enter all the readings for example opening
dip, closing dip, temperature, density, API (sp.gravity) etc.

Correction factors in Tanks

Floating roof correction

It is a number which is considered while calculating the volumes of material in tanks as
the floating roof of the tank disturbs the volumetric calculations specially innage and
ullage calculations.

Temperature correction factor:

The volume of the tank may change due to temperature hence the calculation of the
material in the tank may be not be accurate.

Worklist

The combination of tanks is called a worklist.

Integration of Silo Management with MM and FI

The dip postings and stock in SM has integration with IM and FI. Due to high volume
involved in the business, it is imperative that we understand the storage system in depth. A
storage tank in the industry is termed as Silo and is configured with the following
characteristics.

1. Tank Strapping/Linear-to-volume measurements:
Tank volume measurements can be made using the tank strapping/linear measurement
function. Based on the depth of the product in a tank, the conversion table can be used to
determine the corresponding volume quantity.

2. Floating Roof Correction:
The displacement of liquid petroleum product in a tank resulting from a floating roof will
be taken into account when calculating volume using the tank strapping/linear
measurement function.

3. K Factor Calculation:
Corrections for tank expansion because of temperature will be applied to volumes
obtained from tank capacity tables that are certified at a single, standard temperature.

4. Ullage / Outage Procedures:
In addition to the measurement of innage (depth of liquid in a tank), it is also possible to
carry out an ullage (outage) measurement (the capacity of the tank not occupied by liquid).

5. Tank Calibration History:
It is possible to store tank calibration history data in the R/3 system, allowing dip readings
to be monitored and captured using the correct calibration data.
User Exits in IS Oil

During my project involving IS-Oil, we used User exists which turned out to be useful
during post implementation support. We used some of these User exits in IS Oil to update
the prices in the Price tables for Crude Oil. We has to keep in touch with our SAP XI
[Exchange Infrastructure now called PI Process Integration - a toll used to connect
different systems] colleague who would get Oil prices from Platts and other agencies
from the International Market . I thought it would be useful to share with these User Exits
in IS-Oil.

User Exits:

All customer exits in Function group XOIJ.

OIJA0001 OIL-TSW: User exit for Checks in Ticket Archiving
Program
OIJA0002 OIL-TSW: User exit for Checks in Nomination
Archiving Program
OIJA0003 OIL-TSW: Archiving user exit for Display of Ticket
Details
OIJA0004 OIL-TSW: Archiving user exit for Display of
Nomination Details

OIJBPOST TS: User Exit for Post Documents

OIJGEO01 OIL-TSW: User exits for EDI Outbound
Process of Nominations
OIJGPO01 OIL-TSW: User Exits for Printing Process of
Nominations
OIJMD OIL-TSW: Customer exits for TSW Master Data

OIJNOM OIL-TSW: Customer Exits used in the Nomination
Transactions
OIJTKT Customer Exit in the Beginning of Ticket

IDoc
Supporting Transactions

WE05 IDoc Test Transaction

WE19 IDoC Transaction

SE71 SAPScript

SMOD Customer modifications

SAP IS Oil Configuration

This is a very precious document, as it will help you to configure the Marketing,
Accounting and Pricing module in SAP IS Oil. I have tried to document it using SAP
standard documentation from the IMG. It defines all the steps in the SAP IS Oil
Configuration and gives an understanding of the step required for SAP IS Oil
Configuration.

Define Quotation Types
Description
Table OICQT
This screen is used to define the various types of quotation used in the formula and
average pricing functionality. The quotation type is used with the quotation source in the
key to define a specific quotation.
Define Quotation Source
Description
Table OICQS
This screen is used to define the various sources from which quotation types will be
collected. The quotation source is used with the quotation type in the key to define a
specific quotation. Standard settings
the standard system uses data routine 1. This specifies that all quotations will be stored
in the quotation price table OICQP. This table can be found in Sales and Distribution
Master Data.
Recommendation
you may create additional routines that access other tables.
Define Quotation Data
Description
Table OICQC
This screen is used to define the various quotations for which prices will be collected. The
keys to the table are quotation source, quotation type and quotation number.
The table also stores the currency and the Unit of Measure in which the quotation prices
are quoted.
The Factory Calendar field is used to specify the days on which the quotation prices are
published.
Define format for Second level Pricing Analysis Report
Description
Table OICRD
This screen is used to define the format of the item section of the second level pricing
analysis report.
First level analysis is given in the Formula Value Display screen, from where the user can
access second level analysis.
The second level analysis report provides more detailed analysis of the formula used to
evaluate the condition type.
The report has a header and an item section. The format for both sections can be defined
using user exit routines. The default item section routine reads the entries in table
XOICRD to determine the format.
The analysis can be displayed for different levels of the formula:
Formula evaluation
A Term evaluation
B Term evaluation
Term item evaluation
The keys to the table are report number and column number. The table also stores the
fields for display, column header texts and column widths.
Requirements
these functions can only be used with Formula and Average pricing.
Standard settings
The default report supplied by IS-Oil is ROICANAL.
Notes: the report number is specified per condition type in table T685A. This is done at
detail level in the section F&A pricing analysis. This table is found in IMG:
Sales and Distribution - Define Condition types

Transaction V/06
Define Number Range for Repository Master
Description
Table INRDP
Here you define a number range within which the repository master will be numbered.
You can assign this number range in Customizing for the Industry Solution Oil & Gas
(Downstream) by choosing MAP (Marketing, Accounting and Pricing) -> Formula &
Average Pricing -> Formula Repository -> Maintain Formula & Average Repository
Control Parameters.
A number range can be defined as internal, where the system automatically assigns a
number sequentially upon the creation of a document, or as external, where a number
within the range defined has to be manually entered by a user. An external number is
indicated by the field Ext.

Transport

The number range intervals are not included in automatic recording of customizing
changes. Transports of all changes made within number range interval maintenance must
be triggered manually.
In the initial screen for number range interval maintenance, choose the function Interval ->
Transport.
Please note the information that you get when transporting number range intervals.
Activities

To define a number range, you have to create a new group:
Insert a group, to which you can assign an internal and/or an external number interval.
Specify the limits of the number range. The individual number intervals may not overlap.
Thus, every number can only occur once.
Maintain Formula & Average Repository Control Parameters

In this menu section, you determine the control parameters for the formulas in the formula
repository. These parameters control:
The number assignment for formulas, using a number range.
The selection criteria used when creating, changing and displaying formulas, which are
controlled by a table.
Standard settings
SAP delivers table OICQOIL, screen number 1410 and a number range as control
parameters.
Recommendation
SAP recommends that you do not change the control parameters.
Activities
If, based on your company-specific requirements, you need other selection criteria for
creating, changing and displaying formulas and if you need a different number range,
proceed as follows:
1. Define your own sub screen.
To do that, copy the sub screen that is available and change it according to your needs.
2. Create your own table.
3. Assign a new number range, from which the system assigns the numbers for the
formulas.
Define Copy Rules for Invoice Receipt

In this IMG activity, you can define rules for how delivery costs are copied from a
movement document to an invoice document.
You can define how delivery costs, which have been allocated for split invoicing, are
repriced.
During invoice receipt repricing, the pricing type specifies how the system processes
delivery costs, when copying them from a goods receipt to an invoice receipt.
Maintain Formula & Average Pricing User Exits
In order to make Formula and Average Pricing as flexible as possible, many of the
calculation rules that are used are specified in user exit routines and are thus fully
customizable.
All the routines for Formula and Average Pricing can be found under this menu, where
they can be created, displayed and changed.
Maintain formula & average repricing user exit
You use this user exit to control whether or not F&A conditions are to be predetermined
either when a field (attached to an F&A condition and relevant to an access sequence) is
changed during the creation of the document or when referencing documents. For
Example
If the customer sets the variable OIC_REPRICE to any value other than initial, F&A
condition redetermination is triggered at different points, because the code is activated
only if OIC_REPRICE is not initial.
Case 1: Repricing would occur each time that a field relevant to pricing condition
determination is changed while inside a document. For example, during the creation of a
sales order, changes to the Plant field, which has an F&A access sequence attached to it,
would cause condition redetermination, that is, the formula would be read from the
database and evaluated again.

Case 2: Even if OIC_REPRICE is set to X (or any value causing it not to be initial), copy
controls have priority over this setting during the creation of documents with a reference.
For example, during the creation of a sales call-off for a contract, if the copy control
between order types OR and CQ has been set to pricing type A, even though you have
asked for F&A condition redetermination, conditions remain unchanged.
Case 3: Setting OIC_REPRICE to X does not influence condition redetermination if it
involves changing of the formula itself in the repository, unless you force redetermination
with pricing type B or choose the New Pricing pushbutton.

Activities
The SAP enhancement OICREPRI is available for F&A repricing:
1. Create the enhancement using transaction CMOD.
Either create a new project or use an existing project.
2. Activate the project.
The changes only become active when you activate the project.
IS Oil Transaction Codes

The following is a list of transaction codes and logical tables which would help you to
work in IS Oil with ease.
Master Data
O402 Maintain Location Master
Sales
VK02 Maintain Pricing Condition
VK22: Maintain Quotation
VK42: Maintain Contract
VA02 : Maintain Sales Order
Nomination Processing
O4NM : Maintain Nomination
O4TM_BPB : Maintain Berth Planning Board
O4TCN : Stock Projection Engine (generate SPW)
O4TB_RDALV : Display Stock Projection Worksheet (SPW)
Shipping and Ticketing
O4TEN : Maintain Ticket
O4TENCORR : Correct Ticket
O4TENREV : Reverse Ticket
O4THN : Delete Ticket
SAP IS Oil Tables for Nomination
OIJNOMH Nomination header
OIJNOMI Nomination Item
SAP IS Oil Tables for Ticket
OIJ_EL_TICKET_H Ticket Header

OIJ_EL_TICKET_I Ticket Item
IS OIL Training Resource Plan

This is a sample of a typical Training Plan for IS-Oil TSW. Different tools are used for
training development. We used CATT tool that was an innovative idea and CATT is
normally used for Master Data migration or legacy data migration purposes. It might help
the consultants to have a quick reference while designing their training program. The
week refers to the slots in the deadline management plan during project execution. Cycle
[ASAP Roadmap].
TSW Training Resource Plan

Topic Week Resource

Training Scope Content Week10

Training Development Week12

Create Training Presentations Week13

PPT Quality Check Content Week13

PPT Quality Check Editing Week14

Create Master Data and Examples Week14

Create Customizing Material Week15

Training Material and Exercises Week16

Instructor Guide Week16

Quality Check Exercises Week17

Quality Check Exercises Edit Week17

CATT Creation Week18

Training Delivery Week17

Recommended SAP IS OIL Resources

Based on my experience of participating in IS OIL implementation I can say the SAP

Academy literature is much useful and helpful in the process in addition to Business
Process knowledge of Oil Industry. The only source would otherwise recommend is the
Help Files on IS OIL.

https://help.sap.com/

As an alternative you have either to attend SAP Academy Course of be fortunate enough
to be part of an IS OIL implementation.
Appendix
1. MM Purchasing Organisational Structure
I came across a detailed MM Configuration document during one of my SAP projects and
found it useful. I shall try to share its important contents in few posts with the readers of
my blog.
Organogram in MM Purchasing
Client:
The client is a commercial, organizational unit within the R/3 System, with its own data,
master records, and set of tables. For a business perspective, the client forms a corporate
group.
Company Code:
The company code is the smallest organizational unit for which you can have an
independent Accounting department within external Accounting. A company code
represents an independent accounting unit, for example, a company within a corporate
group (client). Balance sheets and Profit and Loss statements, required by law, are created
at company code level. You can set up several company codes in one client in order to
manage various separate legal entities simultaneously, each with their own balanced set of
financial books. You can use a special Customizing function to copy a company code.
This copies the company code specifications to your new company code.
Plant:
A plant is an organizational logistics unit that structures the enterprise from the
perspectives of production, procurement, plant maintenance, and materials planning. A
plant is a manufacturing facility or branch within a company. A Plant can be one if the
following types of locations:
Central delivery warehouse
Regional sales office
Manufacturing facility
Corporate headquarters
Maintenance plant
When creating a new plant, you can use the plant copying function, when you use this
function, the system processes the entry in the plant table and in all dependent
Customizing and system tables in which the plant is included as key.
Storage Location:
The storage location is an organizational unit that allows the differentiation of material
stocks within a plant. Inventory management on a quantity basis is carried out at storage
location level in the plant.
Physical inventory is carried out at storage location level.
Valuation Area
Valuation area is organizational level which material is valuated. Two possible
1) Company Code: Valuated at company code level, the valuation price of a material is
the same in all of a companys Plant (that is, in a company code).
2) Plant: Valuated at plant level, you can valuate a material in different plants at
different prices.
Note: valuation at plant level is mandatory if you want to use of the production either
planning or product cost accounting components, or if your system is a Retail system.
Purchasing Organization
An organizational level negotiates conditions of purchase with vendors for one or more
plants. It is legally responsible for completing purchasing contracts. You can assign the
purchase organization to company codes (centralized) and plants (decentralized) or
combination of both.
Plant Specific Purchasing organization:
A purchasing organization is responsible for procuring materials for one plant only.
Cross Plant purchasing organization
You can set up a cross-plant purchasing organization for each company code. This
purchasing organization procures material and services for all plants assigned to the
company code.
Cross Company Code Purchasing Organization
If you want to organize purchasing on a cross-company-code basis, you cannot assign a
company code to the purchasing organization in customizing. When you create a purchase
order, for example, the system asks you to enter the company code for which you want to
procure the material.

2. MM Purchasing Configuration
The following is the SAP Configuration MM Purchasing Guide. The Organogram used in
in the Purchasing sub module:

1. Create Company Code
Company code is the basic organizational unit in FI (Financial accounting) for which a
balance sheet and profit & loss account can be drawn. We create company code 9100 (A
Ltd.) which is located in country India.
For Configuration, we use the following path on SAP application screen:
SAP Menu tools > Customizing >IMG > SPRO > Execute Project > IMG
> Enterprise Structure > Definition > Financial Accounting > Define select a
company, copy, edit the data to suit your organization and country and then SAVE.
Following screen is for copy, delete check company code
Note: By selecting the second option Edit Company Code data, you have to manually
configure all the subsequent assignments. By selecting the first option all the configuration
and tables, get copied automatically along with assignments. This option should be
selected in case of rollouts.
Double Click on Edit Company Code
In the Copy option you need to
CLICK on to copy a company code from an existing company code. You can copy from
existing company code delivered by SAP.
Key in From Company code 1000 . To company code
You can SELECT a four-character alphanumeric key as the Company Code Key.
Moreover, key in the necessary parameters that are self-explanatory. Then choose edit
company data.
Position the company code select and press ZOOM icon. Moreover, edit the data.
Moreover, Save.
Click the Address ICON and change the address. Etc., and then press OK and then save.
This key identifies the company code and must be entered when posting business
transactions or creating company code-specific master data.

CLICK and Update the following required fields:
The company code should be always kept numeric.

Country: The country where company code is located and the balance sheet and income
statement that will be prepared according to that country law.
Here the company is located in India so, we have selected the country id IN (INDIA).

Currency: It is the local reporting currency of the country. In this case it is INR (Indian
rupees) since the company is located in India.
CLICK on Address and update the following fields
Click to SAVE.
Thus, company code 9100 is created.
2. Define Company
IMG enterprise Structure > Definition > Financial Accounting > Company Code
> Define Company
In the SAP system, consolidation functions in financial accounting are based on
companies. A company can comprise one or more company codes.
We will create a company for our company code 9100.
CLICK and update the following:
CLICK on SAVE

3. Assign Company Code to Company
IMG enterprise Structure Assignment financial Accounting >

Assign Company code to company
Position the company code -> Select the same and choose the company code from help.
Ex., Assign company code 9100 to company 9100
CLICK on SAVE
4. Define Plant
IMG > Enterprise Structure > Definition > Logistic-General
(Creating a plant)
CLICK on Define, Copy, Delete, Check Plant
DOUBLE CLICK on Copy, Delete, and Check Plant.
Press F6 or CLICK on Copy Icon by select any existing plant.
Copy from Plant (Std Plant) . To Plant (New Plant)
SAVE & CLICK on Go Back.
DOUBLE CLICK on Define Plant -> Position the new plant -> select the plant -> ZOOM
Change necessary fields.
SAVE & CLICK on Go Back.

5. Assign Plant to Company Code
IMG > Enterprise Structure > Assignment > Logistic-General > Assign Plant to
company code
CLICK on Assign Plant to Company Code

SELECT the Plant (go to binocular and key in the plant and Click on the selected one)
Select the plant and CLICK on Delete and SAVE
Note: This is only when you copy Plant from Standard Plant.
Again, find the Plant.
SELECT the Company.
Then CLICK on Assign
Select the Plant (check mark)
Press Enter
CLICK on SAVE.
CLICK on Go back

6. Maintain Storage Location:

IMG >Enterprise Structure >Definition >Material Management > Maintain
Storage Location.
Click on Maintain Storage location.

Key in Plant & Press
Click on New Entries (Creating new Storage Locations)
or
first select the available storage locations and then Click on copy icon and change the
storage location and description and save and go back.
Key in Sloc. & Description

Click on Save.
Click on Go Back

7. Maintain Purchase Organization
IMG >Enterprise Structure >Definition >Material Management > Maintain >
Maintain Purchase Organization
Click on Maintain Purchasing Organization
Click on New Entries
Key in Purch. Organization (only max of 4 characters)
Click on Save
Click on Go Back
8. Assign Purchasing Organization to Company code, Company & Plant
IMG >Enterprise Structure >Assignment >Material Management
Click on Assign purchasing organization to company code
Select the company code for which the Pur. Org to be assigned. > Click on Assign >
Check the

Purchase Organization > Click on SAVE
Click on Assign purchasing organization to plant
Find the plant and delete and Save.
Find Purch Org and select and then Click on assign > Check on plant > SAVE
Click on Save.
Click on Go Back
Assign Standard P.O to Plant:
Find the plant >In Pur Org column Press F4 and choose the plant > SAVE.
3. SAP Physical Inventory

This is a description of the Physical inventory procedure to set up and carry out the
different physical inventory methods.
Inventory Method

In SAP, the Physical inventory method is assigned at the Storage Type level [except in
cycle counting]. All of the inventory methods are executed within the Storage Type. Note:
When you take annual inventory, the entire storage type is blocked for movement and all
bins are counted.

Continuous and Annual Inventory

In Continuous inventory and Cycle counting; only the affected storage bins are blocked
for movement. When you select continuous inventory, you are counting the bin and you
must count all quants within that bin. When you select cycle count, you are infact counting
the material, wherever that material is within the storage type/s selected. In the case of
mixed storage, all quants within the bin must be counted. [A quant is the combination of
Material and a Storage Bin]

When you clear differences in WM, any discrepant amount is written to the interim
storage type for differences and the bins are unblocked. You then clear differences in IM
to adjust the inventory balance and create the accounting document. Warehouse inventory
data is year-dependent and must be reset at the beginning of a new inventory period.

The Continuous or Annual Physical inventory is distributed over the entire year. When it
is carried out on a continuous basis, up to date information about the correspondence
between the warehouse stock and the book inventory is always available. Continuous
Inventory and WM Cycle counting in the Warehouse Management system makes it
possible for you to separate materials into classes (e.g. A, B, C) and take inventory for
each class separately several times throughout the year.

Configuration for Cycle Counting
In the Inventory Management IMG under Physical Inventory, define the cycle counting
indicators and the number of times per year that inventory counts are to be taken for each
class.

Enter the cycle count indicator (A, B, C) into the Storage View of the material master
record for each material that will be counted using the cycle counting task.

Stock Placement and Removal:

The SAP system sets the inventory indicator for the storage bin the first time
Stock Placement is done in the storage bin for that fiscal year. The indicator is set when
the transfer order is confirmed. Transfer orders provide proof of movement following the
inventory.

The transfer order for Stock Removal is printed with a notice that zero stock check is
active for a specific bin. The zero stock check must be verified when the transfer order is
confirmed. If the warehouse worker determines that the storage bin is not empty, the
actual quantity remaining is entered at confirmation of the transfer order. The system
carries out the correction of stock using the interim storage type for differences. The
difference must be cleared from WM and recorded in IM.
Update in the Physical Inventory

During the update process, the SAP system reads the count results and reads any changed
book inventory balances and book values.

4. WM Organisational Hierarchy
This is the WM Organogram in Standard SAP

The Organisational Structure is the most important element in SAP WM. It is the link
between the Inventory Management in MM and WM. It helps you understand all the
movements whether they are internal Warehouse movements, Goods Placements or Stock
Removal etc.

The warehouse structure in Warehouse Management is hierarchical. The following are the
important elements in WM Hierarchy.
Warehouse Number

It is used to define a complex warehouse complex in WM. This Number is used in all
warehouse movements.
Storage Type
Each of the warehouse consists of areas that make up the warehouse complex. These
areas called storage type. A Warehouse can have physical as well as logical storage
types. Each storage type is divided into storage sections. A storage section generally
includes all bins that have certain characteristics in common depending upon their use.
Storage Bin
Each storage type and storage section consists of a row of storage spaces that are called
storage bins in WM. The coordinates of the bins tell us what materials need to be stored in
them.
Quant

The quant is the combination of a material and a storage bin.
5. Third Party Order Processing

The SAP Academy documentation has really explained the third party order processing
very well. During my study, I learnt a lot from it other than practice on the SAP system.
Here is a gist of the third party processing for those who are interested. In the third-party
order processing, your company does not deliver the goods ordered by the customer.
Instead, you pass on the order to an external vendor, who then sends the goods directly to
the customer and sends the invoice to you. The purchase order of your customer is entered
in a sales organization of your company as a sales order. Afterwards, a purchase order for
the external vendor is created in your company.
Third party order processing is initiated when you enter a sales order with a third-party
item. Either the order consists partially of third-party items or all the items in the order are
third-party items. Depending on how your system is configured in Customizing, thirdparty item categories can be determined automatically by the system for the respective
materials. However, so that you can process materials that you normally deliver yourself
as third-party items, you can manually change a standard item into a third-party item by
entering the respective item category.
During automatic scheduling of third-party order items, the system takes into
consideration:

1- Planned delivery time from the material master, that is, the time the vendor requires
delivering the goods.

2- Purchasing department processing time, that is, the time the purchasing department
requires to process the third-party orders, is also included.
Note: The purchasing department processing time is assigned to the plant in Customizing.
In standard Customizing for sales (IMG), the system is configured so that a purchase
requisition is automatically created in purchasing when you save the sales order to the
database. Here, a separate purchase requisition item is automatically created for each
third-party item. While creating the purchase requisition, the system automatically
determines a vendor for each requisition item.
In the sales order, you can make subsequent changes to the quantity and delivery date for a
third-party order item. The changes you make are automatically copied into the respective
purchase requisition, provided the release status of the purchase requisition still allows
this.
The purchase requisition has the account assignment for the sales order. This account
assignment cannot be changed in the purchase requisition. The sales

documents control include the sales document type, the item category, and the schedule
line category.
You create third-party order items by creating a standard sales order (for example, sales
document type OR for a standard order) and Item category TAS for third-party order
items. The sales order can consist of further third-party order items or items with other
item categories. The system is configured so that Schedule line category CS is
determined for third-party order items.
For the most part, the item category depends on the sales document type and the item
category group of the material. The two other factors, that is, item usage and the item
category of the superior item, are of minor importance in third party order
processing. Assign the item category group BANS (third-party item) to materials
whose sales are processed solely as third-party orders. The item category determined by
the system can be changed if you have defined allowed alternatives in Customizing.
In the standard system, schedule line category CS (third-party) is used to process thirdparty order items. Since third-party order items are not supplied by your company, you do
not have to post the goods issue in your system. Therefore, the schedule line category CS
in Customizing does not contain a movement type and is not set as being relevant for
delivery. The Customizing settings for schedule line category CS needs
1- Document type for the purchase requisition,
2- Item category (with internal character representation) and
3-account assignment category.
When a purchase order is created, the created purchase order appears in the document
flow for the sales order. Third-party order items in purchase orders are marked with item
category S. Third-party items must have an account assignment. In standard SAP, account
assignment category X is used.

Map the business process such that the entry of the vendor invoice receipt is only possible
if a GR for the PO was entered in the system beforehand. You post the GR only when the
vendor reports to you that they have performed the delivery.

If GR is provided for in your business process for third-party order processing, you can
only post the invoice receipt after you have entered the goods receipt into the system. As
soon as the invoice receipt is recorded in the system, the customer is billed. Since no
outbound delivery exists in the system for third-party order items, you set the indicator for
Order-related Billing during selection of the documents to be billed.
In the copying control for sales document to billing document, the standard setting for the
third-party order item category defines that the quantity from the invoice receipt
document, not the order quantity, for example, is copied into the billing document (Billing
quantity field).

A Rare Guide To SAP SD

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

A Rare Guide To SAP SD

Uploaded by

Copyright:

Available Formats

A

Rare Guide to SAP SD & Basic IS-Oil

Phase 5: Go Live and Support

approved BBP shall be charged as per the agreed customization rate.

SAP Project Management Reports

Write sap enhancement if required

2) Define customer classifications.

A new customer group is created.

Define Goods Receiving Hours

Fields in Customer Master

PARVW5 Sales employee C

SD Shipping and Transportation

Transportation Planning Point : A Location or a group of people

2. Receiving Invoices from service agents and posting them as invoices in FI

Person or company that places an order for

Person or company to where we deliver

Person or company to where we send the

Person or company who pay the

The main customer is a logical parent

The employee is responsible for

Pricing Master Data

Identify the characteristics of a condition. For example, in pricing, different

production, procurement, maintenance, and materials planning. A plant is a place where

Return Order Process

Sales and Operation Planning

Cross Modular Configuration

> Strategy Types

Sales and Operation Planning [SOP]

Info Structure in SOP

Sales and Operation [SOP] Configuration

Testing and Training

Missing Functionality If Yes, explain:

Cut over Plan

screen, double clicking on the last item:

How to use CATT in SAP

The following Procedure explains how it is done in the system.

24) Press Tab button on the keyboard twice.

SAP Training Module

Sales Information System

2. Under Organizational data, enter Sales Organization.

SAP Configuration Template

SD Month End Closing

SAP SD Transaction Codes

Customer Master Tables - KNA1, KNB1, KNVV, KNKK, KNVP

Entering SAP Community

Does delivery-scheduling back from required delivery date?

Settlement Run Credit Memo Request Remove Block Credit Memo

> Strategy types

> Create SOP Plan [MC93]

> Inbound or Outbound deliveries

E Is part of the Sales Area

C All existing Invoices are updated

Linked documents are called:

C Item number counter

Which of the following statements are TRUE:

Equally good for preparing Certification also.

Oil and Gas Industry

of barrels of oil products.

IS Oil TD Master Data

TD TD Master Data Define Routes

Define bulk shipment

SAN TSW PIPELINE

No. range Int.