A Rare Guide to SAP SD & Basic is OIL

7/25/2019 A Rare Guide to SAP SD & Basic is OIL

1/152


2/152

A Rare Guide to SAP SD & Basic IS-Oil

Knowing the rare

Faizullah Khan


3/152

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


4/152

SD Certification

Recommended Books

SAP IS OIL

Oil and Gas Industry

IS Oil TD Master DataTSW 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


5/152


6/152

SAP MethodologyASAP Methodology of Project Implementation

SAP recommends that you use ASAP as a standard methodology for implementationplanning and for implementing SAP software. The ASAP Roadmap provides a step-by-

step guide to implementation. During the five phases of an ASAP project, the results ofeach phase are recorded in specific documents. This is particularly important in Phase2. 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 ofmembers from both the SAP Client and the SAP Implementation Team or ConsultingCompanys 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 todetermine the business requirements needed to support these goals. A detailed documentcalled the Business Blueprint document consisting of both the AS IS situation of theClient Business processes and the proposed TO BE mapping in the SAP system isdocumented in this document. The document is duly signed by the Clients BusinessProcesses Owners [BPO].

Phase 3: Realization

The purpose of this phase is to implement all the business and process requirementsidentified in the Business Blueprint. You configure the system step-by-step in the BaselineConfiguration 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 successfullycompleted this phase, you will be ready to run your business in your production system.


7/152

Phase 5: Go Live and Support

Transition from a project-oriented, pre-production environment to a successful and liveproduction environment.

Details of SAP Project using ASAP Methodology

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

Phase 1: Project PreparationDuring this phase, our team will prepare and conduct a project kick-off meeting with theProject

Team of Client. We will execute an initial project planning and preparation for the ERPimplementation.

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 variouskey managers and officials of Client to define project objectives, scope, and schedule. Inaddition, the relevant business process scenarios will be defined. In order to document theresults gathered during the business requirement workshops, we will create a BusinessBlueprint (Implementation Document). It is the Client responsibility to give writtenfeedback and schedule workshops on BBP. If the Client does not respond within 10 daysof BBP submission, it shall be then considered as approved. Any changes from the


8/152

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 clientbased on the Business Blueprint. Other key focal areas of this phase will includeconducting all integration tests and drawing up end user documentation. It is Clientresponsibility to provide all relevant Master Data in prescribed form on the datemutually agreed in the project plan. Any deviation/delay in hand over of Master Data willbe charged at as per agreed customization rate. Client shall be responsible for DataCleansing and Preparation Activity.

Milestones:

Validate Business Requirements

Implementation of Business Requirements

Integration & Acceptance Testing

Plan End User Training

Phase 4: Final Preparation


9/152

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

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

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-productionenvironment to live operation. Go-Live means day on which first transaction is added intothe system. The most important elements of this phase will include setting up systemsupport, monitoring system transactions and optimizing overall system performance.

Milestones:

Go-Live

Support Operation

Handover Administration

Support Plan


10/152

SAP Project Management Reports

I had the opportunity of reading stuff on SAP Project Management Reports when I becamethe team lead for an implementation. I found the material important and added with itmy 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 thatare 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 SAPimplementation,

2- Describes the progress w.r.t project objectives,

3- The progress towards the milestones [Accelerated SAP Roadmap- also called ASAPRoadmap in SAP Project],

4- Deliverables set for the period and5- 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

ustification 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 normallywith 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


11/152

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 planaccording 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 publicationby 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, aproject logo and a reference to the project public website.


12/152


13/152

SD ConfigurationBusiness Blueprint Document

The following is the structure of a practical Business Blueprint Document. You can copypaste 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 besigned by the Client.

Module Name:

Release:

Prepared By:

Date:

1. Blueprint Agreement

Signing this document records your agreement to the contents of the Blueprint, andconfirms 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.


14/152

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


15/152

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




16/152


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


17/152


18/152

SD Configuration Template

For those interested to know about the order and constituents of SAP SD ConfigurationSteps in the Implementation Management Guide [IMG] of the Standard SAP, This is just aquick Reference. If you are a new entrant into SAP or a junior consultant you will have torefer to IMG a lot as each screen you see on the SAP System screen is configured andcontrolled from the IMG. Moreover, this reference will help you know the practical

concepts helpful in configuring the SAP SD successfully. Just reading the standarddocumentation from the Help portal of SAP [help.sap.com] is quite boring and needs a lotof 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


19/152

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 bulkpurchaser).

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


20/152

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 thepurpose of pricing or generating statistics.


21/152

Purpose

You can freely define customer groups according to the needs of your organization. Youassign 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 conditiontype that lets you create pricing records for customer groups. Additionally, when you wantto 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


22/152

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 applypricing conditions. When you want to generate sales statistics, you can use sales districtsas 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


23/152

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


24/152

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


25/152

Fields in Customer Master

Creating customised reports for a client is an essential part of any SAP implementation asthe Standard SD reports are usually not sufficient for mapping their business processes into the system. For SD implementation, the knowledge of certain master data helps ingiving the functional specifications of the reports to the ABAPers [programmers]. In theSales 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 importantfield mapping of Customer Master along with their type [C or DYMD or CURR] andlength of each field as well as whether they are marked Mandatory in the IMG.

Customer Master

Field Name DescriptionType Length Mandatory

KUNNR Customer NoC 10KTOKD Customer Account Group C

4COUNTRY Country KeyC 3REGION Region C

3TITLE_MEDI Title C

15NAME1 Name 1 C

35NAME2 Name 2 C

35NAME3 Name 3 C

35NAME4 Name 4 C

35

CITY1 CityC 35

PO_BOX P.O.Box. C10

POST_CODE2 Postal codeC 10

SORT1 Search Term C20

LANGU Language Key C

1STREET StreetC 35TEL_NUMBER First telephone number


26/152

C 16

FAX_NUMBER Fax numberCURR 31

HOUSE_NUM1 House number C 7

TEL_EXTENS ExtCURR 10

FAX_EXTENS Ext ExtCURR 10

SMTP_ADDR Email 1C 53

REMARK Notes 1 C53


REMARK Notes 2 C

53SMTP_ADDR Email 3C 53

REMARK Notes 3 C53


REMARK Notes 4 C53

ANRED Form of Addr C30

NAME1 Name Contact Person C28

NAMEV First Name Contact Person C35

NAME_LAST Last Name Contact PersonC 28

TEL_NUMBER Telephone No Contact Person

CURR 16TEL_EXTENS Ext Contact Person

CURR 7

MOB_NUMBER Mobile No Contact PersonCURR 24

FAX_NUMBER Fax number Contact PersonCURR 31

FAX_EXTENS Ext Contact PersonCURR 10

ABTNR Dept. Contact PersonCURR 4

VTEXT DescriptionC 20


27/152

PAFKT FunctionCURR 2

VTEXT DescriptionC 20

Accounting View

BUKRS Company codeC 4ZUAWA Key for sorting according to assignment numbersC 3BUSAB Accounting clerk

C 2

AKONT Reconciliation Account in General LedgerC 10KNRZE Head office account number (in branch accounts)C 10ZTERM Terms of payment keyC 4VZSKZ Interest calculation indicator

C 2ZINDT Key date of the last interest calculation

DYMD 8ZINRT Interest calculation frequency in months

C 2EIKTO Our account number at customer

C 12ZSABE User at customer

C 15KVERM MemoC 30

FDGRV Planning groupC 10XAUSZ Indicator for periodic account statementsC 1DATLZ Date of last interest calculation run

DYMD 8XZVER Indicator: Record Payment History ?

C 1ALTKN Previous Master Record Number

C 10MGRUP Key for dunning notice groupingC 2TLFXS Accounting clerks fax number at the


28/152

customer/vendor C 31PERNR Personnel Number

C 8INTAD Internet address of partner company clerk

C 130MABER Dunning area

C 2MAHNA Dunning procedureC 4

MADAT Last dunned onDYMD 8MAHNS Dunning levelC 1

Sales View

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

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

KZAZU Order combination indicator C1

VSBED Shipping conditions C2VWERK Delivering plant C 4

VKBUR Sales office C4KKBER Credit control area C 4

PARVW1 Bill to party C 10

PARVW2 Ship to party C 10PARVW3 Payer C 10PARVW4 Main customer C10


29/152

PARVW5 Sales employee C10KUKLA Customer Class C 2WAERS Currency CURR3


30/152

Pricing in SAP SD

SAP Pricing is considered one of its strengths. It is used in multiple applications inConfiguration of both SD and MM. The Multinationals and ex- CMM Level 5 companiesuse a complicated pricing schema in their business that cannot be handled by ordinaryERP solutions in the market. SAP does the job efficiently. However, for SAP Consultantsit 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 aboutPricing 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 PricingElements

Pricing Procedure : It is used to determine valid condition record

Pricing Procedure Determination: Sales Area, Customer Pricing Procedure, Sales DocPricing Procedure

Header Conditions : Header conditions are automatically distributed among Items.

1. Header Conditions has to be marked as Group Condition in order to be distributedamong Items

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


31/152

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

Procedure in the IMG

Pricing in Billing : Pricing can be done again at billing level using followingPricing 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 remainingpricing 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 exclusiongroup and

The others are de-activated

4. The cumulative value of a condition can be tracked and displayed in a conditionrecord


32/152

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 distributedamong items

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

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


33/152

SD Shipping and Transportation

Shipment Processing consists of the following

1. GR for Inbound or GI for Outbound

2. Create Shipment document3. 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


34/152

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


35/152

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


36/152

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 Distributionmodule, 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 thecustomer.

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.

DivisionA 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 OfficeA physical location (for example, a branch office) that has responsibility for the sale of

certain products or services within a given geographical area.


37/152

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.


38/152

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 netprice and a discount that refers to a gross price.

Condition Record


39/152

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 bechanged 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 ProcessingThe 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 defaultdelivering 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 orderto 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


40/152

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 outbounddelivery 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 oran 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 canuse 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.


41/152

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 DocumentWhen you create a billing document, data is copied from the sales order and the delivery

document to the billing document.


42/152

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


43/152

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


44/152

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 inthe 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 groupThese 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 PlanningSales & 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.


45/152


46/152

Cross Modular ConfigurationSD Batch Management

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

User Exits used toMaintain 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


47/152

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 orLogistics> 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 > Characteristicsor

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

Customizing related to Batch Management

Activity


48/152

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 ActivateStatus 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 ofMeasure

Batch Determination

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

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

> Access Sequences



49/152

> Strategy Types

Logistics - General > Batch Management > Batch Determination and Batch Check> Batch Search Procedure Definition

Logistics - General > Batch Management > Batch Determination and Batch Check> Batch Search Procedure Allocation and Check Activation

Logistics - General > Batch Management > Batch Determination and Batch Check> Activate Automatic Batch Determination in SD


> Define Selection Classes

Logistics - General > Batch Management > Batch Determination and Batch Check> Define Sort Rules

Logistics - General > Batch Management > Batch Determination and Batch Check> Maintain Batch Allocation Strategy Number Ranges


50/152

Sales and Operation Planning [SOP]

Sales & Operations Planning (SOP) is a flexible forecasting and planning tool with whichsales, 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 ofindependent requirements. In turn, this data is fed to Master Production Scheduling [PP-MP-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 forsales 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 anyorganizational level, and define the content and the layout of the planning screens. Youcan process your planning data from the standpoint of almost any organizational unit (forexample, 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 scopeto track previous planning data, anticipate market demand, run analyses, and performwhat-if simulations. A series of mass processing functions automate the planning of largevolumes of data.

Scope of SOP

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


51/152

Info Structure in SOP

The Sales & Operations Planning (SOP) application is based on information structures. Aninformation structure is a statistics file containing operational data. This can be eitherplanning data you anticipate will happen or actual data that happened. Aninformation 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 Planningmenu. With Standard SOP,you work with just one organizational unit, the product grouphierarchy, 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 carriedout in Flexible Planning, on the other hand, can be based on any information structure ofyour choice, either a self-defined information structure or a standard informationstructure. This means you can plan any combination of organizational units and any keyfigures. In addition, you can design your own planning table layouts, known as planningtypes. You can also maintain plans using the Planning menu in the logistics informationsystems.

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

Three planning methods are available:

1. Consistent planning

2. Level-by-level planning

3. Delta planning


52/152

Sales and Operation [SOP] Configuration

In one of the implementations in my career, we had to map the Sales andOperation Planning requirement of the company into SAP and give them the futureprojection. A Pharmaceutical company had multiple Pharmacies across the country.Hence, it was extremely important for them. We worked over the functionality so much inthe 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 willhelp you in SOP functionality.

The Structure MCVBRP is appended by ABAPer to include the required Key Figures usedin 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)


53/152

Testing and Training

SAP UAT TemplateUAT stands for User Acceptance Test. UAT is an important activity in the ASAPMethodology used for SAP Implementation. It is a very tense and intense activity as thekey users and some experienced end users mostly raise their objections on the TO BEDesign agreed upon in the Business Blueprint. It often witnesses unpleasant momentsbetween 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 ofthe Business process owners while explaining their business requirements and deeptransactional 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 scenariosused 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


54/152

Setup Data To be entered by Key Users

Special Requirements Unique or specific requirements that need to be emphasized forconfiguration. 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


55/152

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 IfYes, explain:


56/152

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
https://www.blogger.com/


57/152

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 aweek. It is essential from business point to inform all the business partners about the downtime in advance. Therefore as a part of preparation, it is recommended to send thisinformation 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 theapplication components. Since production machine will be connected to client network, itis necessary to test this connectivity in advance. In addition, all printers will also beinstalled 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 requiredformat 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 tomake sure all activities related to Go Live have been performed and system is ready to goin Production.

Support after Go Live

To support the users after Go Live, helpdesk will be established. All the calls from userswill 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


58/152

team (FI, CO, MM, SD, and BW) for the solution. Support team will then base on priority

look into the issue.


59/152

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 takenfrom the copy of QA Client into the Training Client so that the End Users can practice thenew transactions in the SAP system. The Training Client is usually refreshed after acertain interval when the data is consumed in case the number of End Users is huge and allhave 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 usedin the raining exercise.

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

2- Note that the headings of the columns are infact the variables used in the trainingdocument.

This data source contains data for 6 sets of data in total. So the merged document willhave 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 isrecommended to divide this document into smaller sets to utilize less memory resources ofcomputer and hence fast editing or of the document.

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

Training Exercise


60/152

1- It is the real source document of SAP training material to be created in bulk for the endusers 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 valuesacquire 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 valuesfrom 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


61/152

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 Enterbutton

6. Enter the Quantity recounted 270.

7. Click on the Enterbutton

8. Record the message at the bottom of the screen

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

10. Click on the Savebutton

11. Record the message at the bottom of the screen

12. Click on the Exitbutton 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.


62/152

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 givenbelow:

System Services Catt Record

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

Legend: Z = all test cases normally start with Z, SCM = the area in which you arecreating the CATT,

MM01= the transaction code used to create a material master.

3) Click on the TCDbutton

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

5) Enter Industry Sectorand Material typeand press enter.

6) Select the viewsand organizational structureand press enter.

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

8) Click on the Savebutton.

9) Another window will pop up. Click on the local objectbutton after deleting anyvalue in the development class.

10) Click on the back button.

11) Click on the Changebutton now.


63/152

12) Double click on theTCDbutton.

13) Click on the Field List.

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

15) Enter &descriptionin 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 (inthis 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 deleteanyvalue in the Default valuefiled 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 thefile 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 valuesotherwise its always stored in SAPworkdir by default.

22) Click on the Transferbutton

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


64/152

24) Press Tab button on the keyboard twice.

25) In this column now enter all the values for the variable (in this case &description) foras many sets as needed. Please note that the values should be in the same column and notin 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) SelectLong radio button under the Log typesection.

29) SelectBackground radio button under the Processing Modesection.

30) Selectexternal from file radio button under the Variantssection.

31) Click on the Choosebutton. 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 inthe background and now these materials are ready for use. If there is an error then theresult is, be a Red color for that material otherwise Green color shows that the CATT wasexecuted successfully.


65/152

SAP Training Module

1- It is a detailed document about a transaction or a group of transactions used in thebusiness.

2- It is based on the Business Process Script. It explains every minute details in non-ASAPmethodical 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 anothermodule for into Goods Receipt for Purchase Order or Delivery (MIGO) and even onemodule for a couple of similar reports like LB10, LB11, LB12.

3- The module transaction has to have the business scenario as well as detailed SAPscreen 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 transactionCS03to display a material bill of material (BOM).

Business Procedure

A bill of materials (BOM) is a complete, formally structured list of components that makesup 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 BOMitems. The Material Standardization Division (MSD) creates bOMs.

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

The following BOMs can be created in SAP:

Material BOMs


66/152

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 bechanged.

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 boldfacetype. Optionalfields are

labeled in ordinary type.

Fields not listed below should not be used.

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


67/152

Note: The Plant field should not be entered, as BOMs will always be group BOMs.

Click on the Enterbutton.

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

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 theNext screenbutton to view the data for the other components.

After all necessary data has been viewed, click on theHeaderbutton.

Note: To display further information, click on the following tabs: Further data,Admin. data, Doc. assignment.

To exit this transaction, click on the Exitbutton until the initial R/3 screen is displayed.


68/152


69/152

Sales Information SystemSales Information System SIS Setup

In order to enable postings in SIS for Info Structure S430, the following steps are carriedout:

Activate Update

IMG -> Logistics - General -> Logistics Information System (LIS) -> Logistics DataWarehouse -> 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); notethat there is no option to set the reporting period split for S430, because it records statisticsby document item, there is no aggregation within reporting periods.

Check SIS settings for statistics groups

IMG -> Logistics - General -> Logistics Information System (LIS) -> Logistics DataWarehouse -> Updating -> Updating Control -> Settings: Sales -> Statistics groups,

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

Check item level update groups

IMG -> Logistics - General -> Logistics Information System (LIS) -> Logistics DataWarehouse -> Updating -> Updating Control -> Settings: Sales -> Update group -> Assignupdate 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, materialstatistics group, document statistics group and item category.


70/152

Check header level update group

IMG -> Logistics - General -> Logistics Information System (LIS) -> Logistics DataWarehouse -> Updating -> Updating Control -> Settings: Sales -> Update group -> Assign

update group on header level,

Check that update group 00001 (SIS: Sales Document, Delivery, Billing Document) isset for the required combinations of sales area, customer statistics group and documentstatistics 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 validupdate group assignment has been made.

Document item material must have a statistics group (MVKE-VERSG) for which a validupdate 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) -> LogisticsData 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

IMG -> Logistics - General -> Logistics Information System (LIS) -> Logistics DataWarehouse -> 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.


71/152

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.


72/152

2. Under Organizational data, enter Sales Organization.

3. For this example, no SD transactions need to be entered. For a list of transactions, clickon 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 (forexample, 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 > billingdocuments > 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 theoutput screen.

5. Optional: Choose further sel. criteria to select additional selection criteria.


73/152

6. Choose Enter.

List of All / Open Deliveries


Logistics > Sales and distribution > Shipping and Transportation > OutboundDeliveries > 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 dateon 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 leftside of the screen are those that are to be displayed.


74/152

SAP Configuration Template

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

Configuration document

Release My SAP ECC5.0

Prepared By:

Date: Month [MM] Day [MM] Year [YYYY]

Table of Contents

1. Document Control2. General Settings3. Enterprise Structure4. Document Number Ranges Overview5. Business Transactions

Document Control

General Settings

The configurations can be made in this menu path:

Example:

Sales Org path in IMG


75/152

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


76/152

Maintain number ranges for orders

Example:

Order Master Data > Maintain number ranges for Orders

Order Type

From Number

To Number


77/152

SD Month End Closing

Month End Closing is the first litmus test of successful Go Live in an SAP Project. Mostmodules and especially SD, MM and FI are involved in this intense practice, as the figuresin the reports should be reconciled to give an accurate picture of results. After one monthof post implementation, the client as per their business practice to reconcile figures inSales 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 practicesof the SAP Customer, the following steps are recommended as SAP SD month-end closingActivities:

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. Notethat 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.


78/152

SAP SD Transaction Codes

Whether it is configuration or Training during an SAP implementation, you need toremember some tables and transaction in order to ease your job. There is some logicbehind these transaction codes too and with experience you know them if you are a keenobserver. The following is a list of such transaction that will help you appreciate SAPlogic 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


79/152

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]


80/152

Entering SAP CommunitySAP Consulting Skills

Consulting skills include Analytical skills, Communications skills, interpersonal skills and

documentation skills.

Analytical skills helps you to analyses business processes and business scenariossystematically and the ability to translate them into the SAP framework.

Training Skills include presentation skills, language skills and knowledge of third partytraining development tools like Resite, DDS, SnagIt etc.

Interpersonal skills are a tool to work in a team as SAP is an integrated solution andconsultants 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 isrequired 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 withknowledge of tools like SolMan [Solution Manager] in addition to working under pressureto meet ticket resolution deadlines.

Knowhow of Tele-commuting Technologies is an asset when a consultant needs to workfrom a remote location via phone, mobile, skype or video conferencing etc. A consultant issupposed to know these state of the art technologies to offer his/her services to the clientto get required info from the client, any other team member or perform the requiredknowledge transfer [KT, as we call it] to the client.


81/152

Example An SAP Presentation

I had the opportunity of delivering a presentation at a seminar and used thefollowing Seminar Agenda for the participants. I thought it might be helpful for someconsultants 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 SAPbut 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


82/152

Remote System Access

Question Answer Session


83/152

SD Interview Tips

Sales Order [VOV8]:

Doc type, No R

A Rare Guide to SAP SD & Basic is OIL

Documents

Transcript of A Rare Guide to SAP SD & Basic is OIL