sap sd doc.pdf

8/10/2019 SAP SD DOC.pdf

1/54

Day 1 :- Company Plant Storage Loca

Company Code

SALES AREA Sales Organization Shipping Point

Distribution Channel Division

Sales Office

Sales Group Sales Person

Company code to sales organization 1 to n

Sales organization to distribution channel n to n

Sales organization to division - n to n

Sales area to sales office - n to n

Company code to plant - 1 to n

Plant to storage location n to n

Plant to shipping point n to n


2/54

Definition:-

Enterprise Structure SD Definition

Sales Organization

Distribution Channel

Sales Office

Enterprise Structure Logistics-General Definition

Division

Plant

Location (Storage Location)

Enterprise Structure Logistics-Execution Define Shipping Point

Sales Office is just for MIS purpose.

(All FI transactions in SAP hits at the Company Code & Plant Level)

Storage Location can be different because of physically of different places and (2) material type can bedifferent e.g. manufacturing material, trading material etc. (Materials can be broadly distributed into 4types: 1. Finished or manufactured material or Trading material (FERT) 2. Raw Material (ROH) 3.Service Material (DIEN).

The only tab in which both the Definition & Assignment of storage location falls under the definitiontab of SPRO.


3/54

ASSIGNMENTS:-

SD ASSIGN

Sales Organization to company code

Distribution Channel to Sales Organization

Division to Sales Organization

SET UP SALES AREA

Sales Office to Sales Area

Sales Group to Sales Area

Sales Organization ----- Distribution Channel ----- Plant

Sales Group is on HR level

Customer is always created on Company code & sales area.

Why we assign the 3 Sales Organization ----- Distribution Channel ----- Plant?

1) When we create customer than the plant tab is there, if we do not assign the 3, the integrationis not possible.

2) During a creation of a Sales Order I have to mention a plant which specifies the delivery.

Logistics-General Assign plant to Company Code

Logistics-Execution Assign Shipping Point to Plant

Company is always of 6 alphanumeric digits

Company code is of 4 alphanumeric digits

Sales Organization is of 4 alphanumeric digits

Distribution Channel & Division is of 2 alphanumeric digits

Storage location, Plant, Shipping Point is of 4 alphanumeric digits

Sales Office & sales Group is of 4 alphanumeric digits


4/54

SATGES OF SAP IMPLEMENTATION:-PROJECT PREPARATION (when you study the project)

GAP ANALYSIS

AS IS & IS AS

BLUE PRINT (complete details of the project)

REALIZATION (customization stage)

FINAL PREPARATION (integration testing)

LEGACY SYSTEM MIGRATION (migration data)

2 tools for this stage 1) LSMW LEGACY SYSTEM MIGRATION WORKBENCH

2) BDC (BATCH DATA COMMUNICATION) for ABAP

GO LIVE

POST GO LIVE SUPPORT


5/54

3 TIER ARCHITECTURE:-

DEVELOPMENT CLIENT (1-Customization & SPRO work done here, 2- BASIS raises TR)

SAND BOX (this is for checking whether TR is correct or not)

QUALITY CLIENT (1-Buffer Storage and 2- Unit Testing)

PRODUCTION CLIENT (Live)

There is only 1 Sand box for basis team requirement / Quality Client can be 2 or 3 / Production Clientis 1


6/54

SAP R/3:-

Enter the data ------------ SAP GUI (Presentation Layer ) -------Front End

(Application Layer) -------ABAP (Tables / fields / Structure)

(Database Storage) ---------SAP Server (BASIS)

Presentation Layer

Various devices could be used to access SAP business software. For example: desktop, mobile devices, laptops, andso run. This device would be called a presentation layer. You might have to install a piece of software on these

devices so that they could talk to the application server (computer running the actual SAP software). You could alsouse your web browser to access SAP application. Whatever the case may be, the front end device would

communicate with the application server. The device would simply display you a presentation layer while theapplication is actually running on the application server. The device is also called a "client".

Application ServerThe actual SAP software runs on an application server. Client node simply displays the image of the screen that is

actually being produced on the application server. It is important to note the application server only runs SAPsoftware. Data is not stored in application server

Database Server

Data is stored on a separate machine called database server. Presentation layer communicates with applicationserver to retrieve the screen image to be displayed to the user. Application server in turn communicates with the

database server to write data to the database and to retrieve data from the database. The database server would behosting a database management system like Oracle. Oracle is the most popular choice of database to be used with

SAP software. Other databases could be used as well e.g. SQL Server (from Microsoft) and DB2 (form IBM).


7/54

TABLES FIELDS

SALES ORDER VBAK (Header) CustomerSold to partyPO.No.Date

VBAP (Item) MaterialQuantityPlant

BILLING VBRK (Header) PayerBilling dateBilling Type

VBRP (Item) MaterialMaterial Amt.

DELIVERY LIKP (Header) Material typeMaterial Quantity

Ship to partyDelivery datePGI (post goods issue)

LIPS (Item) ItemItem category

T CODE SE16 helps us to see the data of VBAK, VBAP, VBRK, and VBRP

PO stands for Purchase Order

PGI is Post Goods Issue which means the actual delivery date & hits the inventory a/c. (when click on PGI date; the

amount delivered to the customers shows.)

During PGI SD & MM integration takes place in 2 ways:-

1) Inventory is reduced.2) Inventory a/c is debited.


8/54

Day 2:-

Customer A/C Group :- (4 digits)T- Codes for Customer

1) XD01 Customer Data including all fields2) VD01 SD related customer data

Views maintained by XD01:-

1) General Data : Customer NameCustomer AddressTelephone noCountry Code

Customer ClassificationNeilson ID

2) A/C ing Data : Reconciliation A/C (Recon A/C)3) Sales Area Data: Sales Tab (sales element data)

Shipping Tab (Delivery plant stored here) Billing Tab (payment term of a customer stored) Partner Functions (SP, SH, BP, PY)

When a SO is created, SP is there, during delivery SH is there and during invoice BP is there.

When invoice is created and saved then the screen transfers to accounting document. A/c ing information of acustomer is stored in a payer.We cannot maintain a/c ing data in VD01

Customer Master Relevant T- Codes:-

1) OBD2 ----- T- Code for field behavior2) Xd01 ----- customer data for all3) XDN1 ----- when we click on XDN1 in command prompt : 3 tabs are there,

a)

Interval : display mode, not modifiable b) Status: Scale of no. range & current customer no. c) Interval: We can create & modify no. range here. Current no. range would be 0.


9/54

CUSTOMER A/C GROUP:

When we put XD01 in command prompt then the first tab is A/C group, it is also called customer a/c group.

Uses of Customer A/C Group

Customer A/C Group :- (4 digits)

1)

Customer Master Data (Field Behavior) 2) No. Range of a CustomerIt helps in determining that a field can beMandatory/ suppressed/ hidden or not in use

Customer A/C group maintains the Field behavior (customer master data) & specifies the no. range of a customer.

Types of Customer A/C Group in an organization:-

1) Domestic Customer A/c group : Used in normal sales cycle2) Export Customer A/c group : Used in Export sales cycle3) One time sale Customer A/c group: used in cash sales cycle.

SPRO Path for creating/ changing customer a/c group:

SPRO

FI

A/C Receivable/ Payable

Customer a/c group

Master data preparation

Create no. ranges

Assign no. ranges


10/54


11/54

MATERIAL MASTER RECORD:-

MM01 Material Master CreateMM02 -- Material Master ChangeMM03 Material Master Display

Sales relevant views in Material Master:-

1) Basic Data12) Sales Organization Data13) Sales Organization Data 24) General/ Plant Data5) General Plant Data/ Storage 16) General Plant Data/ Storage27) Accounting1

Most important fields:-

BASIC DATA 1(a) basic unit of measure (unit of measurement of material)(b) Division (of sales organization) (1 division has many materials)

SALES ORGANIZATION DATA 1(a) Sales unit (measurement in which goods are sold)(b) Minimum order quantity (minimum amount customer needs to order)

SALES ORGANIZATION DATA 2(a) a/c assignment group (it specifies the material is either manufacturing or trading type)(b) item category group (used for item category determination)


12/54

SALES: GENERAL PLANT(a) gross weight (it includes the weight of the packaging also)(b) net weight (It determines the freight charges)

PLANT DATA/ STORAGE 1

(a) storage condition (for storage location determination)

PLANT DATA/STORAGE 2(a) weight unit (unit of gross/ net weight)(b) volume weight

ACCOUNTING 1(a) valuation class (basically used for inventory a/c ing)(b) moving price

MATERIAL MASTER CREATION STEPS:-

MM01

ENTER

VIEWS WILL ARISE

CLICK ON VIEWS

CLICK ON ORGANIZATIONAL DATA/ LEVEL:PlantSales organizationDistribution Channel

MATERIAL INDUSTRY SECTOR MATERIAL TYPEa) Finished goodsb) Trading goodsc) Servicesd) Raw material


13/54

Day 3:-

Pricing Procedure:-

CONDITION TABLE

V/03

V/04

V/05

V/07Xxxx

V/06Xxxx

V/08Xxxx

001

002

003

ACCESS SEQUENCE

01 001 Sales org + Customer + Material

02- 003 - Sales Org + Customer

03 002 Sales Org

CONDITION TYPE

PR00

PRICING PROCEDURE

PR00 Price

KF00 Freight MASTER DATA

K005 - Discount


14/54

PRICING TECHNIQUE:-

a) Condition Tableb) Access sequence We have to configurec) Condition Type these 4 steps d) Pricing Proceduree) Pricing Procedure Assignment We will assign preceding 4 steps here f) Master Maintenance Power user & End user work on it

CONDITION TABLE:-

Condition table are cluster of pricing fields which are required to create an access sequence inthe pricing technique.

NOTE: Sales Organization should always be present in condition table.

T-Codes for condition table:-

Sales Area Customer PricingProcedure

Document PricingProcedure

Condition Record (/NVK11)

V/03 - Create condition table

V/04 - Change condition table

V/05 - Display Condition table


15/54

Looks like:-

Creation of condition table (steps):-

V/03

Enter

Table no (e.g. 951, 967 ---we can put table no from 900 to 999 in SAP ECC 6.0)

Enter

Available fields

Double click on the fields to choose (e.g. sales organization, customer etc.)

Click Generate Tab

Yes

Ticket System arises

TABLE

SELECTED FIELDS FIELD CATALOGUE

SO SOMaterial Material

CustomerEtc.

968 no


16/54

ACCESS SEQUENCE:

Access Sequence is a step wise combination of condition tables (or fields) that is requiredto create a condition type.

T Code for access sequence is V/07 --- Create Access Sequence

Looks like:-

Access Sequence

Access

Fields

ASCQ DESCRIPTION CATEGORY DESCRIPTIONA111 XYZ 1/2

AC TABLE DESCRIPTION REQUIRED

10 600 ABC

A111

600 10

Condition I Doc.STR

Doc.Field

LongField

.. ..` ..


17/54

Creation of Access Sequence Steps:-

V/07

Enter

Click on new entries

AS Description Type Description

Retail accesssequence

Enter

Select whole line

Click access

Select new entries

Put table no (e.g. 951 &967 & description)

Select first line

Double click on fields

Enter


18/54


19/54

(Based on (+) (-) everything is describe)

Click on each and every fields &put on the basis of condition class

Put access sequence that we created before in the screen

Save

Division of Manual Entries:-

1) No limitation2) Free3) Automatic entry has priority4) Manual entry has priority5) Not possible to process manually

MASTER MAINTENANCE:-

Master maintenance is used to create condition records for different condition type.

T Codes for Master Maintenance:-

ondition classrice, dis, tax,m)

Plus/ Minus Calculation Type Rounding Rule Manual Entries

VK11 Create Master Maintenance

VK12 Change Master Maintenance

VK13 Display Master Maintenance


20/54

Steps to create Master Maintenance:-

VK11

Enter

Click on condition type

Put condition type we have taken before for access sequence

Enter

Click 1st one

Enter

Put Sales Organization

Put Customer

Search on customer

Put customer name (*more*)

Enter


21/54

Enter

Save

Steps to Change Master Maintenance:-

VK12

Condition type

Enter

Select any one

Enter

Click on clock sign

Materialgroup

REJC

Amount

100

Unit

INR

Unit(BUM)

M2

Valid From

17/9/2012

Valid to

29/2/2013


22/54

Steps to Display Master Maintenance:-

VK13

Condition type

Enter

Select any one (you have to select from the condition tables)

Enter

PRICING PROCEDURE:-

Pricing procedure is a systematic input of condition type . Standard pricing procedure for salesis RVAA01. & T- code is V/08.

Pricing procedure skeleton view:-

Price (+)Discount (-)Tax (+)Gross amount (price discount + tax)

NOTE: - Condition type that we created will be used in pricing procedure

80% of work is done by SD consultant20% of work is done by FI consultant


23/54

Steps to Create Pricing Procedure:-

V/08

Enter

Click on any one

Click control

Step Co Condition type Description

Price

Discount

Total

ELEMENTS:-

What are the 2 elements SD consultant uses in pricing Procedure?

SD consultant puts condition type & FI consultant puts a/c key of condition types created by SDconsultant.

PRICING PROCEDURE ASSIGNMENT:-

Pricing procedure is done in:-

Sales Area + Customer Pricing Procedure + Document Pricing Procedure;

Therefore, Sales Area + Customer Pricing Procedure + Document Pricing Procedure = Pricing Procedure.

Pricing Procedure always comes in Sales Order.


24/54


25/54

Day 4:

DIFFERENT DETERMINATION

PROCEDURES:

PLANT DETERMINATION:

SALES ORDER

Plant Delivery

Shipping Point Picking Point (Storage Location)

Plant Determination is mandatory and is always there.

Plant Determination is determined in a hierarchical basis:

1) CMIR : Customer Material Information Record

2) CMR : Customer Master Record3) MMR : Material Master Record

CMIR Is a combination of a customer master & material master.

SHIPPING POINT DETERMINATION: (is always there)

Shipping Condition (CMR) + Loading Group (MMR) + Plant (Determined) = Shipping Point

(Sales: General Plant)

STORAGE LOCATION / PICKING POINT DETARMINATION:

Storage Condition (MMR Plant Data Stor 1) + Shipping Point + Plant = Storage Location / Picking PointStorage condition in the MMR is never maintained, the MM people keep it blank, usually picking point is

not determined, we give it manually during delivery time, and as per industry requirement storagelocation is kept blank by the MM.


26/54

ITEM CATEGORY DETERMINATION :( How a material behaves e.g. profit, service, demo)

Sales Order Document Type + Item Category Group (NORM) + Usage (Blank) + Higher Level ItemCategory (TAN) = Proposed Item Category (TAN).

NOTES:

The first two are important (Sales Order Document Type + Item Category Group)Item Category Group is NORM in most cases (from MM)Usage in 90% cases is kept blank (is for background calculation)TAN Costing Material, TANN is Free Goods, TAX is servicesHigher Level Item Category for hierarchical maintenance like TAN1, TAN2 TAN3 (combination of thesethree gives proposed Item Category TAN)

SPRO Pathway:SPRO S/D Sales Sales Document Sales Document item

Enter Enter Data New Entries Assign

CMIR allows following things:a) It helps to give a customer specific name to the material.b) It helps in plant determination.c) It helps in determining minimum material quantity that we want to store in our plant.d) It helps in fixing the cap of part deliveries.

Note: Maximum part deliveries should be 9 because for maximum of 9 times any customer can get itsdelivery from a vendor for one Sales Order.

CMIR VD51:-

VD51 Enter (Customer, Sales Organization, Distribution Channel) Sales Document

Enter First screen appears, enter material no. Enter

Automatically material description arises


27/54

SALES ORDER DOCUMENT TYPE: (VOV8) IMPORTANT BUTTONS:-

a) Sales Order Document Category

Order(C) Credit Memo (K) Debit Memo (L)

b) Number Assignment / System of a Sales Order : Number Rangec) Item No. Increment (specifies the serial number e.g. 10, 20 etc.) Number scaled) Reference Mandatory (100 10 discount = 90). Say suppose the given discount should be 5

instead of 10, then raise a credit memo of 5 i.e. Reference to billing document. Whencredit/debit note is created then select (M) - it stands for with reference to billing document.

e) Probability Probability of sales order converts into Billing, maximum time it would be 100%(Probability is for MIS)

f) Output Application : for output determination, how printout of SO will come

g) Document Pricing Procedureh) Screen Sequence Group Determines screen of SO (for ABAP)i) Delivery type j) Billing Type BILLING TYPE

Delivery Related Billing Order Related Billing (SO Credit Note)(SO Delivery PGI Invoice) (When there is no movement of material(When material movement takes place) e.g. credit/debit note)

Item Category document Type: (VOV7)

a) Pricing : Determines whether an item will have a price or will be free e.g. TAN or TANNb) Billing Block : It specifies that the material having this item category will be blocked for invoicing.c) Billing Relevant : Is used to maintain that the material is relevant for billing or not.d) Determine Cost : Should always be ticked . It determines the manufacturing or trading cost of

that material. It determines the cost price .


28/54

Day 5:

Incompletion Procedure:

Incompletion procedure generally checks the incompletion of the document; or it gives the control for acertain document to be complete in order to run that particular document. (The fields that is mandatoryin Sales Order that we define by Incompletion Procedure)

PATH:

SPRO S/D Basic Function Log of Incomplete Item

Define Incompletion Procedure

Assign Incompletion Procedure

What are the levels in which we can define Incompletion Procedure?

1) Sales Header2) Sales Item3) Sales Schedule Line4) Delivery Header5) Delivery Item6) Sales Activity

7) Partner

Incompletion Procedure:

Group Description

A Sales Header Select ItBC

Procedure

Incompletion Procedure Description

10 Enquiry

Select 20 Standard Orders


29/54

Fields

TABLE FIELD NAME DESCRIPTION SCREEN STATUS WARNING SEQUENCE

VBAK AUDAT DOCUMENTDATE

KKAU 01

NOTES:

Screen - is done by ABAP and is automaticallyStatus group is a pre defined SAP group that specifies in which the level the status of the fields will be

checkedWarning will always be ticked

We can assign Incompletion Procedure on T- Code VOV8

2 basic use of Incompletion Procedure:

1) It specifies the fields for which the user must enter the values during processing e.g. Sales Order.2) Determines the fields that appear in the incompletion log when the data is missing & throws

away the particular screen.

OUTPUT DETERMINATION:

Output Determination is an assignment of a Sales Document type (Sales Order, Delivery, and Billing) toits Output Printout.

XYZ (Document Title)

123

(By ABAPers)

Company CodeCustomerMaterial


30/54

PATH:

SPRO S/D Basic Function Output Control

Output Determination using Condition Technique Output Determination

What are the levels in which Output Determination can be maintained?

1) Sales Activities2) Sales Document3) Billing documents

Maintain Output Determination

Select

Control Data

New Entries

Step Condition Type (ABAP)

Assign Output Determination

V1 Is a kind of application of S/D which is SAP standard, which contains the cluster of differentprocedure (output procedure, a/c determination procedure)


31/54

SALES CYCLE:Inquiry Quotation Sales Order Delivery Billing

Pre-Sales (No a/c ing workIs done & is only for MISPurpose)

CONTRACT: Contract is a modify form of Sales Order which has a valid from & valid to dates. There are2 types of contract:

a) Quantity Contractb) Service Contract

SALES CYCLE:

Sales Order Delivery PGI Invoice A/C Entry

Pre Requisites of a Sales Order:

a) Customer Codeb) Material Code

c) Quantityd) Pricee) Delivery Plant

Pre Requisites of a Delivery:

a) Material Codeb) Picking Quantityc) Ship to partyd) Delivery Plante) Storage Location

For PGI to happen we have to complete the 5 steps of delivery, if not done PGI does not takes placePGI is a step in which inventory is reduced.


32/54

Pre Requisite of an Invoice:

a) Delivery No.b) Bill Datec) Bill to party

d) Net Amounte) Tax

A/C Entry:

a) Payerb) Amount (Net &Tax)

A/c is always posted on payer.

Day 6:

CREATION OF SALES ORDER:

Customer code no.

Delivery Plant

Material Quantity Price Tax SO Date1) ABC2) XYZ

3)

XXX

Price is alwaysper/ piece

VAT- 12.5%CST- 2%

Valid From Valid to

SO date is importantVAT is always 12.5% (the tax within the state)CST is always 2% (the tax is outside the state and within the country)SAP condition type for VAT is JIVPSAP condition type for CST is JCST

T Codes to check the inventory stock of a plant:

1) MB5B Gives you the information of all the stock available in a plant2) MMBE Gives you the information for the breakup of that material stock, storage location wise

(stock of one material).


33/54

How to check the stock of the material by using T Code MMBE & MM5B?

Plant Material FromDate

To Date OpeningStock

TotalReceipt

TotalIssueQuantity

ClosingStock

BUM

3041 - 7/10/2012 7/10/20102 10 +2 (add) -5(delivery)

7 M 2

Steps: - (MB5B)

MB5B

Material no (Keep it empty)

Company Code (CPIL)Plant (3041)Date (7/10/2012)

Execute

Steps :- (MMBE)MMBE

Select Stock (For selecting Ctrl + Y)

Paste (for paste Ctrl +V)

Execute

Taxes (VAT & CST) are always payable for Sales and receivable for Purchase.


34/54

Tax maintains:

VK11

(JIVP for VAT) & (JCST for CST)

Plant

Customer

12.5% / 2%

Enter

Tax

Up search *KOL* vat payable (place e.g. KOL)

Enter

Steps to create Sales Order:

a) Customer Creationb) Condition Table Creationc) Access Sequence Creationd) Pricing Proceduree) Master Maintenance (VK11)

Price Maintain (ZA00 Condition Type, VK13 Display Master Maintenance) Tax Maintain


35/54

Pre requisite of Sales Order:

Customer code: 0011000017Material code: CM00048RDelivery Plant: 3041

VK11: ZA00, JIVPDate: 7.10.2012 - 7.10.2012

Creation of Sales Order: VA01

VA01

Order type (ZAGR order type would always be given)

Enter

Customer code (0011000017)PO No. 12234Require Delivery Date (7.10.2012)

Enter

Material Code

Quantity

Unit of Measure

Plant

Enter


36/54

` Double click on material

Condition

Order ReasonSO no (1734110425)

Whenever you create a SO the pricing date & the required delivery date should always be the same.

DELIVERY: VL01N

SAP standard you cannot do delivery on a Sunday. To do a delivery on a Sunday put a date forward toopen the screen & then change the date to Sunday.

VL01N

Date

GO TO

Header

Processing

Change the date to 7.10.2012

Billing date changes automatically

Shipment


37/54

1) Means Transport Type 2) Transaction Id. code (truck no.) 3) Route (west)

Enter

Back

Picking

Picked quantity

Picked Status

PGI (it gets automatically saved)

Delivery no (8234110418)

Display SO: - VA03 (to delivery through SO)

VA03

SO No (open)

Enter

Sales document

Delivery


38/54

Billing: VF01

VF01

Delivery No (automatically / if not then enter)

Enter

Save

A/C DETERMINAT ION: VKOA

How is a/c determined through VKOA?

1) Application: V (it is for S/D)2) Condition: KOFI(without costing assignment) & KOFK (with costing assignment)3) Chart of A/C: Company code4) Sales Organization5) Plant6) Division7) A/C assignment group: for customer8) A/C assignment group: for material9) A/C key: Pricing procedure

The combination of all the above will determine G/L a/c in which the revenue of the bill will be postedPurpose of a/c determination is to generate the a/c ing document of the bill.


39/54

Day 7:-

Notes:-

MB5B is the T- Code to check the stock of the material

During creation of a Customer you should always maintain the customer pricing procedure

V/08 is for pricing procedure.

Sales Order:Condition Analysis Pricing Procedure assigned to SO Open (V/08)

Pricing Procedure:-

How many columns are there in a pricing procedure?

There are 16 columns in a pricing procedure.

The important columns are:

1) Steps : Is basically the hierarchy in which the condition type in a pricing procedure is assembled.E.g. Price- 10, 20, 30

Discount 40, 50, 60Tax 70, 80, 90Gross Amount 100

2) Condition Type : In a single pricing procedure only one price condition type can be maintained

3) From : It determines the step of the condition type on which the calculation of existing4) To : condition type can be maintained.

5) Manual : Is the control which determines if a condition type can be manually maintained or not.(if we have not maintained the price in VK11 then the price will not flow)

6) Required : The control which makes the any condition type mandatory.

7) A/C Key: Is used for a/c ing determination of a condition type. The same is maintained in VKOA.

8) Accrual Key: used in rebate condition type. The accrual key is linked to G/L account in VKOAwhere the accrued amount is stored. The standard Accrual Key in ERU.


40/54

Text Determination:-

Text determination is always used for MIS purpose.

Before creating text determination, you have to create Sales Order & before saving, GOTO Header

Text Determination:-

VA01

GO TO

Header

Text

The White Box- Is for one text type, standard we can maintain 365 alpha numeric characters.

Delivery:-

Delivery Forecasting:-

There are 3 types of delivery forecasting:

1) Forward Scheduling : - The date calculated from the day of production to the date of delivery.Here the delivery date is determined based on material requirement in a plant.

2) Backward Scheduling : - Is determining the delivery date based on customer requirement,accordingly the production and the material requirement planning is determined.

3) No Scheduling : - Is for maximum Retail Sector. During holidays (which are maintained in factorycalendar) no delivery is possible.

In 3 types of Delivery Forecasting there are 5 steps (dates):

1) Picking2) Transport Planning3) Loading4) Planned GI5) Delivery Date.

Based on these 5 steps (date) billing date is determined.


41/54

Day 8

COPY CONTROL:-

Copy Control is certain key/controls which determine the values which are to be copied from SalesOrder to Delivery and from Delivery to Billing.

SALES ORDER

(VTLA)DELIVERY

(VTFL)BILLING

VTLA ZAGR (Select) Magnify Header

1) Header:-a) Order Requirement : Are certain pre- requisite which should be present in a Sales Order for a

delivery to happen. E.g. an order should contain material quantity, delivery plant, etc. for adelivery to happen. 001 is the SAP Standard routine for Order Requirement.

b) Combination Requirement: Are SAP provided routines which specifies/helps to combinemultiple orders into one single delivery. It helps in combining multiple sales orders into onesingle delivery by controlling certain features like all the sales order will have the same customer

and the delivery date would be the same etc. 051 is the SAP standard routine for combinationrequirement.c) Copy Item No.: Sales Order (10, 20) then in Delivery it will be (10, 20) the hierarchy will be the

same.

2) Item:-a) Order Requirement: In Header and Item both the order requirement are the same, its just

that this is used for Item Data. b) Update Document Flow: Controls the flow of the documents

(Sales Order Delivery Billing) and it controls that the documents are beingprocessed or completed.

c) Positive & Negative Quantity: Specifies that the order to delivery is forward or backward. When SO Delivery (positive+)When SO Return Delivery (negative-)For e.g. standard SO +ive / -ive quantity would be plus (+) andIf it is return SO +ive / -ive quantity would be minus (-)


42/54

DELIVERY BILLING (VTFL)

VTFL ZAGR (Select) Header Magnify

1) Header: a) Copying Requirements : Are routine which manages to club multiple deliveries into one billing.

003 is the SAP standard routine for copying requirements.

b) Assignment/ Allocation No. Are basically used for identifying the Sales Order/ Delivery/

c) Reference No. Purchase Order No. of the bill. They flow in the HEADER of the bill.

d) Copy Item No.: Sales Order (10, 20) then in Delivery it will be (10, 20)

2) Item: Item ZTAN (select) Magnifya) Data VBRK/VBRP: Are routines which controls the header/item values in a bill for e.g. we can set

the routine 011 to specify the bill date = Today (current date)

b) Billing Quantity : Checks that the quantity which flows in the bill should not exceed delivery/order

quantity.

c) Positive & Negative Quantity: Specifies that the Delivery to Billing is forward or backward.

d) Pricing Type: It controls how the price which flows in the invoice behaves.

D copy pricing elements unchanged.

e) Pricing Source : Is the document source from which the price in a bill flows.


43/54

CREDIT MANAGEMENT:

Credit Management enables to set credit limit per customer and how the system response if thecustomer credit limit exceeds.

There are 2 types of Credit Management:

a) Centralized Credit Managementb) Decentralized Credit Management

Centralized Credit Management:

CPIL

Credit Control Area (CCCA) [there is only one CCCA]

Code1 Code2 Code3 Code4

Decentralized Credit Management

CPIL

CCCA1 CCCA2 [there are more than 1 CCCA]

Code1 Code2 Code3 Code4 Code5 Code6


44/54

Step 1: Create new CCCA: T code is OB45

OB45 Click on any one & copy Change Name & Currency Enter

Save

Step 2: Assign CCCA to Company Code: T code is OB38

SPRO S/D Basic Functions Credit Management & Risk Management

Credit Management

Step 3: Define Credit Groups

Step 4: Assign Sales & Delivery Document to Credit GroupClick Select

Step 5: Define automatic Credit Control[CCCA + Risk Category + Credit Group]

Step 6: Master Maintenance

Master Maintenance How to maintain a credit limit for a customer? FD32

FD32

Customer

Credit Control Area

Enter

Click on all the boxes

Enter

Enter

Enter


45/54

DAY 9:

FREE GOODS:

Free Goods are of 2 types:

a) Inclusive Free Goods : Where you get the same quantity for what you have order for, but at aless price. E.g. 100pc Order Delivery 100pc Billing 80pc (as 20 pc wouldbe given for free for an order of minimum of 100pc) 80pc TAN and 20pc TANN

b) Exclusive Free Goods : Where you get more quantity for what you have ordered for but payingthe same price. E.g. 100pc Order Delivery 120pc Billing 100pc (100 pc TAN &120pc TANN)

Item Category for free goods is TANN (where there is no price)

Master Maintenance of Free Goods Condition Type

VBN1 Create

VBN2- Change

VBN3- Display


46/54

SALES DEAL/ PROMOTION:

Sales Deal / Promotion are any kind of discounts or benefits which are given for a specific period owingto a specific occasion.

STEP 1: We have to create a Sales Promotion. T- Code VB31

VB31 Promotion Type (Define validity period, condition type & table) Enter

Save Create Promotion Screen (enter validity & description) Enter Sales Area Data

Promotion XX Created

STEP 2: Sales Deal: T- Code VB21

VB21 Type of Sales Deal Enter Create Sales Deal (Description/validity/promotion/condition)

Sales data created save

STEP 3: Add the promotion Condition Type KA00 in the pricing procedure.

SAP standard condition type for Sales Deal/ Promotion is KA00

STEP4: Run the Sales Order as usual.

NOTE: Fill/ maintain the condition type KA00 with the material on which the promotion would be given.

In Sales Promotion we have to give:

a) Validityb) Name of the Sales Promotion e.g. Diwali Bonanza and any comments of the sales promotion which

is needed for MIS purpose.

Sales Deal is created with reference to a Sales Promotion it contains the condition type KA00 and itsmaster maintenance i.e. the materials with the discount and its validity period.


47/54

Rebate:

Rebate Agreements are a form of special discount paid retro actively to a customer. This discount isbased on the sales volume of a customer over a specific period of time.This rebate discount is only relevant if the customer purchases the required volume

E.g. XYZ (customer) has a target of 200,000 coke bottles (material) in one year.Completing the target of 200,000 bottles the customer gets a 10% discount on his purchase.The customer completed the target of 200,000 bottles on Oct. then on the customer purchasesOn Nov. 500 bottles being CP is 20000 Discount is 2000/-On Dec. 1000 bottles being CP is 40000 Discount is 4000/-Total discount being 6000/- at end of the year the customer gets a credit note / cash of 6000/- from thecompany.

Configuration of Rebate Agreement: (VBO1)Step 1 Define Agreement Type

Agreement Type consists of:a) Validity periodb) Condition Table (customer, material and rebate/discount).

Customer/ Material Rebate

Proposed Valid From

Valid To

Payment Method

Verification Levels

Manual accrual Order Type

Manual Payment

Payment Procedure

Partial Payment

Settlement

Final settlement


48/54

1) Payment Method defines that the rebate amount paid to the customer can be partial ormanual or final settlement.

2) Verification Levels determines the levels in which the user can see his accrual rebate amount.3) Manual accrual Order Type determines the order type of a rebate credit note.4) Manual Payment

a) Payment Procedure determines that the credit note can be issued manually orautomatically

b) Partial payment determines the order type of a partial payment.5) Settlement

a) Final settlement determines the level after which a credit note can be issued.

In which levels we have to activate the rebate processing?

We have to activate the rebate in

a) Billingb) Sales Organizationc) Customer Master


49/54

Partner Function:-

SPRO S/D Basic Functions Partner Determination

Set up Partner determination

In how many levels we can determine partner functions:-

In 8 levels we can determine partner functions:-

1) Customer Master2) Sales Document Header3) Sales Document Item4) Delivery5) Shipment6) Billing Header7) Billing Item8) Sales Activity

Customer A/c Group

PARTNER DETERMINATION PROCEDURE

Partner Function (SP, SH, BP, PY)

Partner Function can be1) Non-modifiable i.e. the partner function in the customer master is a grey out field and the same

cannot be modified.2) Is mandatory i.e. the partner functions should flow in the customer master otherwise the customer

master cannot be saved.


50/54

TICKET SYSTEM:-

There are 2 types of changes in SAP:

1) Config Changes OBD2, V/06, Partner Function2) Master Changes - XD01, XD02, VK11, VK12, XDN1

DEVELOPMENT CLIENT (closed)

SANDBOX TESTING

QUALITY CLIENT

PRODUCTION CLIENT (open)

SE10 is the T-Code to check what are the tickets generated.

SE10

Modifiable Which have not been released (cannot be modified)Released Have been released

TICKET

Config Tickets (Basis) SOLMON Tickets(That is raised by the consultant)


51/54

Configuration Level changes that are raised by a consultant create tickets.

SOLMON is Solution Manager Tickets:-These are the tickets which are raised by the end users when they face any kind of difficulties.

These tickets should be solved by the consultant.

To raise SOLMON ticket:

HELP

Create Support MessageThe component of a SOLMON Ticket is a T-Code specific.

SOLMON ticket

Development Production

I have solved production based SOLMON tickets for master data & very few development basedSOLMON ticket (a/c group suppress)


52/54

Customer Practical:-1) Create Customer

2) Extend a customer to different Sales Area

XD01 Put Customer Reference (1001, 50, 11) Sales Area (1001, 40, 11)

3) New no. series starting with 19

XDN1 STATUS SELECT & CHANGE THE NO.

Can a no. series be changed after a customer is created with that no. series?

Yes we can change in XDN1, but it will throw an error stating that no. series can only be changedduring initial entry.

4) New Partner Function to the existing customer master

a) Create normal customer with the same name but address would be different

b) Open XD02 with the previous customer and then go to Partner Function tab

c) Specify whether (SP, SH, BP, PY)

d) Save

5) Block the customer

XD05 Only Customer All Company Codes Tick on the boxes Save

Sales Practical:-1) How to delete a Sales Order?

VA02 Sales Order No. Sales Document Delete

2) How to delete a Delivery Order?

VL02N Deliver Order No. Outbound Delivery Delete

3) How do I check the document flow of a Sales Order?

VA03 Sales Order No. Enter F5

4) VF11 is the T- Code to cancel the invoice

VF11 Billing Document No. Save


53/54

LOGISTICS EXECUTION

Logistics Execution is divided into 3 parts:-

1) Transportation VT01N (transport challan)2) Shipment3) Route Determination for MIS & CIS purpose

1) TRANSPORTATION: VT01N is the process to generate a delivery challan.

VA01 VL01N (Delivery No.) With a delivery no. we can create a deliveryVF01 challan through VT01N

a) Delivery challan consists of materials, its quantity, truck no., shipment no., drivers name etc. b) In VT01N we can create the delivery challan through 2 process:

Collective Processing (CP): It is a creation of one delivery challan of multiple deliveriesSingle Processing (SP): one delivery = one challan (creation of one delivery challan withone delivery)

2) SHIPMENT: It is the process of calculating the cost of the shipment. This follows a differentpricing procedure .The cost is dependent on the weight of the material.

3) ROUTE DETERMINATION: It is the process of determining the route, which are given manuallyduring the creation of the delivery.

VOV6 is for schedule line category MASTER DATA. CP is the schedule linecategory for normal Sales Cycle.

Check the MOVEMENT TYPES


54/54

MOVEMENT TYPES:

I) Sales Order Delivery PGI 601 II) Sales order Delivery REVERSE PGI 602 (T.Code VL09) III) Initial entry of a stock through MB1C 561/562(Cancel) IV) STO PGI 641 V) STO REVERSE PGI 642 VI) One storage location to another storage location stock transfer 341 VII) One storage location to another storage location stock transfer (REVERSE) 342 VIII) Post Goods Receipts PGR 342 IX) MIGO 301

MIGO PROCESS:COMPANY (Factory or Branch):-

1) Stock Transfer Order (STO) (ME21N)2) Delivery (by factory against STO) (VL10B)3) PGI (VL02N)4) Proforma Invoice (created against delivery) (VF01)5) MIGO (the receiving branch does a MIGO based on delivery)

RANCHI (Branch): the receiving branch makes a STO

Proforma Invoice: is the invoice generated during Stock Transfer Order (STO) as this invoice does notgenerate any revenue for the company, it is not a/c ing relevant.

FB03 is the T- Code to check any a/c ing documentSTO Delivery Proforma Invoice (Not a/c ing) MIGO

sap sd doc.pdf

Documents