SAP Sales & Distribution Module

OTC Boot Camp – FTR Batch (Jan-March 2011)

Prepared by: Kaushik Sarkar

Document Number: OTC-2011-0001

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Table of contents
Day 4: 01-Feb-2011 .......................................................................................... 17
1.0 Customizing the Sales Document type ........................................................... 17
1.1 Create a Sales Document type.................................................................. 17
1.2 Assign Sales area to Sales Document type .................................................... 17
1.3 Partner Determination procedure for Sales Doc type ....................................... 17
1.4 Pricing Procedure Determination in the sales order ........................................ 18
1.5 Required Delivery Date proposal in the sales order ......................................... 19
1.6 Purchase Date Proposal in the Sales Order ................................................... 19
1.7 Sales Document Numbering ..................................................................... 20
1.8 Item Increment ................................................................................... 20
1.9 Item Category Determination ................................................................... 21
1.10 Customer Material Info Record – Tcode VD51 ................................................ 22
1.11 Plant Determination in the Sales Order ....................................................... 26
1.12 Shipping Point Determination .................................................................. 30
1.13 Incompletion Log ................................................................................. 35
1.14 Text Determination (Tcode VOTXN) ........................................................... 43
Day 5: 02-Feb-2011 .......................................................................................... 48
2.0 Customizing the Sales Document type ........................................................... 48
2.1 Check for Purchase Order number in the sales order ....................................... 48
2.2 Enter PO Number ................................................................................. 50
2.3 Item Division ...................................................................................... 51
2.4 Sales document block ............................................................................ 52
2.5 Incomplete Messages ............................................................................. 54
2.6 Schedule Lines .................................................................................... 55
2.7 Schedule line category .......................................................................... 58
Day 6: 07-Feb-2011 .......................................................................................... 61
3.0 Customizing the Sales Order ....................................................................... 61
3.1 Reference Mandatory ............................................................................ 61
3.2 Check Division..................................................................................... 63
3.3 Common Distribution Channel / Division for Master Maintenance ........................ 65
3.4 Combine Sales Organizations ................................................................... 68
3.5 Alternate Sales document type ................................................................. 69
3.6 Product Attribute check in the sales order ................................................... 71
3.7 Item Proposal ..................................................................................... 75

L&T Infotech - Confidential Page 2 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

3.8 Default Delivery Block in the sales order ..................................................... 81

3.9 Default Billing Block in the sales order........................................................ 82
3.10 Shipping Conditions in the Sales Doc type .................................................... 83
4.0 Customizing Item Category ........................................................................ 83
4.1 Business Item...................................................................................... 83
4.2 Weight Volume Relevant ........................................................................ 88
4.3 Defaulting Billing Block at the item level ..................................................... 91
4.4 Pricing .............................................................................................. 92
5.0 Schedule Line Settings .............................................................................. 92
5.1 Default delivery block in the schedule line................................................... 92
6.0 Pricing Condition Technique....................................................................... 93
6.1 Customize a condition table – V/05............................................................ 94
6.2 Create an access sequence: Tcode V/07 ...................................................... 97
6.3 Create a condition type – V/06 ................................................................ 100
6.4 Creating Condition records for condition type – VK11 ..................................... 100
6.5 Create Pricing procedure with condition type Y888. – V/08 .............................. 101
6.6 Determine the pricing procedure in the Sales Order – Tcode OVKK...................... 102
6.7 In the sales order, the price gets automatically picked up ............................... 102
6.8 Linking Condition table to the Condition Type .............................................. 102
Day 7: 08-Feb-2011 ........................................................................................ 104
7.0 Pricing ................................................................................................ 104
7.1 Pricing with multiple condition tables in an access sequence ............................ 104
7.2 Importance of Exclusive Checkbox in the Access Sequence ............................... 107
7.3 Condition Class of the Condition type ........................................................ 108
7.4 Pricing Procedure with multiple condition types of condition class B (PRICE). ........ 109
7.5 Condition types with Condition Class A (Discounts & Surcharge) ......................... 110
7.6 Discount Condition type with Calculation type Percentage ............................... 112
7.7 What happens when you don’t put FROM in the percentage discount................... 114
7.8 Statistics Field in Pricing Procedure .......................................................... 115
7.9 Creating sub-totals in pricing Procedure (From / To) ...................................... 116
7.10 Manual Checkbox in Pricing Procedure ....................................................... 118
7.11 What happens when you select Checkbox Required (Discount condition types) ?
– To be checked.................................................................................. 119
7.12 What happens when you select checkbox Manual and Required ......................... 119
7.13 Sub-Totals in the Pricing Procedure (KZWI1 to KZWI6) .................................... 121
7.14 Viewing Sales Order Pricing in database ..................................................... 123
7.15 Viewing Condition records in database....................................................... 124
7.16 Requirement Routine ........................................................................... 127
L&T Infotech - Confidential Page 3 of 730
 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

7.17 Concept of Condition Base value and Condition Value ..................................... 128
8.0 Condition type Settings ........................................................................... 129
8.1 Plus/Minus ........................................................................................ 129
8.2 Calculation type – Quantity .................................................................... 130
8.3 Calculation type – Gross Weight ............................................................... 131
8.4 Calculation type – Fixed Amount .............................................................. 132
8.5 Changes which can be made – Item Conditions ............................................. 134
8.6 Changing the calculation type in the sales order ........................................... 135
8.7 Deleting Condition types in the Sales Order ................................................. 137
8.8 Deleting Condition Records .................................................................... 138
8.9 Condition Record Validity Proposal during VK11 ............................................ 139
9.0 Delivery Processing – 17.20 hours .............................................................. 140
9.1 Configure Delivery type – Tcode 0VLK ........................................................ 140
9.2 Configure Delivery Item Category – Tcode 0VLP ............................................ 141
9.3 Put the delivery type in the sales document type .......................................... 142
9.4 Pre-requisites for creating a delivery ........................................................ 143
9.5 Storage Location Determination in the Delivery – Tcode OVL3 ........................... 144
9.6 Maintain material master for storage location .............................................. 145
9.7 Route Determination ............................................................................ 146
Day 8: 09-Feb-2011 ........................................................................................ 150
10.0 Material Master ..................................................................................... 150
10.1 General Item Category group versus Item Category Group................................ 150
11.0 Delivery Processing ................................................................................ 151
11.1 Delivery and Transportation Scheduling ..................................................... 151
11.2 When is a sales order due for delivery? ...................................................... 156
11.3 Rounding Workdays in shipping point ......................................................... 157
12.0 Invoicing ............................................................................................. 157
12.1 Billing document type – Tcode VOFA ......................................................... 158
12.2 Assign the billing document type to the Sales document type ........................... 158
12.3 Copy Control settings – Delivery to Billing: Tcode VTFL ................................... 159
12.4 Create Individual Billing Document – Tcode VF01 .......................................... 160
Day 9: 14-Feb-2011 ........................................................................................ 162
13.0 Revenue Account Determination ............................................................... 162
13.1 Assign Account key in the Pricing Procedure – Tcode V/08 ............................... 162
13.2 Assign Account determination Procedure to Billing type – Tcode VOFA ................. 163
13.3 Account Determination Procedure ............................................................ 163
13.4 Maintain G/L Accounts (Master Data) for Revenue Determination - VKOA .............. 171
L&T Infotech - Confidential Page 4 of 730
 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

13.5 Create a Sales Order ............................................................................ 172

13.6 Create a Billing document ..................................................................... 173
13.7 Analysis of Revenue Account Determination ................................................ 175
13.8 Viewing Reconciliation Account in the Account Document generated from
Billing ............................................................................................. 176
13.9 Posting Block in billing type – Tcode VOFA .................................................. 178
13.10 Viewing Customer Balances – Tcode FD10N ................................................. 180
14.0 Material Listing and Exclusion ................................................................... 183
14.1 Material listing – Condition Technique ....................................................... 183
14.2 Material Exclusion ............................................................................... 188
Day 10: 15-Feb-2011....................................................................................... 189
15.0 Reconciliation Account Determination ........................................................ 189
15.1 Reconciliation Account Procedure ............................................................ 191
15.2 Condition type KOAB and Access Sequence KOAB .......................................... 191
15.3 Assign Account determination procedure to billing type .................................. 193
15.4 Assign G/L Accounts ............................................................................ 193
15.5 Define Alternative Reconciliation Accounts ................................................. 194
15.6 Reconciliation Account determination in the billing document .......................... 195
16.0 Material Master – Pricing Reference Material ................................................. 196
17.0 Customer Master - Transaction Dependent Screen Layouts – Tcode OB20 ............. 197
17.1 Account Group vs. Tcode Settings ............................................................ 201
18.0 Sales Document type .............................................................................. 201
18.1 Sales Document – Sub Item ..................................................................... 201
18.2 Pricing Date in the Sales Order ................................................................ 203
18.3 Pricing Date in Individual Condition types ................................................... 204
18.4 Date type ......................................................................................... 207
18.5 Immediate Delivery ............................................................................. 209
19.0 Item Category Settings ............................................................................ 209
19.1 Billing Relevance ................................................................................ 209
20.0 Billing................................................................................................. 210
20.1 Billing type – Document Pricing Procedure .................................................. 210
20.2 Release Billing Documents for Accounting – Tcode VFX3 .................................. 210
21.0 Material Determination ........................................................................... 212
21.1 Material Determination Procedure ............................................................ 212
21.2 Condition type, Access Sequence and Condition Tables ................................... 212
21.3 Assign Material Determination Procedures to Sales Document Types ................... 214
21.4 Maintain Material Determination Condition Records – VB11 .............................. 214
L&T Infotech - Confidential Page 5 of 730
 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

21.5 Substitution Reasons – Tcode OVRQ .......................................................... 215

21.6 Sales Order Entry ................................................................................ 218
21.7 Item Category determination for sub-items specific to material determination
- Outcome A ...................................................................................... 218
21.8 Item Category determination for sub-items specific to material determination -
Outcome B ........................................................................................ 220
Day 11: 16-Feb-2011....................................................................................... 221
22.0 Pricing ................................................................................................ 221
22.1 Header Conditions ............................................................................... 221
22.2 Scales ............................................................................................. 225
22.3 Condition type VPRS ............................................................................ 228
Day 12: 17-Feb-2011....................................................................................... 230
23.0 One Time Customer ............................................................................... 230
23.1 Account Group CPDA ............................................................................ 230
23.2 Maintain a One-Time Customer – Tcode VD01 ............................................... 231
23.3 Create a Sales Order for One-time Customer ............................................... 233
23.4 Delivery and Billing of one time customers .................................................. 234
24.0 Cash Account Determination .................................................................... 234
24.1 Create Cash Account Determination Procedure – Tcode OV76............................ 234
24.2 Assign Cash Account Determination Procedure to the Billing type – Tcode OV78 ...... 235
24.3 Assign G/L Accounts – Tcode OV77 ........................................................... 236
24.4 Create a billing document ..................................................................... 236
24.5 Account determination analysis ............................................................... 236
25.0 Proforma Invoice ................................................................................... 237
25.1 Define a Proforma Invoice – Tcode VOFA .................................................... 238
25.2 Order and Delivery Related Proforma Invoices.............................................. 238
25.3 Copy Control Settings – Proforma Settings ................................................... 239
25.4 Multiple Proforma Invoices per Document ................................................... 239
26.0 Removing Revenue Account Determination from Billing type ............................ 240
27.0 Combining Sales Organization ................................................................... 240
Day 13: 18-Feb-2011....................................................................................... 241
28.0 Order Related Billing .............................................................................. 241
29.0 Copy Control – Order to Billing .................................................................. 243
29.1 Pos/Neg Quantity = 0. .......................................................................... 243
29.2 Billing Quantity .................................................................................. 244
29.3 Copy Control: Order to Billing – Pricing Type ............................................... 244

L&T Infotech - Confidential Page 6 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

30.0 Pricing ................................................................................................ 248

30.1 Pricing – Condition type ‘Accrual checkbox’ ................................................ 248
30.2 Condition type Setting - Reference Condition type ........................................ 250
Day 14: 21-Feb-2011....................................................................................... 252
31.0 Delivery Processing ................................................................................ 252
31.1 Picking Location Determination ............................................................... 252
31.2 Reversing Goods Issue .......................................................................... 256
31.3 Proof of Delivery................................................................................. 260
32.0 Billing................................................................................................. 265
32.1 Assignment Number & Reference Number in Billing........................................ 265
32.2 Reversing Billing document – Tcode VF11.................................................... 268
32.3 Cancellation Billing type ....................................................................... 271
32.4 Negative Posting ................................................................................. 272
33.0 Sales Order Processing ............................................................................ 275
33.1 Sales Order Block ................................................................................ 275
34.0 Customer Master ................................................................................... 276
34.1 Blocking Customers ............................................................................. 277
35.0 Material Master ..................................................................................... 280
35.1 Material Master Status .......................................................................... 280
36.0 Pricing ................................................................................................ 283
36.1 Lower Limit and Upper Limit in the Condition Record ..................................... 283
37.0 Rebate Processing ................................................................................. 286
37.1 Rebate Pre-Requisites .......................................................................... 287
37.2 Rebate Condition Type/Access Sequence/Table............................................ 287
37.3 Put Rebate Condition type into Sales Order Pricing Procedure ........................... 290
37.4 Creation of Rebate Condition Type Groups .................................................. 291
37.5 Creation of Rebate Agreements – VB(2 ....................................................... 292
37.6 Assign Condition type group to Rebate agreement type – VB(5........................... 292
37.7 Assign Sales doc types R4, R3, B1, B2 to your sales area – OVAZ ......................... 293
37.8 Rebate Account Assignment – Tcode VKOA .................................................. 293
37.9 Customer Master Payer – Prerequisites ....................................................... 293
37.10 Master Data – Create Rebate Agreement Tcode VBO1 ..................................... 294
37.11 Maintain Rebate condition records in the rebate agreement ............................. 295
37.12 Billing Document ................................................................................ 296
37.13 Execute Program SDBONT06 ................................................................... 298
37.14 Rebate Payment ................................................................................. 299
37.15 Reversing Accruals without making Rebate Payment ...................................... 305
L&T Infotech - Confidential Page 7 of 730
 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

37.16 Manual Rebate Payments ....................................................................... 305

37.17 Material for Settlement ........................................................................ 311
37.18 Creating Manual Accruals ...................................................................... 313
37.19 Rebate Processing – Accounting Overview ................................................... 315
Day 15: 22-Feb-2011....................................................................................... 315
38.0 Shipping .............................................................................................. 315
38.1 Route Re-Determination in the delivery based on weight group ......................... 315
38.2 Partial delivery per item – A (Create a delivery with Qty > 0) ............................ 318
38.3 Partial Delivery per item – C (only complete delivery allowed) .......................... 320
38.4 Maximum Partial Deliveries allowed .......................................................... 321
38.5 Specify Characteristics of system messages (variable messages in shipping)........... 323
38.6 Under Delivery tolerance ....................................................................... 323
38.7 Over delivery tolerance ........................................................................ 324
38.8 Checking the partial delivery settings in the sales order .................................. 327
39.0 Sales .................................................................................................. 327
39.1 Sales Unit of Measure ........................................................................... 327
39.2 Minimum Order Quantity ....................................................................... 334
39.3 Minimum Delivery Quantity .................................................................... 336
39.4 Delivery Unit ..................................................................................... 338
39.5 Variable Messages - OVAH ...................................................................... 339
40.0 Inquiry – Tcode VA11 .............................................................................. 341
40.1 Key Features of an Inquiry ..................................................................... 343
40.2 Item type B – Text item ........................................................................ 344
41.0 Quotation – Tcode VA21 .......................................................................... 345
41.1 Creating Quotation with reference to Inquiry ............................................... 346
41.2 Creation of Sales Order from Quotation ..................................................... 348
42.0 Appendix ............................................................................................ 349
42.1 Calendar – Tcode SCAL.......................................................................... 349
42.2 Use of Calendar in the Sales Order ........................................................... 358
42.3 Date Calculation and Calendars in the Sales Order......................................... 361
Day 16: 23-Feb-2011....................................................................................... 362
43.0 Incoming Payment – Tcode F-28 ................................................................ 362
44.0 Entering Customer Invoice directly in FI – Tcode FB01..................................... 369
Day 17: 24-Feb-2011....................................................................................... 374
45.0 Consignment Processing .......................................................................... 374
45.1 Consignment Fill up ............................................................................. 374

L&T Infotech - Confidential Page 8 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

45.2 Consignment pick-up ............................................................................ 379

45.3 Consignment Issue ............................................................................... 384
45.4 Consignment Returns ........................................................................... 388
Day 18: 26-Feb-11 .......................................................................................... 391
46.0 Purchase Process Overview ...................................................................... 391
46.1 Creation of Vendor Master – Tcode XK01..................................................... 391
46.2 Create a material master with Purchasing View ............................................ 393
46.3 For a combination of material and vendor, create an Inforecord – ME11 ............... 395
46.4 Create a Purchase Order for the Vendor – Tcode ME21N .................................. 398
46.5 Release the Purchase Order ................................................................... 399
46.6 Create a Goods Receipt – Tcode MIGO ....................................................... 400
46.7 In the Good Receipt Transaction MIGO, select item OK ................................... 403
46.8 Check the stocks – Tcode MMBE ............................................................... 404
46.9 Create a Vendor Invoice – Tcode MIRO ....................................................... 405
47.0 Purchase order with a Purchase Requisition ................................................. 408
47.1 Creation of Purchase Requisition – Tcode ME51N ........................................... 408
47.2 Release the Purchase Requisition – Tcode ME54N .......................................... 409
47.3 Converting a Purchase Requisition to a Purchase Order ................................... 411
48.0 Third Party Sales (Also known as Drop Shipments) .......................................... 413
48.1 Configuration of Item Category TAS .......................................................... 413
48.2 Schedule Line Category Determination ...................................................... 414
48.3 Schedule Line Category CS ..................................................................... 414
48.4 Copy Control Order – Billing Tcode VTFA .................................................... 415
48.5 Create a Sales Order ............................................................................ 416
48.6 Invoice quantity less than Order Quantity ................................................... 420
48.7 Statistical Goods Receipt (Non Valuated Goods Receipt).................................. 421
48.8 Sales Order – Billing Copy Control Settings Tcode VTFA ................................... 422
48.9 Monitoring the third party processes of the sales order ................................... 423
49.0 Serial Numbers ..................................................................................... 424
49.1 Maintain Serial Number Profile – Tcode OIS2 ................................................ 424
49.2 Maintain Serial number profile in the material master in view Sales:
General/Plant .................................................................................... 425
49.3 Create a Goods Receipt using movement type 501 – Tcode MB1c ........................ 425
49.4 Checking material stocks – Tcode MMBE ..................................................... 426
49.5 An equipment master is generated for each combination of material & Serial
Number – Tcode IE03 ............................................................................ 428
49.6 Create a sales order and delivery ............................................................. 428
49.7 Check the equipment master for serial number 7 of material M-266 .................... 430
L&T Infotech - Confidential Page 9 of 730
 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

50.0 Product Hierarchy – Tcode OVSV................................................................ 432

50.1 Product Hierarchy structure is seen in structure PRODHS – Tcode SE11 ................ 433
50.2 Maintenance of Product Hierarchy – Tcode V/76 ........................................... 433
50.3 Maintain Product Hierarchy in the material Master ........................................ 434
50.4 Product Hierarchy in the sales order ......................................................... 439
51.0 Finding Customizing Transaction codes using table TSTCP ................................ 440
Day 19: 28-Feb-11 .......................................................................................... 442
52.0 Intercompany Sales Order Processing.......................................................... 442
52.1 Overview – Prerequisites ....................................................................... 443
52.2 Process Summary ................................................................................ 443
52.3 Base Settings – Ordering Company code ..................................................... 443
52.4 Base Settings – Delivering Company Code.................................................... 444
52.5 Defining the IC Billing Sales Area – Tcode OVV9 ............................................ 444
52.6 Define an intercompany customer IC-1000 in the delivering company sales area
3000-10-00 and company code 3000. ......................................................... 445
52.7 Assign this customer number to Sales Organization 1000 – Tcode OVVA ................ 445
52.8 Assign delivering plant 3000 to Ordering Distribution Chain 1000-10 .................... 446
52.9 Define Intercompany Billing type – Tcode VOFA ............................................ 446
52.10 In Order type OR, maintain intercompany billing type Tcode VOV8 ..................... 447
52.11 Pricing Procedure Settings ..................................................................... 447
52.12 Create Condition records for PI01 – Transfer Price ......................................... 448
52.13 Maintain Customer Price ....................................................................... 448
52.14 Create a customer order in Ordering Company Code ...................................... 450
52.15 Customer Delivery is done from shipping point 3000 and Plant 3000 .................... 450
52.16 Customer Billing ................................................................................. 452
52.17 Intercompany Billing Document ............................................................... 454
52.18 Business Area Link ............................................................................... 457
52.19 Billing Error....................................................................................... 457
Day 20: 01-Mar-11 .......................................................................................... 458
53.0 Definition of a Fiscal Year – Tcode OB29 ...................................................... 458
53.1 Calendar Year with Number of Posting Periods = 12 ....................................... 458
53.2 April to March with 12 Periods ................................................................ 459
53.3 Year Dependent Fiscal Year with 12 periods ................................................ 460
53.4 One company code can have only one fiscal year – Tcode OB37 ......................... 461
54.0 Closing MM Periods ................................................................................ 462
54.1 Allowing Posting to earlier period & Viewing current Period ............................. 463
54.2 Closing Period: Tcode – MMPV ................................................................. 464

L&T Infotech - Confidential Page 10 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

54.3 Danger – Period Closing ......................................................................... 465

55.0 Moving Average Price in the Material Master ................................................. 466
55.1 Changing the Moving Average Price – Tcode MR21.......................................... 469
56.0 Intercompany Stock Transport Order with SD Delivery .................................... 472
56.1 MM configuration ................................................................................ 472
56.2 SD Configuration ................................................................................. 476
56.3 Create a Purchase Order ....................................................................... 481
56.4 Process Delivery Due List using Tcode VL10D in company code 3000. ................... 482
56.5 Check stock position in Plant 1000 – Tcode MMBE .......................................... 484
56.6 Do a goods receipt in Plant 1000 – Tcode MIGO ............................................. 485
56.7 Check the stock status in plant 1000. ........................................................ 486
56.8 Create Intercompany billing document based on the delivery ........................... 487
56.9 Goods Issue at plant 3000 and goods receipt at plant 1000 simultaneously ............ 487
Day 21: 02-Mar-11 .......................................................................................... 488
57.0 Stock Transport Processing between Plants of same company code .................... 488
57.1 Define Purchase document type UB .......................................................... 489
57.2 Define Shipping Data for Plants ............................................................... 490
57.3 Assign Delivery Type and Checking Rule ..................................................... 491
57.4 Assign Document Type, One-Step Procedure, Underdelivery Tolerance ................ 491
57.5 Delivery Item Category Determination – Tcode 0184....................................... 491
57.6 Schedule line category Determination – VOV5 .............................................. 492
57.7 Create Purchase Order ......................................................................... 492
57.8 Create delivery using Tcode VL10D ........................................................... 492
57.9 One Step Process – Goods Issue and Goods receipt in a single jhatka ................... 495
58.0 Individual PO Cycle ................................................................................ 496
58.1 SAP Process Overview ........................................................................... 496
58.2 Standard item category – TAB Configuration ................................................ 496
58.3 Schedule line category CB Configuration .................................................... 497
58.4 Create sales order with Item Category TAB ................................................. 498
58.5 Create a Purchase order from the Purchase Requisition – Tcode ME21 ................. 500
58.6 Post Goods Receipt for the PO ................................................................ 502
58.7 View Sales Order Stock – Tcode MMBE........................................................ 503
58.8 Create a delivery for the sales order ......................................................... 505
58.9 Carry out billing for the delivery .............................................................. 506
59.0 Returns Processing ................................................................................ 506
59.1 Returns Processing with reference to Billing doc / credit memo ........................ 506
59.2 Returns Process with reference to a sales order............................................ 514

L&T Infotech - Confidential Page 11 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

59.3 Scrapping the material instead of taking it back in goods stocks ........................ 517
59.4 Creating Returns without Reference ......................................................... 520
59.5 Giving Customer Free of Charge Subsequent delivery instead of credit memo ........ 521
60.0 Material Type Configuration – Tcode OMS2 ................................................... 525
60.1 User Departments ............................................................................... 527
60.2 Price Control ..................................................................................... 528
60.3 Quantity / Value Updating ..................................................................... 530
60.4 Proposal of Item Category in Material Master ............................................... 533
Day 22: 04-Mar-11 .......................................................................................... 533
61.0 Free Goods Determination ....................................................................... 533
61.1 Define Number Range for Free Goods – WC07 ............................................... 534
61.2 Free Goods Condition technique .............................................................. 534
61.3 Activating Free Goods Determination – V/N6 ............................................... 536
61.4 Sales Order Pricing with condition type R100 – Tcode V/08 .............................. 536
61.5 Inclusive Free Goods Sales Order Processing ................................................ 538
61.6 Item Category Determination for inclusive free goods with item generation &
Exclusive Rebates ............................................................................... 544
61.7 Inclusive Rebate without Item Generation .................................................. 544
61.8 Exclusive Rebates ............................................................................... 547
62.0 SD Bill of Material (BOM) Processing............................................................ 549
62.1 Create a SD BOM – Tcode CS01 ................................................................ 549
62.2 Processing of SD BOM in a sales order ........................................................ 551
62.3 Main Item Level – Sales Order Processing .................................................... 551
62.4 Main item – Configuration (TAQ) .............................................................. 557
62.5 Sub item – Configuration (TAE) ................................................................ 558
62.6 Processing at Component level ................................................................ 560
62.7 Processing at component level – Configuration ............................................. 564
62.8 Pricing at the header level and inventory and delivery control at item level .......... 565
63.0 Cross Selling......................................................................................... 566
63.1 Condition technique for Cross Selling ........................................................ 566
63.2 Maintain Customer/Document Procedures For Cross Selling .............................. 568
63.3 Define And Assign Cross-Selling Profile....................................................... 569
63.4 Maintain CUPP for cross selling in the customer master ................................... 569
63.5 Maintain Cross Selling Condition Records – Tcode VB41 ................................... 570
63.6 Create a Sales Order ............................................................................ 572
63.7 Item Category determination for Sub-item .................................................. 573
63.8 Cross Selling Dialog box appears only on request ........................................... 573
63.9 Cross Selling and Dynamic Product Proposal ................................................ 574
L&T Infotech - Confidential Page 12 of 730
 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

64.0 Dynamic Product Proposal ....................................................................... 574

64.1 Maintain Table of Origin for Product Proposal .............................................. 574
64.2 Define Product Proposal Procedure and Determine Access Sequences .................. 575
64.3 Maintain Procedure Determination (Online) for Product Proposal ....................... 576
Day 23: 05-Mar-2011 – Saturday ......................................................................... 576
65.0 Tax Determination ................................................................................. 576
FI Settings – Tax Determination ............................................................................ 576
65.1 Define Country specific Tax Procedure in FI – Tcode OBQ3 ............................... 576
65.2 Define FI account keys – Tcode OBCN ........................................................ 578
65.3 Assign Country of company code to Tax Procedure – Tcode OBBG ....................... 578
65.4 Tax Condition types in FI are defined in Tcode OBQ1...................................... 578
65.5 Tax Access Sequence in FI – Tcode OBQ2 .................................................... 579
SD Settings – Tax Determination ............................................................................ 580
65.6 Define Tax Condition type separately in SD Tcode V/06 .................................. 580
65.7 Define a tax Category e.g. UTXJ in SD which triggers Tax calculation .................. 581
65.8 Define Tax Determination Rules – Tcode OVK1 ............................................. 584
65.9 Define Tax Relevancy of Master Records..................................................... 584
65.10 SD Pricing Procedure Configuration – V/08 .................................................. 585
Tax Master Data Maintenance & Sales Order Creation .................................................. 585
65.11 Tax Jurisdiction Codes .......................................................................... 586
65.12 Tax Master Data is maintained in FI tax codes – Tcode FTXP ............................. 586
65.13 Maintain SD Condition Records for UTXJ to find the Tax Code – Tcode VK11........... 593
65.14 Maintain Customer Tax Classification 3 in the customer Master ......................... 593
65.15 Maintain Material Tax Classification in the Material Master .............................. 595
65.16 Maintain Tax Jurisdiction Code in the Ship-to Party ....................................... 596
65.17 Create a Sales Order & checking Tax Calculations ......................................... 597
65.18 Create the Billing document & checking Tax Accounts .................................... 599
66.0 Pricing Settings ..................................................................................... 600
66.1 Condition type Control in Tcode OVKK ....................................................... 600
66.2 Structures KOMK and KOMP .................................................................... 601
66.3 Additional settings in Access Sequence ...................................................... 602
67.0 Customer Hierarchy ............................................................................... 605
67.1 Business Scenario ................................................................................ 605
67.2 Define Customer Hierarchy Partner Functions .............................................. 606
67.3 Define Hierarchy Types ......................................................................... 606
67.4 Set Partner Determination for Hierarchy Categories ....................................... 606
67.5 Assign Account Groups to higher level account groups .................................... 607
67.6 Assign Sales Areas ............................................................................... 608
L&T Infotech - Confidential Page 13 of 730
 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

67.7 Assign Hierarchy Type for Pricing by Sales Document Type ............................... 608
67.8 Pricing Procedure – Condition types HI01/HI02 ............................................. 609
67.9 Create a hierarchy node – Tcode V-12........................................................ 610
67.10 Create Customer Hierarchy – Tcode VDH1N ................................................. 611
67.11 Maintain Condition records for HI01 condition type. Tcode VK11 ........................ 615
67.12 The customer hierarchy is seen in the Partner Screen of the Sales Order Header .... 615
68.0 Billing Calendar – Tcode OVR4 ................................................................... 617
68.1 Define Billing Schedule ......................................................................... 617
68.1 Assign Billing Schedule to the Payer .......................................................... 621
68.2 Impact of Invoicing Calendar on billing ...................................................... 621
69.0 Credit Management ................................................................................ 622
69.1 Organization Structure – Define Credit Control Area (Tcode OB45)...................... 622
69.2 Permitted Credit Control Areas per company code – Tcode OBZK ....................... 623
69.3 Assign Credit Control Area to Company Code – Tcode OB38 .............................. 624
69.4 Assign Credit Control Area to the Sales Area ................................................ 624
69.5 Credit Settings in the Pricing Procedure ..................................................... 624
69.6 Activate Credit Check for Item Category .................................................... 625
69.7 Configuring Simple Credit Check for document type....................................... 625
69.8 Maintain Credit Limit for Customer – Tcode FD32 .......................................... 626
69.9 Sales Order with Simple Credit Check ........................................................ 629
69.10 Updates credit exposure on saving a sales order ........................................... 631
69.11 Define Credit Group for Sales Order .......................................................... 633
69.12 Activating Automatic Credit Control – Tcode OVAK ........................................ 633
69.13 Define Automatic Credit Check – OVA8 ...................................................... 633
69.14 Static Credit Check.............................................................................. 634
69.15 Releasing Credit Check – Tcode VKM1 and VKM3 ........................................... 637
69.16 Viewing Changes in the sales order ........................................................... 638
Day 24: 08-Mar-11 .......................................................................................... 640
70.0 Billing document number = Accounting document number ............................... 640
71.0 Customer Master – Changing account groups: Tcode XD07 ................................ 642
72.0 Shipping conditions in Customer vs. Sales Document type ................................ 646
73.0 Rush Orders ......................................................................................... 646
74.0 Free of Charge Delivery .......................................................................... 647
75.0 Scheduling Agreements ........................................................................... 650
75.1 Create Scheduling Agreement – Tcode VA31 ................................................ 653
75.2 Create delivery for scheduling agreement................................................... 654

L&T Infotech - Confidential Page 14 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

76.0 Pricing - Condition Supplements ................................................................ 655

76.1 Create a pricing procedure for condition supplement ..................................... 655
76.2 Put the supplement pricing procedure in the condition type PR00 ...................... 655
76.3 Assign all supplement condition types to regular pricing procedure..................... 656
76.4 Create condition record for Condition type PR00 .......................................... 657
76.5 Create Sales Order .............................................................................. 658
77.0 Outline Agreements message during VA01.................................................... 659
78.0 Introduction to RICEF ............................................................................. 661
78.1 Reports ............................................................................................ 661
78.2 Interfaces ......................................................................................... 664
78.3 Conversions ....................................................................................... 664
78.4 Enhancements ................................................................................... 665
78.5 Forms .............................................................................................. 666
Day 25: 09-Mar-11 .......................................................................................... 668
79.0 Output Determination ............................................................................ 668
79.1 Assign Output Determination to Billing type: v/25 ......................................... 668
79.2 Maintain output determination procedure................................................... 668
79.3 Create Smart Forms – Tcode SMARTFORMS .................................................. 669
79.4 Maintain output types Tcode V/40 ............................................................ 669
79.5 Maintain output condition records – Tcode VV31 ........................................... 671
80.0 System Landscape ................................................................................. 671
81.0 Client ................................................................................................. 672
82.0 Implementation Projects ......................................................................... 673
82.1 ASAP Methodology ............................................................................... 673
82.2 Phase Wise Project Activities .................................................................. 673
82.3 Forrester Analysis of SAP Onsite-offshore Model............................................ 674
82.4 Report Variant ................................................................................... 675
82.5 Assigning Reports to Transaction codes – Tcode SE93 ...................................... 677
83.0 Authorization Matrix .............................................................................. 680
84.0 Create a Role – Tcode PFCG...................................................................... 680
84.1 Assign required transaction code to Role .................................................... 681
84.2 Assign Authorization to Authorization Activities ............................................ 682
84.3 Generate the authorization Role .............................................................. 686
84.4 Assign User and select User Comparison. .................................................... 686
84.5 Adding a role manually. ........................................................................ 687
84.6 Checking Authorization Object in SAP – Tcode SU53 ....................................... 690

L&T Infotech - Confidential Page 15 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

85.0 Use of Currencies in Sales Documents ......................................................... 692

85.1 Maintain document Currency in Customer Master .......................................... 692
85.2 Document currency in the sales order........................................................ 692
85.3 Maintaining exchange rates manually in the sales Order .................................. 695
85.4 Copy Control Settings – Delivery to Billing Tcode VTFL .................................... 696
85.5 Exchange rate in Billing ........................................................................ 697
85.6 Maintenance of Currency Exchange Rates – Tcode F-62 ................................... 698
Day 26: 10-Mar-11 .......................................................................................... 698
86.0 Project ............................................................................................... 698
86.1 Business Overview ............................................................................... 698
86.2 Deliverables ...................................................................................... 700
86.3 Configuration Decisions ......................................................................... 702
86.4 System Configuration Requirements .......................................................... 703
86.5 Technical Enhancements ....................................................................... 705
Day 27: 11-Mar-11 .......................................................................................... 706
87.0 Creating a Business Blueprint ................................................................... 706
87.1 Business Scenario Requirements .............................................................. 707
Day 28: 12-Mar-11 .......................................................................................... 709
88.0 Planning the final case study presentation ................................................... 709
Day 29: 09-Mar-11 – The End ............................................................................. 712
89.0 Enhancements to the SAP System .............................................................. 712
90.0 Determining a number range dynamically during saving a sales order – My First
User Exit ☺ ................................................................................................... 712
91.0 Customer Master Checks using Exits – Tcode CMOD ......................................... 714
92.0 Appendix ............................................................................................ 715
92.1 Set Start Transaction ........................................................................... 715
92.2 Sales Order Tables .............................................................................. 715
92.3 Viewing Users in the System – SM04 .......................................................... 716
92.4 Creating SD Number Range – Tcode SNRO ................................................... 716
92.5 Finding technical names of fields from master data / transaction data ................ 718
92.6 Personal Settings for F1 Help .................................................................. 720
92.7 Setting standard customizing Request ....................................................... 722
92.8 Setting defaults using parameter IDs ......................................................... 724
92.9 Viewing Customer Master – Administrative Data ............................................ 725
92.10 Viewing Sales order Document flow .......................................................... 726
92.11 Settings overview of sales document type ................................................... 730

L&T Infotech - Confidential Page 16 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Day 4: 01-Feb-2011
1.0 Customizing the Sales Document type
1.1 Create a Sales Document type
Create a new Sales document type – Tcode VOV8

1.2 Assign Sales area to Sales Document type

Assign Sales Area to Sales document type – Tcode OVAZ

1.3 Partner Determination procedure for Sales Doc type

When you try to create the sales order, the system does not allow entering the sold to
party.

This is because partner procedure is not assigned to a sales document type. Assign the
partner procedure to the Sales document type.

L&T Infotech - Confidential Page 17 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

1.4 Pricing Procedure Determination in the sales order

When try to create the sales order, it gives an error.

. Double click on the error to see the diagnosis.

Analysis tells you that there is missing customizing in tcode OVKK. It also tells you there
is DOPP missing in the sales document type. Put DOPP as Z in the sales doc type (VOV8).

Maintain Tcode OVKK. – Pricing procedure determination.

Note: Of the 5 parameters to determine pricing, the only parameter in users control is
the CUPP in the customer master. There are chances of wrong entries here which will be
give pricing procedure error. So always check the customer master for accuracy.

L&T Infotech - Confidential Page 18 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

1.5 Required Delivery Date proposal in the sales order

You try to create a sales order. The delivery date has to be filled in manually. For this
particular sales order, delivery is done on the same day. We want the system to propose
the current as the required delivery.

The system now automatically proposes required delivery date as the current date.

1.6 Purchase Date Proposal in the Sales Order

The purchase order date is the date on the customer’s PO. This could be any date. In
case, you have a scenario where the customer gives the order on the same day as it is
being entered into SAP, then select checkbox Propose PO Date (as current date).

L&T Infotech - Confidential Page 19 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

1.7 Sales Document Numbering

The system does not allow external numbering of the sales order.

This is because the order type has not been configured for external number range.

If you do not follow an external number range, ensure that the assignment is not done.

1.8 Item Increment

Note: If this setting is not there, the item cannot be entered. The system goes into a
loop.

L&T Infotech - Confidential Page 20 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

During sales order entry, the item number is controlled by the item increment.

1.9 Item Category Determination

When we try to enter the line item, we get the follow error.

Define (VOV7) and assign Item categories (VOV4).

L&T Infotech - Confidential Page 21 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

1.10 Customer Material Info Record – Tcode VD51

Business Scenario: In SAP my material code is M-100. But my customer who buys this
product calls it X-4586 in his records. This has to be mapped into SAP and used in order
entry.

Thermax has a boiler – B5687A which is a BAAN generated number. A customer has sent
you a Purchase order with his BAAN generated number A56256 for the same product. You
want to enter a sales order using his BAAN generated number A56256.

1.10.1 Activate customer-material info record in the sales document type

L&T Infotech - Confidential Page 22 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 23 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

1.10.2 Create Customer Material Info Record

The customer material info record has to be maintained for the sold to party (and not
ship to party or other partners).

1.10.3 Go into Ordering Party Overview

L&T Infotech - Confidential Page 24 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

In the ordering party tab, when you enter the customer material number, the system
automatically picks up the material no.

When you see the item overview tab, the SAP material no. is seen as usual.

L&T Infotech - Confidential Page 25 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

1.10.4 Configure sales document type to go to Ordering Party Screen

If you want the system to directly go to the ordering party screen, configure the sales
document type.

1.11 Plant Determination in the Sales Order

1.11.1 Plant determination from the material master

L&T Infotech - Confidential Page 26 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The delivering plant in the sales order gets proposed from the material master. Likely
business scenario would be:
• This particular material is available only in this plant
• All materials go only from one plant

1.11.2 Plant determination from the customer master of ship to party

The delivering plant can be maintained in the customer master.

Business scenario:
You have 2 warehouses in Mumbai and Pune supplying to retailers in these 2 cities. In
normal circumstances, Pune retailers have to be supplied from Pune warehouse and
Mumbai retailers have to be supplied from Mumbai Warehouse. In this case, default the
delivering plant Pune in the Pune Retailer customer masters in SAP.

The allowed delivering plants here depend on Sales Org + DC + Plant combinations
allowed in customizing.

L&T Infotech - Confidential Page 27 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

If material master has plant = 1000

If sold to party has plant = 1001
If ship to party has plant = 1100

Note:
• Plant determination from customer master takes precedence over material master
• The system picks up 1100. i.e. precedence is given to the ship-to party over the
sold to party

1.11.3 Delivering Plant determination from the customer material info record

The system picks up the delivering plant from the customer material info record.
L&T Infotech - Confidential Page 28 of 730
 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

1.11.4 Order of Preference – Plant determination

• The system first searches for delivering plant in customer material info record. If
it finds a plant here, it picks up from here.
• If no plant is found above, it looks at the Ship to Party Master
• If no plant is found there, it looks at the sold to Party Master
• If no plant is found there, it looks at the material master
• If no plant is found there, enter manually

Note: If a plant determination enhancement is coded in the system, it overrides the

above settings.

L&T Infotech - Confidential Page 29 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

1.12 Shipping Point Determination

The physical shipping activities in a warehouse are done by the logistics department.
These include calling the transporters, scheduling the orders for delivery, loading the
trucks. This department is mapped as a shipping point in SAP.

Within a warehouse if you have 2 logistics departments – Road Dispatches and Rail
Dispatches. These may be defined as 2 different Shipping Points. Shipping Point is the
organization structure in the delivery document.

Note: Deliveries cannot be created if there is no shipping point in the order.

1.12.1 Customizing Shipping point determination

Shipping point depends on the delivering plant, the customer master (shipping
condition) and the material master (loading group).

Maximum 11 shipping points can be proposed for a sales order manually.

L&T Infotech - Confidential Page 30 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

1.12.2 Shipping conditions in the customer master of Ship to Party

L&T Infotech - Confidential Page 31 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

1.12.3 Loading group in the material master

1.12.4 Shipping point determination in the sales order

• In the sales order, find out what is the shipping conditions determined

L&T Infotech - Confidential Page 32 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Select the item and display material.

L&T Infotech - Confidential Page 33 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 34 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Shipping point is determined here based on shipping condition 01 and loading group 0001
and plant 1200.

1.13 Incompletion Log

L&T Infotech - Confidential Page 35 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

1.13.1 Define Incompleteness Procedures (Tcode OVA2)

Define an incompletion procedure Y0 with field PO Number.

L&T Infotech - Confidential Page 36 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

1.13.2 Assign Incompleteness Procedures to sales document type (VUA2)

L&T Infotech - Confidential Page 37 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

1.13.3 Warning Checkbox

1.13.4 Impact of IC Dialog Checkbox

L&T Infotech - Confidential Page 38 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

If you keep it blank, the system will allow saving an incomplete document with a
warning.

If we select the checkbox, the system will not allow saving an incomplete document.

L&T Infotech - Confidential Page 39 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

When you say, complete data, you reach the screen where you have to fill in the
data. Once you fill in all missing data, you get a message:

1.13.5 Checking Incompletion in the Sales Order

L&T Infotech - Confidential Page 40 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

1.13.6 What happens if you don’t put a screen in incompletion field definition?

L&T Infotech - Confidential Page 41 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

1.13.7 Define and assign incompletion procedure (VUP2) at item level

L&T Infotech - Confidential Page 42 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

1.13.8 Putting Pricing in Incompletion Log

This works only if both the following conditions are satisfied.
• Pricing procedure should have at least one condition type which is mandatory
• The incompletion log should have the following entry

1.14 Text Determination (Tcode VOTXN)

The customer’s special instructions have to be captured in the sales order. We need
to define texts to input this information.

L&T Infotech - Confidential Page 43 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

1.14.1 Define Text Types (Tcode VOTXN)

L&T Infotech - Confidential Page 44 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Select Text types .

1.14.2 Define and Assign Text Determination Procedures

L&T Infotech - Confidential Page 45 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 46 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 47 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Day 5: 02-Feb-2011
2.0 Customizing the Sales Document type

2.1 Check for Purchase Order number in the sales order

L&T Infotech - Confidential Page 48 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

This is only a warning message. You can still input the same PO number.

L&T Infotech - Confidential Page 49 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

2.2 Enter PO Number

In sales order customizing, select checkbox Enter PO Number.,

If the PO number is left blank at the time of saving the order, the field is filled by the
sales order number.

L&T Infotech - Confidential Page 50 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

2.3 Item Division

If you do not select the checkbox Item Division, the division in the sales order item is
proposed from the division of the header sales area.

If you select the checkbox Item division, the division from the material master.

L&T Infotech - Confidential Page 51 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

If the division is selected from the material master, the system looks for all customer
masters to be maintained in the sales area with division = material master division.

Note: If no division exists in the material master, then the header division is defaulted in
the material.

2.4 Sales document block

L&T Infotech - Confidential Page 52 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 53 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

2.5 Incomplete Messages

If the incompletion log assigned to the sales document type does not have the IC-Dialog,
it allows saving of an incomplete document.

In the customizing of sales document select check box ‘Incomplete messages’.

Creating hard stops for incompletion, there are 2 ways.

1. Assign incompletion log to sales document and select IC Dialog, or

2. Customize Sales document type – Incomplete message check box. This setting
takes precedence over the earlier one.

L&T Infotech - Confidential Page 54 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

2.6 Schedule Lines

2.6.1 Viewing schedule lines for item

Every item in the sales order is divided into one or more schedule line. This gives the
flexibility of giving separate delivery schedules of the item.

Otherwise select icon in

L&T Infotech - Confidential Page 55 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

2.6.2 Checking the effect of schedule lines in the item overview screen
If schedule lines exists for an item, the quantity field gets grayed out, and a check box
appears in the S (Do multiple schedule lines exist) field.

The schedule lines are controlled by the schedule line category. If the item category does
not permit schedule lines, you cannot enter the schedule line data.

2.6.3 Schedule line information

L&T Infotech - Confidential Page 56 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

In the shipping screen of the schedule line, transportation and delivery scheduling is
carried out. The system calculates various dates.

L&T Infotech - Confidential Page 57 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

In the procurement screen of the schedule line, delivery Movement type is viewed.

2.7 Schedule line category

2.7.1 Activate schedule lines for item category

If this setting is not there, during the sales order creation you get the following message:

L&T Infotech - Confidential Page 58 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

2.7.2 Define Schedule Line Category

2.7.3 Assign Schedule line category

L&T Infotech - Confidential Page 59 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Note: MRP type field is found in the MRP1 view of the material master.

L&T Infotech - Confidential Page 60 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

If the schedule line category is not assigned to the item category, you get the following
error message:

Day 6: 07-Feb-2011
3.0 Customizing the Sales Order
3.1 Reference Mandatory

L&T Infotech - Confidential Page 61 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 62 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

3.2 Check Division

L&T Infotech - Confidential Page 63 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 64 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

3.3 Common Distribution Channel / Division for Master Maintenance

Tcode VOR2

L&T Infotech - Confidential Page 65 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Common Distribution Channel / Division

1. Order Entry Sales Area = Y000/04/80
Common Distribution Channel = 00 (for Y000/04) – VOR1

2.

Common Division = 00 (for Y000/80) – Tcode VOR2

3.

4. Customer Master to be maintained for Y000/00/00

5. Material Master to be maintained for Y000/00
Now if you try to maintain a customer master in Y000/04/80, the system gives an
error.

6.

7. If you try to maintain a material master in Y000/04, the system gives an error.

L&T Infotech - Confidential Page 66 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The customer master and material master can only be entered in the sales
8.
area/distribution chain as maintained in the common distribution and division.
Pre-requisite: The sales area with common DC/Division has to be defined in
customizing.

9.

L&T Infotech - Confidential Page 67 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

3.4 Combine Sales Organizations

We have sales organization Y000. The following order types are assigned to this
sales organization.

Now we want to create a new sales organization YFTR with exactly the same sales
document types to similar sales areas. There are 2 ways of doing this:

1. Repeat the configuration settings for YFTR sales organization in OVAOI, OVAM,
OVAN and OVAZ exactly as it is there in Y000.

2. Combine Sales Organizations – Tcode OVAO, OVAM and OVAN.

3. The OVAZ settings of sales organization Y000 are replicated to sales

organization YFTR without maintenance.

4. Any changes in sales document type assignment to Y000 sales organization

impact sales org YFTR.

5. This setting is purely from ease of maintenance and may or may not be used.
The sales areas and sales document types are mirrored and cannot be
different.

L&T Infotech - Confidential Page 68 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

3.5 Alternate Sales document type

There are 3 sales document types assigned to Y000-50-70 for sales order entry.

During sales order entry, we would like to have the option of changing the order type.

In Tcode VOV8, put Alternate sales doc type1.

During Sales order entry,

L&T Infotech - Confidential Page 69 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

This can be done only once in a sales order. The radio button disappears after you select
an alternate sales document type the first time. This happens if a similar setting has not
been maintained in the alternative document type.

L&T Infotech - Confidential Page 70 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

3.6 Product Attribute check in the sales order

We have a ship to party 1054 to which we supply materials. This ship to party is located
in the USA and does not want any material produced in Cuba. We want to map this in
SAP.

3.6.1 Configure Sales Document type – Tcode VOV8

L&T Infotech - Confidential Page 71 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

3.6.2 Maintain Product Attributes in the Material Master

In the material master, Sales Org 2 – Product Attributes, rename Product Attribute 10 as
‘Made in Cuba’.

L&T Infotech - Confidential Page 72 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

3.6.3 Maintain product attributes to be rejected in the ship to party.

In the customer master of the ship to party, Sales Tab, select Product Attributes.

Here you select the product attribute that the ship to party DOES NOT want.

L&T Infotech - Confidential Page 73 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

3.6.4 In the Sales Order

During Sales order entry, the system

i. Checks customizing of sales document type if product attributes are to be
checked.
ii. It goes into the customer master and sees which product attributes, if any the
customer does not want.
iii. If it finds a product attribute, it goes into the material master to check if that
product attribute exists.
iv. If a exact match happens, the system rejects the product in the sales order.

L&T Infotech - Confidential Page 74 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

3.7 Item Proposal

3.7.1 Document type Product Proposal

L&T Infotech - Confidential Page 75 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

3.7.2 Maintain Sales document type Product Proposal in your sales area

L&T Infotech - Confidential Page 76 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

3.7.3 Create Item Proposal – Tcode VA51

3.7.3 Maintain item proposal in the sold to party.

L&T Infotech - Confidential Page 77 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

3.7.4 Sales Order Entry

L&T Infotech - Confidential Page 78 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Else, use icon .

The item proposal number gets defaulted from the sold to party. You can change it here
if you want.

L&T Infotech - Confidential Page 79 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Default without quantity:

Default with quantity:

Selection List:

L&T Infotech - Confidential Page 80 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

3.8 Default Delivery Block in the sales order

In the sales document type, put a delivery block.

The delivery block gets defaulted in the sales order at header level.

L&T Infotech - Confidential Page 81 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

3.9 Default Billing Block in the sales order

In the sales document type, configure the billing block.

This block gets defaulted to the sales order Header.

L&T Infotech - Confidential Page 82 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

3.10 Shipping Conditions in the Sales Doc type

If the shipping condition is maintained in the sales document type, it over rides the
settings in the customer master. i.e. it does not consider the customer masters at all.

4.0 Customizing Item Category

4.1 Business Item

4.1.1 Item Level Sales

L&T Infotech - Confidential Page 83 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

4.1.1.1 If the field is selected

4.1.1.2 If the field is not selected, the following data is in display mode only
Delivery time
Pricing date

L&T Infotech - Confidential Page 84 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

4.1.2 Item – Sales B

4.1.2.1 With the field selected

L&T Infotech - Confidential Page 85 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

4.1.2.2 If the field is not selected, the following data is in display mode only

Customer Group, Pricing Group, Price List and Sales District.

L&T Infotech - Confidential Page 86 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

4.1.3 Item – Shipping

4.1.3.1 With field selected

4.1.3.2 Field not selected

The following fields are in display mode:

• Department
• Means of transport type
• Means Transport
• Receiving Point
• Order Combination
• Shipping type
• Special Processing
• POD Relevant

L&T Infotech - Confidential Page 87 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

4.2 Weight Volume Relevant

4.2.1 In the material master – Basic View the weight and volume is maintained.

L&T Infotech - Confidential Page 88 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

4.2.2 Weight / volume Relevant

L&T Infotech - Confidential Page 89 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

4.2.3 Not relevant for weight / volume

In the sales order, the weight and volume goes in display mode with values 0.

L&T Infotech - Confidential Page 90 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

4.3 Defaulting Billing Block at the item level

L&T Infotech - Confidential Page 91 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

4.4 Pricing

This setting works in tandem with the requirement routine 002 in the pricing procedure.
If the requirement routine is not there, the system carries out pricing irrespective of
whether this is selected or not.

5.0 Schedule Line Settings

5.1 Default delivery block in the schedule line

L&T Infotech - Confidential Page 92 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The delivery block is defaulted in the schedule line.

Note: No separate block is at the item level.

6.0 Pricing Condition Technique

Pricing is controlled by the Condition type.

You can enter prices manually in the system or you can store it as master data as
Condition Records.
Condition Records are stored in Condition tables.

L&T Infotech - Confidential Page 93 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

6.1 Customize a condition table – V/05

Non SAP Standard Condition tables should be created in the number range 501 – 999.

Create a condition table with 2 fields:

• Sales Organization
• Material

L&T Infotech - Confidential Page 94 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Generate the table by selecting icon .

L&T Infotech - Confidential Page 95 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

In the background, the system generates a database table with a prefix A. While defining
the condition table, we had put in just 2 fields i.e. Sales Organization and Material. The
system automatically creates the remaining fields of the table.

L&T Infotech - Confidential Page 96 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

6.2 Create an access sequence: Tcode V/07

L&T Infotech - Confidential Page 97 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Select the entry Z888 and go to Accesses. Put your table 888 here.

The field should get grayed out. Select the condition table
and go to . You’ll reach the following screen.

L&T Infotech - Confidential Page 98 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Go back to previous screen.

L&T Infotech - Confidential Page 99 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Save the access sequence.

6.3 Create a condition type – V/06

Create condition type Y888 and assign the access sequence Z888. Now your condition
table 888 is finally linked to your condition type Y888.

6.4 Creating Condition records for condition type – VK11

Select key combination to see which condition table has been assigned to the access
sequence of this condition type. You see the description of the condition table.
L&T Infotech - Confidential Page 100 of 730
 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Enter the Price.

6.5 Create Pricing procedure with condition type Y888. – V/08

L&T Infotech - Confidential Page 101 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

6.6 Determine the pricing procedure in the Sales Order – Tcode OVKK

6.7 In the sales order, the price gets automatically picked up

At the bottom of the screen, you see

6.8 Linking Condition table to the Condition Type

L&T Infotech - Confidential Page 102 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

A condition table has no use till it is assigned to a condition type, because what you see
in the sales order is the condition type. Condition type Rules the sales order.

This assignment is not a direct assignment. I.e. the condition table is not directly
assigned to the condition type.

First the condition table is assigned to the Access Sequence. Then, the access sequence is
assigned to the condition type.

A condition type on its own has no use unless it is assigned to a pricing procedure. The
pricing procedure is finally determined in the sales order.

• Create a condition table 888.

• Create an access sequence Z888– Assign condition table 888 to this access
sequence
• Create a condition type called Y888.
• Assign the access sequence Z888 to the condition type Y888.
• Create a pricing procedure Y000 with the condition type Y888.

L&T Infotech - Confidential Page 103 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Day 7: 08-Feb-2011
7.0 Pricing
7.1 Pricing with multiple condition tables in an access sequence

Business Scenario:
Product M-100 has a price of 1000 for all customers.
One customer 5555 has a long relationship with the company. We want to give him
Product M-100 for 800.
We need to map this in SAP without resorting to Manual Pricing.

7.1.1 Create 2 condition tables: Customer/Material & Material

7.1.2 Assign the access sequence to the Condition type

L&T Infotech - Confidential Page 104 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

7.1.3 Create Condition record for customer/Material 5555 / M-100 = 800 EUR

7.1.4 Create Condition record for M-100 = 2000 EUR. This applies to all other
customers.

L&T Infotech - Confidential Page 105 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

7.1.5 In the sales order, the system accesses each table in the access sequence
sequentially i.e. check first table, then second table etc.

If condition record exists in any of the tables, the access stops. The system does not hunt
further. The pricing analysis is seen in the pricing screen.

L&T Infotech - Confidential Page 106 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

7.2 Importance of Exclusive Checkbox in the Access Sequence

Note: The system accesses the records of all the condition tables in the access sequence.
The last record it finds is the active record. This is shown in Green.

L&T Infotech - Confidential Page 107 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

7.3 Condition Class of the Condition type

There are 3 types of condition types:

• Price
• Discounts/Surcharges
• Taxes

L&T Infotech - Confidential Page 108 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

7.4 Pricing Procedure with multiple condition types of condition class B

(PRICE).

L&T Infotech - Confidential Page 109 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Note:
• There can only be one active condition type of class B in a pricing procedure.
• If there is more than one condition type of class B, the last one in the pricing
procedure is active. All others become statistical or inactive.

7.5 Condition types with Condition Class A (Discounts & Surcharge)

L&T Infotech - Confidential Page 110 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Create a pricing procedure with one pricing condition type (Class B) and 2 discount
conditions types (Class A).

Maintain Condition records for K004 and ZMDS.

L&T Infotech - Confidential Page 111 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

In the sales order,

Note:
• Multiple Discount Condition types (Class A) is allowed in the sales order

7.6 Discount Condition type with Calculation type Percentage

Business Scenario: We want to give a percentage discount to a customer based on the

Main Price.

L&T Infotech - Confidential Page 112 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

In the pricing procedure, put this discount condition type and refer it the price using the
field FROM.

Maintain Condition record for K007.

In the Sales Order,

L&T Infotech - Confidential Page 113 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

7.7 What happens when you don’t put FROM in the percentage discount

L&T Infotech - Confidential Page 114 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The system calculates the net value of all the active condition types and calculates the
percentage on this.

7.8 Statistics Field in Pricing Procedure

L&T Infotech - Confidential Page 115 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Statistical values are not taken in the Net Value Calculations.

Statistical lines in the pricing procedure are normally used to help in calculations of
other condition types or put condition values for information.

7.9 Creating sub-totals in pricing Procedure (From / To)

L&T Infotech - Confidential Page 116 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Note: if you don’t maintain from and to, the system takes all the active condition types
automatically.

L&T Infotech - Confidential Page 117 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

7.10 Manual Checkbox in Pricing Procedure

In the sales order, the condition type with manual checkbox does not automatically get
determined. You have to maintain it manually irrespective of whether condition records
exist or not.

L&T Infotech - Confidential Page 118 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

7.11 What happens when you select Checkbox Required (Discount

condition types) ? – To be checked

7.12 What happens when you select checkbox Manual and Required

IN the sales order, you get a pricing error that the condition type has not been
maintained.

L&T Infotech - Confidential Page 119 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 120 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Note: Required Entry works in tandem with the Incompletion Log.

7.13 Sub-Totals in the Pricing Procedure (KZWI1 to KZWI6)

Sales order item details are stored in table VBAP. This table has 6 fields KZWI1 to KZWI6.

In the pricing procedure put Sub Totals 1 and 6 to our condition types.

L&T Infotech - Confidential Page 121 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

In the Sales Order,

On saving the sales order, VBAP table fields KZWI1 and KZWI6 gets populated.

L&T Infotech - Confidential Page 122 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

These subtotals from Table VBAP are used in Reporting.

7.14 Viewing Sales Order Pricing in database

Sales Order Pricing is stored in table KONV.

L&T Infotech - Confidential Page 123 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The document condition is first found in table VBAK.

First find the value KNUMV in the table VBAK. Use this value in table KONV along with
sales order item no. to retrieve the sales order item level pricing.

7.15 Viewing Condition records in database

L&T Infotech - Confidential Page 124 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Note: 2 entries exist in this table because of different validity dates. Each entry
generates its own condition record number.

From Table A889 find the condition record number. Use this condition record number in
table KONP to find the condition record details.

L&T Infotech - Confidential Page 125 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 126 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

7.16 Requirement Routine

This is a piece of ABAP code which deactivates the condition type in the sales order if
certain requirement is not met.

Example: If delivering plant is not there in the item level, do not allow the condition
type to be active.

In the item category: Select No Pricing

In the pricing procedure select requirement 2.

L&T Infotech - Confidential Page 127 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

In the sales order, the requirement routine checks the item category for Pricing. It does
not find an entry and deactivates the condition.

7.17 Concept of Condition Base value and Condition Value

If Rate = $1000
Quantity = 5 (Calculation type Quantity) - Condition Base Value
Total = $5,000 – Condition Value

L&T Infotech - Confidential Page 128 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

8.0 Condition type Settings

8.1 Plus/Minus

If you put Blank, the system will allow both positive and negative values.
If you put A, the system will allow only positive values.
If you put X, the system will allow only negative values.

L&T Infotech - Confidential Page 129 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

8.2 Calculation type – Quantity

The calculation type controls the condition base value in the sales order. The calculation
type Quantity uses the sales order item quantity as the condition base value.

The calculation type from the condition type gets defaulted in the condition record. If
any changes are made thereafter, the condition record has to be recreated again, else
the changes will not reflect in the sales order.

L&T Infotech - Confidential Page 130 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

8.3 Calculation type – Gross Weight

L&T Infotech - Confidential Page 131 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

8.4 Calculation type – Fixed Amount

In the sales order, irrespective of the quantity the price is fixed.

L&T Infotech - Confidential Page 132 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Note: Condition Base value for fixed amount condition type is 0.

L&T Infotech - Confidential Page 133 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

8.5 Changes which can be made – Item Conditions

8.5.1 Deselect the Amount/Percent

You cannot change the condition rate manually in the sales order.

8.5.2 Deselect the Amount percent as well value

L&T Infotech - Confidential Page 134 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

8.6 Changing the calculation type in the sales order

L&T Infotech - Confidential Page 135 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Now the calculation type can be changed in the sales order.

Now you can change it to say B (Fixed Amount).

L&T Infotech - Confidential Page 136 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

8.7 Deleting Condition types in the Sales Order

L&T Infotech - Confidential Page 137 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Now you can delete this condition type in the sales order by selecting the condition type

and hitting the delete indicator at the bottom of the screen.

8.8 Deleting Condition Records

8.8.1 Do not delete

Delete condition records by selecting the item and hitting icon .

L&T Infotech - Confidential Page 138 of 730
 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

8.8.2 Delete with Popup

8.9 Condition Record Validity Proposal during VK11

During creation of condition records, the validity dates are proposed by the system.

L&T Infotech - Confidential Page 139 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

9.0 Delivery Processing – 17.20 hours

A sales order has to be delivered. Deliveries are controlled by the delivery document
type.

9.1 Configure Delivery type – Tcode 0VLK

L&T Infotech - Confidential Page 140 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

9.2 Configure Delivery Item Category – Tcode 0VLP

The delivery item category is an extension of the sales item category.

L&T Infotech - Confidential Page 141 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

9.3 Put the delivery type in the sales document type

L&T Infotech - Confidential Page 142 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

9.4 Pre-requisites for creating a delivery

9.4.1 The shipping point has to be determined in the sales order.

9.4.2 Copy Control settings have to be made between Sales document type and
delivery type – Tcode VTLA

In the copy control, copy standard settings of OR-LF-TAN

Select .

L&T Infotech - Confidential Page 143 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

9.5 Storage Location Determination in the Delivery – Tcode OVL3

Picking location is determined in the delivery based on shipping point, plant and storage
condition.

Storage condition is a field in the material master.

L&T Infotech - Confidential Page 144 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

9.6 Maintain material master for storage location

L&T Infotech - Confidential Page 145 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

9.7 Route Determination

9.7.1 Define a Route – Tcode OVTC

L&T Infotech - Confidential Page 146 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 147 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

9.7.2 Tcode 0VRF – Route Determination

9.7.3 County of Departure / Departure Zone is maintained in the Shipping Point.

9.7.4 Receiving Country / Receiving Zone are maintained in the Ship to Party (Master
Data)

L&T Infotech - Confidential Page 148 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

9.7.5 Material master, maintain the transportation group in Sales: General/Plant data
(Master Data)

9.7.6 Route Determination in the Sales Order.

• The system reads the departure country / zone from the shipping point
• Then it reads the Receiving country/zone from the Ship to Party
• Then it reads the Shipping condition from the sold to party
• Then it reads the transportation group from the Material master

L&T Infotech - Confidential Page 149 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Day 8: 09-Feb-2011
10.0 Material Master
10.1 General Item Category group versus Item Category Group

The General Item Category is found in the basic data screen of the material master and
not dependent on Sales Organization and Distribution Channel. This field can have only
one value irrespective of the Sales organization and distribution channel.

L&T Infotech - Confidential Page 150 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The item Category Field is found in the Sales: Sales Org 2 Screen. This field can have
different values for different Sales Organization and Distribution Channel.

During Item Category Determination: Sales Document type + Item Category group = Item
Category, the item category group is first read from the field Item Category Group. If no
entry exists here, the General item category group is taken.

11.0 Delivery Processing

11.1 Delivery and Transportation Scheduling

L&T Infotech - Confidential Page 151 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

11.1.1 Define Scheduling By Sales Document Type

11.1.2 Define Scheduling By Shipping Point

11.1.3 Calculation of Goods Issue Date – Backwards Scheduling

The goods issue date = Required Delivery date – Transit Time.
The transit time is maintained in the Route.

L&T Infotech - Confidential Page 152 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

11.1.4 Forward Scheduling – Calculating Delivery Date from Goods Issue Date

If the required delivery date is today, but the transit time is 10 days, the system will
propose delivery date of today + 10 days. A new schedule line is created for today + 10
days. Today’s schedule does not get deleted – it just shows that confirmed quantity is
zero for today.

L&T Infotech - Confidential Page 153 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

11.1.5 Calculation of Loading Date

Loading Date = Goods Issue Date – Loading time

Loading time determination is controlled in the shipping points.

L&T Infotech - Confidential Page 154 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

11.1.6 Material Availability Date

Material Availability date = Loading date – Pick/Pack time.

11.1.7 Transportation planning date

Transportation Planning date = Loading Date – Transportation Lead time.

Transportation Lead time is defined in the Route.

L&T Infotech - Confidential Page 155 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

11.2 When is a sales order due for delivery?

A sales order is due for delivery on the material availability date or transportation date,
whichever comes first.

If you try to create a delivery earlier, you get the following error message.

L&T Infotech - Confidential Page 156 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

11.3 Rounding Workdays in shipping point

(To be done)

12.0 Invoicing

A sales order which is delivered has to be billed. Billing is controlled by the billing
document type.

L&T Infotech - Confidential Page 157 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

12.1 Billing document type – Tcode VOFA

12.2 Assign the billing document type to the Sales document type

L&T Infotech - Confidential Page 158 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

12.3 Copy Control settings – Delivery to Billing: Tcode VTFL

L&T Infotech - Confidential Page 159 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

12.4 Create Individual Billing Document – Tcode VF01

11.52 hours

L&T Infotech - Confidential Page 160 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

.. 11.55 hours

The document flow of the sales order gives the delivery and billing document numbers.

L&T Infotech - Confidential Page 161 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Day 9: 14-Feb-2011
13.0 Revenue Account Determination

When a customer gets billed, an accounting document gets created. In case of credit
sales, the customer account gets debited and the revenue account gets credited. When
payment comes in, customer account gets credited and bank A/c gets debited. The final
net entry for sales looks like this:
Debit Bank A/c
Credit Revenue A/c

13.1 Assign Account key in the Pricing Procedure – Tcode V/08

L&T Infotech - Confidential Page 162 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

13.2 Assign Account determination Procedure to Billing type –

Tcode VOFA

13.3 Account Determination Procedure

13.3.1 Define Account Determination Procedure

The standard account determination procedure contains Condition Types KOFI.

L&T Infotech - Confidential Page 163 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

13.3.2 Account determination type KOFI

Account determination type KOFI is assigned to access sequence KOFI.

13.3.3 Access sequence KOFI

L&T Infotech - Confidential Page 164 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

13.3.4 Condition Tables in access sequence KOFI

L&T Infotech - Confidential Page 165 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 166 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 167 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 168 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

13.3.5 Condition table fields in master data

Field KTGRD – Customer Account Assignment Group: This is found in the Billing tab of
Sales Area data of customer.

L&T Infotech - Confidential Page 169 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Field KTGRM – Material Account Assignment Group.

L&T Infotech - Confidential Page 170 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

13.4 Maintain G/L Accounts (Master Data) for Revenue

Determination - VKOA

We want the Revenue Account to be determined based on Sales Organization + Customer

Account Assignment Group (KTGRD) + Material Account Assignment Group (KTGRM) +
Account key.

If this was pricing we would gone to VK11 and entered values in table 1 for condition type
KOFI. In Revenue account determination, master data maintenance is done in
Configuration directly on condition table and not condition type.

Note: Here you see all the revenue determination condition tables irrespective of what
the access sequence, what the condition type is or what account determination
procedures are.

When the condition table gets generated, the system automatically adds fields
Application, Condition type and chart of accounts.
L&T Infotech - Confidential Page 171 of 730
 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

13.5 Create a Sales Order

The customer account assignment group gets picked up from the Payer in the sales order.
This can be changed in the sales order.
Note: The account assignment group is always picked from the Payer. If entries exist in
the sold to party and not the payer, this field remains blank in the sales order.

The material Account assignment group gets picked up in the item level. This cannot be
changed in the sales order.

L&T Infotech - Confidential Page 172 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

13.6 Create a Billing document

L&T Infotech - Confidential Page 173 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The customer account assignment group can be changed in the billing document before
posting.

L&T Infotech - Confidential Page 174 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The material account assignment group can be changed at the item level.

13.7 Analysis of Revenue Account Determination

L&T Infotech - Confidential Page 175 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The billing document flow gives the accounting document number.

13.8 Viewing Reconciliation Account in the Account Document

generated from Billing

Note: In a credit sale, the customer gets debited. In the balance sheet, a parallel entry is
made in the debtors Account (reconciliation account).

L&T Infotech - Confidential Page 176 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The debtor’s account comes from the Payer master – Company code data.

L&T Infotech - Confidential Page 177 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

13.9 Posting Block in billing type – Tcode VOFA

If you select the checkbox Posting Block in billing type, accounting document does not
get automatically generated during billing. It has to be manually carried out.

Select Icon .

The accounting document gets created now.

L&T Infotech - Confidential Page 178 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Summary
1. Account determination procedure KOFI00 assigned to billing type F2
2. Account determination procedure KOFI00 has account determination type KOFI
3. Acc Determination type KOFI has access sequence KOFI
4. Acc sequence KOFI has first table 1 with fields
• Sales org
• Customer assignment group
• Material Account assignment group
• Account key.
The Condition table generation adds application, condition type and chart of
accounts automatically as added table keys.

Customer Master / Material Master / Pricing Procedure

• Customer account assignment group 01 - customer master
• Material account assignment group 03 - material master
• Account key ERL - pricing procedure

6. Maintain G/L Account - master data maintenance in customizing.

Application V
Condition type KOFI
Chart of Accounts INT
CAAG 01
L&T Infotech - Confidential Page 179 of 730
 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

MAAG 03
= G/L A/c 800000

9. The customer account assignment group is picked up from the Payer.

13.10 Viewing Customer Balances – Tcode FD10N

The customer balances are always viewed for a Payer. This is done for a company code
and a fiscal year.

L&T Infotech - Confidential Page 180 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

When you double click a line, you see the accounting documents generated for the
period.

To view individual billing document, double click an accounting document,

L&T Infotech - Confidential Page 181 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 182 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

14.0 Material Listing and Exclusion

Business Scenario: We have say, 2000 materials in our Price List. I have a deal with a
customer to supply only Material X-100. No other material is to be given to him.

14.1 Material listing – Condition Technique

L&T Infotech - Confidential Page 183 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

14.1.1 Create condition table – Tcode OV06

L&T Infotech - Confidential Page 184 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

14.1.2 Create Access Sequence

14.1.3 Create Listing type and assign Access Sequence

L&T Infotech - Confidential Page 185 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

14.1.4 Procedures for maintaining listing

14.1.5 Activate listing by sales document type

14.1.6 Create Condition Records for Listing – Tcode VB01.

L&T Infotech - Confidential Page 186 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 187 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

14.2 Material Exclusion

Using Material Exclusion: All configurations are same except that you put the procedure
against Exclusion in the Sales document type.

L&T Infotech - Confidential Page 188 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Day 10: 15-Feb-2011

15.0 Reconciliation Account Determination

The reconciliation account is taken from the company code data of the Payer.

L&T Infotech - Confidential Page 189 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Suppose customer 862 is used in both domestic as well as export transactions. Different
debtors accounts are to be used for domestic as well as exports. We want to dynamically
determine the reconciliation account during billing.

L&T Infotech - Confidential Page 190 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

15.1 Reconciliation Account Procedure

15.2 Condition type KOAB and Access Sequence KOAB

L&T Infotech - Confidential Page 191 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

A database table with Prefix C gets generated in the background.

L&T Infotech - Confidential Page 192 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

15.3 Assign Account determination procedure to billing type

15.4 Assign G/L Accounts

L&T Infotech - Confidential Page 193 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Note: Only after the condition table is assigned to an access sequence and the access
sequence is assigned to the condition type, you can assign G/L Accounts.

15.5 Define Alternative Reconciliation Accounts

Put the alternate reconciliation account allowed for the customer here.

L&T Infotech - Confidential Page 194 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

15.6 Reconciliation Account determination in the billing document

L&T Infotech - Confidential Page 195 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

16.0 Material Master – Pricing Reference Material

Business Scenario: The price of Material M-863 is always same as M-862.

L&T Infotech - Confidential Page 196 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

With this setting, we don’t have to create condition records for M-863 separately. We
just put in the material master that M-863 pricing is same as M-862 (Pricing Reference
Material field).

17.0 Customer Master - Transaction Dependent Screen Layouts –

Tcode OB20

You can make customer master screens suppressed, display, Optional, required entry
based on Transaction codes XD01/2/3, FD01/2/3, VD01/2/3.

Note: This is not dependent on any Account Group.

L&T Infotech - Confidential Page 197 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 198 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Now, when we go to VD02, the customer fields which are in display mode above cannot
be entered.

L&T Infotech - Confidential Page 199 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 200 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

17.1 Account Group vs. Tcode Settings

Account Group Tcode Setting Effect in Tcode Precedence

Setting
1. Suppressed Required Account Group
Optional Suppressed Account Group
Display Account Group
2. Required Suppressed Suppressed Tcode
Optional Required Account Group
Display Display Tcode
3. Optional Suppressed Suppressed Tcode
Required Required Tcode
Display Display Tcode
4. Display Suppressed Suppressed Tcode
Required Display Account Group
Optional Display Account Group

18.0 Sales Document type

18.1 Sales Document – Sub Item

In the sales document type, you put the sub-item increment as 1.

L&T Infotech - Confidential Page 201 of 730
 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Example: A Computer consists of CPU, Mouse, Monitor and Keyboard. These are separate
stock items sold together. If you enter the four components separately, there won’t be a
link that it is part of a single product. In this case we create a material master called
Computer and put the 4 components as sub-items. The computer is the higher level item
to the sub-items.

Item Category Determination for Sub Item:

So far for normal item category determination, we have the following setting.

L&T Infotech - Confidential Page 202 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

18.2 Pricing Date in the Sales Order

Pricing date is found in the sales order in Header – Sales Tab.

L&T Infotech - Confidential Page 203 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

If you leave the Prof.f.pricing date blank, it proposes the current date. If you select A, it
proposes the pricing date = requested delivery date.

The pricing condition records get picked up according to the date in the pricing date.

18.3 Pricing Date in Individual Condition types

18.3.1 When you leave the field blank, condition records are picked based on
Pricing Date

L&T Infotech - Confidential Page 204 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

18.3.2 When the condition type has Pricing date as E, it takes the document
date for pricing.

L&T Infotech - Confidential Page 205 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

18.3.3 When condition type has pricing date as A (Date of Services Rendered)

Note: If you leave this field blank, the system takes required delivery date.

18.3.4 When condition type has Pricing date as C (Billing date)

L&T Infotech - Confidential Page 206 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

18.4 Date type

If you choose date type Month, the effects are seen in the following:

18.4.1 Requested delivery date

L&T Infotech - Confidential Page 207 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

18.4.2 Pricing Date

18.4.3 Schedule Lines

Note: If you select Week,

The pricing date will be first date of the week

L&T Infotech - Confidential Page 208 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

18.5 Immediate Delivery

On saving the sales order, the delivery automatically gets created.

19.0 Item Category Settings

19.1 Billing Relevance
For billing to happen select Billing relevance as A (delivery related billing) or billing will
not happen.

L&T Infotech - Confidential Page 209 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

20.0 Billing
20.1 Billing type – Document Pricing Procedure
Pricing procedure is redetermined in the billing document if we maintain DOPP in the
billing document type.

20.2 Release Billing Documents for Accounting – Tcode VFX3

L&T Infotech - Confidential Page 210 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 211 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

21.0 Material Determination

Business Scenario: You have been selling Material X all these years. This material has got
phased out and has been upgraded to Material Y. When you enter Material X, the system
should determine Material Y.

21.1 Material Determination Procedure

21.2 Condition type, Access Sequence and Condition Tables

L&T Infotech - Confidential Page 212 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

This generates a database table KOTD001.

L&T Infotech - Confidential Page 213 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

21.3 Assign Material Determination Procedures to Sales Document

Types

21.4 Maintain Material Determination Condition Records – VB11

L&T Infotech - Confidential Page 214 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

In the sales order, when you put M-862 as the line item, the system automatically
replaces it with material M-863.

21.5 Substitution Reasons – Tcode OVRQ

21.5.1 Warning

Put substitution reason in the material determination condition record.

L&T Infotech - Confidential Page 215 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

21.5.2 Strategy

When you put setting A (Substitute products are displayed for selection)

L&T Infotech - Confidential Page 216 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

You have a choice here of selecting or not selecting the substituted product.

21.5.3 Outcome

Outcome A works only for automatic strategy. i.e. field strategy should be blank.

L&T Infotech - Confidential Page 217 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

21.6 Sales Order Entry

The original material entered can be seen in the Item – Sales A Screen.

21.7 Item Category determination for sub-items specific to material

determination - Outcome A

L&T Infotech - Confidential Page 218 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 219 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

21.8 Item Category determination for sub-items specific to material

determination - Outcome B

L&T Infotech - Confidential Page 220 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Day 11: 16-Feb-2011

22.0 Pricing
22.1 Header Conditions

A condition type is defined as a header condition by selecting checkbox ‘Header

Condition’.

You cannot put an access sequence in a header condition type. If you try, you get the
following message:

The header condition type is put in the pricing procedure as a discount.

In the sales order

L&T Infotech - Confidential Page 221 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 222 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Header conditions work only if it is activated.

L&T Infotech - Confidential Page 223 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The header condition value is distributed to the items in proportion of their net value.
i.e. if the net value of first item is 5000 and second item is 15,000, a discount of 1000 get
distributed in 5000/20000 x 1000 = 250 and 15000/20000 x 1000 = 750.

L&T Infotech - Confidential Page 224 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

22.2 Scales
Business Scenario: The product pricing is based on volumes lifted.
1 – 100 EA: 1000 EUR
101 – 200 EA: 900 EUR
200 onwards EA: 800 EUR

The scales are configured in the condition type:

L&T Infotech - Confidential Page 225 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

In a Descending scale, the amounts will be descending.

22.2.1 Scale type: To

L&T Infotech - Confidential Page 226 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

In this case 0 – 100: Price is 1000 EUR, from 101 – 200, the price is 800. No price is
allowed for quantities from 201 onwards.

22.2.2 Graduated-to Interval Scale

L&T Infotech - Confidential Page 227 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

22.3 Condition type VPRS

L&T Infotech - Confidential Page 228 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Subtotal B -

VPRS condition type has condition category G.

Condition type VPRS gets in the material cost from the material master.

L&T Infotech - Confidential Page 229 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Day 12: 17-Feb-2011

23.0 One Time Customer
Business Scenario: Cash Customers and Non Repeat Customers do not have to be
maintained as regular customers.

In SAP, Account Groups CPD (internal number range) and CPDA (Alphanumeric number
range) are used for one time customers.

23.1 Account Group CPDA

L&T Infotech - Confidential Page 230 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

23.2 Maintain a One-Time Customer – Tcode VD01

L&T Infotech - Confidential Page 231 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 232 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

23.3 Create a Sales Order for One-time Customer

You get a pop-up to enter the one time Customer address details.

Save the Sales Order. All one-time Sales Order is created for the same customer code
with different addresses.

L&T Infotech - Confidential Page 233 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

23.4 Delivery and Billing of one time customers

The delivery is created out as usual for one time customers. Billing should be done with a
billing type with Cash Account Determination. This prevents the one-time customers
going into Accounts Receivables.

Note: There are clients who put one time customers as receivables too. FI Consultants
should be closely involved here to define the process.

24.0 Cash Account Determination

Business Scenario: There are 2 types of sale: cash sale and credit sale. Receivables or
debtors get generated for credit sale which is converted to cash later. In a cash sale,
cash comes n directly. i.e. goods are sold on cash and not on credit.

In SAP, cash sale is handled through cash account determination. The end result of this is
the Cash or Bank A/c should be debited and not the customer A/c.

24.1 Create Cash Account Determination Procedure – Tcode OV76

L&T Infotech - Confidential Page 234 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

24.2 Assign Cash Account Determination Procedure to the Billing

type – Tcode OV78

You assign the cash account determination procedure to the billing type.

Note: A billing document type cannot have both cash account determination and
reconciliation account determination. Also, revenue account determination is still
required with a cash account.

L&T Infotech - Confidential Page 235 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

24.3 Assign G/L Accounts – Tcode OV77

24.4 Create a billing document

The cash account gets debited instead of the customer.

24.5 Account determination analysis

L&T Infotech - Confidential Page 236 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

25.0 Proforma Invoice

Definition 1: Proforma invoice is a preliminary document used to declare the value of

the trade. It can be issued before the transaction to facilitate customs and payment
arrangements. This document models the final commercial invoice, and may look just
like the commercial invoice except for the Pro forma invoice heading, but can also omit
minor details.

Definition 2: A price quote that a potential seller gives to a potential buyer that details
the sale price and any applicable commissions and fees. It is given in the form of an
L&T Infotech - Confidential Page 237 of 730
 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

invoice. A Proforma invoice exists in order to give a potential buyer a precise figure of
the final cost of a transaction. This helps the buyer in making his/her investment
decisions. The Proforma invoice also helps the seller avoid ill feelings that may result
from unexpected fees charged to the buyer, which could drive away future business.

25.1 Define a Proforma Invoice – Tcode VOFA

In SAP, Proforma invoices are billing documents with SD document category U. Proforma
Invoices do not generate accounting documents irrespective of whether we assign
account determination procedures to it.

25.2 Order and Delivery Related Proforma Invoices

Note: There are 2 types of Proforma invoice

1. Delivery related Proforma Invoice (F8) - used in Exports and is a legal requirement.
2. Order Related Proforma invoice (F5) - price quotes before deliveries are made.

L&T Infotech - Confidential Page 238 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

25.3 Copy Control Settings – Proforma Settings

Maintain copy control from delivery to billing (Tcode VTFL) for Proforma invoice
(standard is F8).

For order related billing, maintain billing quantity C and for delivery related Proforma
Invoice maintain billing quantity D.

25.4 Multiple Proforma Invoices per Document

L&T Infotech - Confidential Page 239 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Unlike a normal invoice (one invoice for one delivery), you can have multiple Proforma
invoices for a single delivery.

26.0 Removing Revenue Account Determination from Billing type

If you remove the revenue account determination procedure from the normal billing
type, no accounting document will get created. No error messages will be shown either.-
keep in mind.
Note: If revenue account determination procedure is removed from a billing document by
mistake, the accounting will go haywire - KEEP IN MIND !!!!!

27.0 Combining Sales Organization

We have a sales organization 1000 with 3 sales areas and assigned to the following
document types:
1000-00-00: OR
1000-00-10: ZOR
1000-00-20: YOR

We have a new sales organization 1020 and 1030 which is a mirror of sales organization
1000 and has similar combinations of distribution channels and divisions and documents
types.

1020-00-00: OR
1020-00-10: ZOR
1020-00-20: YOR

L&T Infotech - Confidential Page 240 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

And

1030-00-00: OR
1030-00-10: ZOR
1030-00-20: YOR

The document type assignment is normally done through Tcode OVAZ. Instead of this,
this can be done by the combining Sales Organization (for document types) functionality.

Note: For sales organization 1020 and 1030, the combine distribution channel and division
should also be maintained.

This is just OVAZ simplification – This has nothing to do with master data maintenance.

Day 13: 18-Feb-2011

28.0 Order Related Billing

In case of transactions which do not require delivery, e.g. services, billing can be directly
based on the sales order.

The item category controls order related billing.

The Billing relevance should be B (Relevant for order-related billing - status acc.to order
qty)

L&T Infotech - Confidential Page 241 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

TCode VTFA - Copy control from Order type to Billing type.

In VOV8, put the order related billing type.

L&T Infotech - Confidential Page 242 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Now, if you try to create a billing document again once all the order quantity has
been billed, the system does not allow this. This is because the Pos/Neg. quantity is set
to (+)

29.0 Copy Control – Order to Billing

29.1 Pos/Neg Quantity = 0.

If you use (+), if the order quantity is 10 and the billing quantity is 10, the System
calculates balance quantity to be invoiced as 10 - 10 = 0. You cannot bill the order
further. Also, the order quantity cannot be changed now.

If you use (0), if the order quantity is 10 and the billing quantity is 10, the system does
not calculate any balance. You can now create as many billing documents from the
order. i.e. the system does not check if the item has already been billed earlier. After
you have billed once, the system allows the order quantity to be changed. This is not
possible when you use (+).

L&T Infotech - Confidential Page 243 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

29.2 Billing Quantity

• A for order-related billing

• B for delivery-related billing
• C and D for pro forma invoices
• E, F and I for a third party business transaction
• G and H for batches

29.3 Copy Control: Order to Billing – Pricing Type

29.3.1 Pricing type G - Copy pricing elements unchanged and redetermine taxes

L&T Infotech - Confidential Page 244 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Example: We put condition type Z001 as manual price.

Now in the order, we change the price to 666 EUR. The billing document also
takes this manually changed value i.e. 666.

L&T Infotech - Confidential Page 245 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

29.3.2 Pricing type B- carry out new pricing

If you use pricing B, all changes in the sales order are disregarded. During billing
pricing is carried out again.

L&T Infotech - Confidential Page 246 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

29.3.3 Pricing type C - Copy manual pricing elements and redetermine the
others

In the sales order,

L&T Infotech - Confidential Page 247 of 730
 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

In the billing document, the system copies the manual condition type and recalculates
the condition record.

Note: Be very careful while using both B as well as C. the sales order price is negotiated
and the customer may not take kindly if the price is increased in billing.

30.0 Pricing

30.1 Pricing – Condition type ‘Accrual checkbox’

Condition type K004.

L&T Infotech - Confidential Page 248 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

With the accrual checkbox,

Without the accrual checkbox,

The accrual checkbox results in the condition type automatically statistical in the sales
order pricing irrespective of whether it is marked statistical or not in the pricing
procedure.

L&T Infotech - Confidential Page 249 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

30.2 Condition type Setting - Reference Condition type

The field reference condition type is not seen if the access sequence is not there.

The field gets activated when you put the access sequence.

L&T Infotech - Confidential Page 250 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

In our example, condition type Z004 with access sequence Z001 refers Condition type
Z001 in application V.

Important: Both the condition type Z001 and Z004 should refer to the same condition
table for this to work. Here the condition table is 862.

Note: the condition index checkbox gets ticked and is in display mode.

The new condition type is now put in the pricing procedure.

L&T Infotech - Confidential Page 251 of 730
 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Create condition records for condition type Z004.

Day 14: 21-Feb-2011

31.0 Delivery Processing
31.1 Picking Location Determination

This functionality is only for the delivery. For the sales order, storage locations are put in
manually and too when you want to lock the storage location in the delivery.

L&T Infotech - Confidential Page 252 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Picking location does not get determined automatically if storage location field is
populated in the sales order. In this case, the sales order storage location gets copied
into the delivery.

The delivery item category should have Stlocation required and Determine Sloc checkbox
active. Tcode 0VLP.

Storage location determination Tcode is found in Tcode OVL3.

Storage Conditions are found in the material master.

L&T Infotech - Confidential Page 253 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

During Creation of a delivery, the storage location gets automatically determined.

In the Item  Picking View, you see the storage condition as well as the plant.

L&T Infotech - Confidential Page 254 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The shipping point as well as Route is seen in the view Header  Shipment

L&T Infotech - Confidential Page 255 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

31.2 Reversing Goods Issue

L&T Infotech - Confidential Page 256 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 257 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Select

L&T Infotech - Confidential Page 258 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

You cannot reverse a goods issue before the date of the goods issue. Put the correct date
and do the reversal again.

The system creates a reversal document. This can be seen in the document flow.

L&T Infotech - Confidential Page 259 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Both the stocks and the accounting entries are reversed. The delivery is now again open
for goods issue.

Note: The goods issue reversal can be done as long as the billing document has not been
created.

31.3 Proof of Delivery

L&T Infotech - Confidential Page 260 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

31.3.1 Set POD relevance of Item Category

31.3.2 Reason for Variance in POD

L&T Infotech - Confidential Page 261 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

31.3.3 In the ship to Party, maintain POD Relevance

31.3.4 Try doing billing before 7 days of goods issue

L&T Infotech - Confidential Page 262 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

31.3.5 Enter Proof of Delivery – Tcode VLPOD

L&T Infotech - Confidential Page 263 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

In case of delivery shortage, put reason DFG2 (defined as negative in configuration) and
put shortage quantity as 2.

Confirm proof of delivery by selecting icon . Once this is done, everything gets grayed
out.

31.3.6 Do the billing once the POD has been done

L&T Infotech - Confidential Page 264 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Note: The billing is done for delivery quantity minus shortages in our example.

32.0 Billing

32.1 Assignment Number & Reference Number in Billing

Reference Number:

L&T Infotech - Confidential Page 265 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The Reference number and assignment number is seen in the billing document header.

Now, Change the reference number to Purchase Order number.

L&T Infotech - Confidential Page 266 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The Reference number gets copied over to the accounting document.

L&T Infotech - Confidential Page 267 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

32.2 Reversing Billing document – Tcode VF11

This can also be done via VF02.

L&T Infotech - Confidential Page 268 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 269 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The cancellation billing document has same entries as original billing document.

L&T Infotech - Confidential Page 270 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

32.3 Cancellation Billing type

The cancellation billing type has to be in the billing type definition – VOFA.

L&T Infotech - Confidential Page 271 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The cancellation billing type S1 has the SD Document Category N – Invoice Cancellation.

It also has account determination procedure KOFI00. Note: Ensure this is not changed.

32.4 Negative Posting

When you reverse a billing document, FD10N i.e. customer balances show equal debit
and credit.

L&T Infotech - Confidential Page 272 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

In the cancellation document type S1, in the negative posting field, choose B.

L&T Infotech - Confidential Page 273 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

When a billing document is now cancelled, it knocks off all entries.

L&T Infotech - Confidential Page 274 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

33.0 Sales Order Processing

33.1 Sales Order Block

Blocks are defined in Tcode OVAS.

Assign Block to Sales Document type

When you create a sales order.

L&T Infotech - Confidential Page 275 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

34.0 Customer Master

L&T Infotech - Confidential Page 276 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

34.1 Blocking Customers

L&T Infotech - Confidential Page 277 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Note: The blocking reasons have to be assigned to the document types.

If you see the same screen via XD02.

L&T Infotech - Confidential Page 278 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

If the customer is blocked in the company code and all transactions allowed, the system
does not allow accounting entries during billing.

The functionality can be achieved using XD05.

L&T Infotech - Confidential Page 279 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

35.0 Material Master

35.1 Material Master Status

L&T Infotech - Confidential Page 280 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 281 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

In the material master, the block can be put in 2 fields.

• X-Distribution Chain Status
• Distribution Chain Status

Now when you create a sales order, you get the following error.

L&T Infotech - Confidential Page 282 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Note: The X-Distribution chain block supersedes the distribution chain block.

36.0 Pricing
36.1 Lower Limit and Upper Limit in the Condition Record

L&T Infotech - Confidential Page 283 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

In the sales order, if you go below or above the limit, the system does not allow you.

L&T Infotech - Confidential Page 284 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 285 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

37.0 Rebate Processing

Rebates are retroactive discounts given after the sale.

- Volume based rebate – Pick up 1000 pieces over 6 months and get an extra
discount of 5 EUR per piece
- Yearly Rebates – Over and above volume based rebates, give 3% discount overall
sales made during the year
- Promotional Rebates – Whatever the customer buys, he gets a rebate in a few days
during a time period
- Discounts are given immediately on an Invoice while rebates are given later

One or more Rebates may be operational on billing documents.

L&T Infotech - Confidential Page 286 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

37.1 Rebate Pre-Requisites

Activate Rebate Processing for Sales Organization – Tcode OVB1

Activate Rebate Processing for Billing type – Tcode OVB0

37.2 Rebate Condition Type/Access Sequence/Table

Pricing Condition type with condition class – C (Expense Reimbursement)

L&T Infotech - Confidential Page 287 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 288 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Rebate Condition Tables are created in Tcode OV20.

Rebate condition tables are stored as KOTE***

e.g. KOTE001.

L&T Infotech - Confidential Page 289 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

37.3 Put Rebate Condition type into Sales Order Pricing Procedure
Create a sub-total line called Basis for Rebate and put 7 in the subtotal field.

When you put the rebate condition type to To field, the Manual Entry field gets grayed
out. Requirement 24 means this rebate is calculated only in the billing document.

L&T Infotech - Confidential Page 290 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

37.4 Creation of Rebate Condition Type Groups

37.4.1 Define Condition type groups

37.4.2 Assign your rebate condition type/table to condition type group

L&T Infotech - Confidential Page 291 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

37.5 Creation of Rebate Agreements – VB(2

37.6 Assign Condition type group to Rebate agreement type – VB(5

L&T Infotech - Confidential Page 292 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

37.7 Assign Sales doc types R4, R3, B1, B2 to your sales area – OVAZ

37.8 Rebate Account Assignment – Tcode VKOA

37.9 Customer Master Payer – Prerequisites

L&T Infotech - Confidential Page 293 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

37.10 Master Data – Create Rebate Agreement Tcode VBO1

Rebate Recipient is always the payer.

L&T Infotech - Confidential Page 294 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

37.11 Maintain Rebate condition records in the rebate agreement

In pricing we maintain pricing condition records using VK11. In rebate we maintain rebate
condition records in rebate agreement.

L&T Infotech - Confidential Page 295 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

In the rebate pricing condition records, there are 2 values:

1. Amount
2. Accruals

The amount is the actual discount given.

Accruals are the estimated discount to be given. This is calculated in the billing
document.

The validity period of the rebate condition type gets carried over from the rebate
agreement.

37.12 Billing Document

The accruals (estimated rebate) get calculated in the billing document.

L&T Infotech - Confidential Page 296 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The rebate accrual is calculated in the billing document.

The Rebate accruals get debited to the ERU G/L Account & credited to the ERU
Provisional Account.

L&T Infotech - Confidential Page 297 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

37.13 Execute Program SDBONT06

Tcode SE38 – Run program SDBONT06.

L&T Infotech - Confidential Page 298 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

37.14 Rebate Payment

L&T Infotech - Confidential Page 299 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 300 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Once you have done the final settlement, the system does not allow any changes in the
rebate agreement.

L&T Infotech - Confidential Page 301 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 302 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Check the credit memo request that was created using Tcode VA02

L&T Infotech - Confidential Page 303 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Note: The credit memo request B1 has been put in the configuration of final settlement
in the rebate agreement type.

Create a credit memo from the credit memo request.

L&T Infotech - Confidential Page 304 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Dr Loss A/c (ERB G/L Account)

Cr Customer

The accrual entries are reversed.

37.15 Reversing Accruals without making Rebate Payment

• In VBO2, put any value in the final payment screen

• The system generates a credit memo request
• Go to the credit request using VA02 and make the rebate payment amount 0
• When you create a credit memo for this credit memo request, only the accrual
entries gets reversed

37.16 Manual Rebate Payments

Note: Manual Payments have to be activated in the rebate condition type.

L&T Infotech - Confidential Page 305 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The allowed drop down for payment procedure are:

The partial Payment document type R3 is configured here.

L&T Infotech - Confidential Page 306 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The rebate is paid out and accruals are reversed to the extent of rebate paid out.

Note: The payment amount and the accrual amount is the same here.
L&T Infotech - Confidential Page 307 of 730
 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Secondly, you cannot pay out more than you accrue. This is configured in the rebate
agreement type.

37.16.1 Reverse Accruals

The system reverses accruals for the amount of the manual payment. If the cumulative
accruals are not sufficient, the system reverses the accruals amount which exists.

The rebate is paid out, but the accruals are not reversed.

Manual Payment not allowed:

1. Manual Partial Payment screen gets deactivated

L&T Infotech - Confidential Page 308 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

2. Manual final payment not allowed either.

Payment can be made only automatically.

Manual Accruals

In the rebate agreement type, select manual accrual.

L&T Infotech - Confidential Page 309 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 310 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

37.17 Material for Settlement

L&T Infotech - Confidential Page 311 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Agreement Status C & D are used for final settlement.

L&T Infotech - Confidential Page 312 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Agreement Status C – When final settlement credit memo request has been created.
Agreement Status D – When final settlement billing has been carried out. i.e. credit
memo has been created.

37.18 Creating Manual Accruals

In the rebate agreement, select .

When you save, this creates a sales document of type credit memo request R4. A billing
document has to be manually created from this credit memo request.

L&T Infotech - Confidential Page 313 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 314 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

37.19 Rebate Processing – Accounting Overview

Billing A/c entries Rebate Payment a/c entries

Billing Normal entries
document 1 Debit Customer
Cr Revenue a/c
--------------------------------------------
Dr ERU A/c 1 - $100
Cr ERU A/c 2 (Provisional A/c) - $100
Rebate Cr Customer - $100
Payment Dr Loss A/c - $100 (ERB)

Reverse the accruals

Cr ERU A/c 1 - $100
Dr ERU A/c 2 (Provisional A/c)
- $100
Note:

Both the accrual accounts gets

nullified at the time of
payment. The final account
entry is
Cr Customer
Dr Loss A/c (ERB)

Day 15: 22-Feb-2011

38.0 Shipping
38.1 Route Re-Determination in the delivery based on weight group

L&T Infotech - Confidential Page 315 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

38.1.1 Define weight groups

Note: The Unit and Sequence No. is the unique fields in this table (TVLGZ).

38.1.2 Maintain Route Determination in sales order & delivery

L&T Infotech - Confidential Page 316 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

38.1.3 Define New Route Determination By Delivery Type

38.1.4 Define Allowed Actual Route by Proposed Route

L&T Infotech - Confidential Page 317 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The delivery Route gets redetermined.

38.2 Partial delivery per item – A (Create a delivery with Qty > 0)

L&T Infotech - Confidential Page 318 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 319 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

38.3 Partial Delivery per item – C (only complete delivery allowed)

L&T Infotech - Confidential Page 320 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

38.4 Maximum Partial Deliveries allowed

In the maximum partial deliveries allowed – put 2.

L&T Infotech - Confidential Page 321 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

You have an order with quantity 5 and create a delivery with quantity 1 as the first
delivery. The remaining 4 has to be delivered in the second delivery. Anything less than 4
gives an error/warning message.

L&T Infotech - Confidential Page 322 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

38.5 Specify Characteristics of system messages (variable messages

in shipping)
Tcode OVM1

38.6 Under Delivery tolerance

L&T Infotech - Confidential Page 323 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

38.7 Over delivery tolerance

In the Delivery item category Tcode 0VLP, select check Over Delivery.
L&T Infotech - Confidential Page 324 of 730
 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

In the customer master, maintain over delivery tolerance.

In the delivery, you get an error message if you cross the over delivery tolerance.

Note: If you put unlimited tolerance, the system does not look at the delivery item
category settings.

L&T Infotech - Confidential Page 325 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 326 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

38.8 Checking the partial delivery settings in the sales order

Note: These settings get copied from the sold-to party and not ship to party.

39.0 Sales
39.1 Sales Unit of Measure
Stocks are maintained inventory in the Base Unit of Measure.

L&T Infotech - Confidential Page 327 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

However, sales may happen in crates, box which store X no. of products in each. E.g.
coke is sold in Crates. Each crate consists of 24 bottles of Coke.

In the material master, go to the additional data screen.

L&T Infotech - Confidential Page 328 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

In our example, one crate consists of 50 EA of M-862

L&T Infotech - Confidential Page 329 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The sales unit is maintained in Sales: Sales Org 1 and can be different for each
distribution chain.

L&T Infotech - Confidential Page 330 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

When you create a sales order, the system automatically proposes the sales unit as the
unit of measure.

The system automatically calculates the condition base value as EA. i.e. 1 CRT = 50 EA
and carries out pricing.

L&T Infotech - Confidential Page 331 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

In the sales order, the option of changing the unit of measure is seen in the drop down.

If you do not want to change the sales unit in the sales order.

If you try to enter the order now, you get an error.

L&T Infotech - Confidential Page 332 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

All other units of measures not allowed for order entry.

L&T Infotech - Confidential Page 333 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Maintaining Prices for Sales UOM.

Note: The Sales UOM is automatically proposed. This can be changed in the condition
record.

39.2 Minimum Order Quantity

In the material master, put the minimum order in tab Sales: Sales Org 1

L&T Infotech - Confidential Page 334 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

When you create a sales order, the system gives a warning.

L&T Infotech - Confidential Page 335 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

39.3 Minimum Delivery Quantity

L&T Infotech - Confidential Page 336 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

When you try to create a delivery, the system gives a warning message.

L&T Infotech - Confidential Page 337 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

39.4 Delivery Unit

When you create a sales order,

When you create a delivery, you get the following warning logs.

L&T Infotech - Confidential Page 338 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

39.5 Variable Messages - OVAH

Certain system messages can be changed from warning to error using the Variable
message functionality. Not all messages are allowed to be changed.

The message number is first noted from the sales order.

L&T Infotech - Confidential Page 339 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Now change the message Category to E (error)

The options available are

L&T Infotech - Confidential Page 340 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

40.0 Inquiry – Tcode VA11

Business Scenario: A customer wants to know about a product. Prices are not
negotiated and only information is sent. This is put in the SAP as in Inquiry.
Inquiry is a sales document type with document category A, Screen Sequence group AG
and Transaction group is 1(Inquiry).

Inquiries are processed using transaction code VA11.

L&T Infotech - Confidential Page 341 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 342 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

40.1 Key Features of an Inquiry

Key Features of an inquiry are:
• Validity Period
• Expected order value = Probability percentage x Net Value
• Standard Item Category is AFN

You can also put in a product description without a product code. This is controlled by
the item category.

L&T Infotech - Confidential Page 343 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

40.2 Item type B – Text item

Item type B in the item category controls if an item in the sales order can be entered
without a product code.

L&T Infotech - Confidential Page 344 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

41.0 Quotation – Tcode VA21

Document Category B,
Screen Sequence Group AG,
Transaction group 2.

L&T Infotech - Confidential Page 345 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

41.1 Creating Quotation with reference to Inquiry

41.1.1 Copy Control from Inquiry to Quotation: Tcode VTAA

L&T Infotech - Confidential Page 346 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

41.1.2 Creation of Quotation VA21

L&T Infotech - Confidential Page 347 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Note: You cannot change the sold-to party since it gets copied from the Inquiry. The
quotation will have a fresh validity period.

41.2 Creation of Sales Order from Quotation

Maintain Copy control from quotation to sales order copying standard QT  OR

L&T Infotech - Confidential Page 348 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

42.0 Appendix
42.1 Calendar – Tcode SCAL

42.1.1 Define Public Holidays

L&T Infotech - Confidential Page 349 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

42.1.2 Define Holiday Calendar

Holiday Calendar can be defined till the year 2098.

L&T Infotech - Confidential Page 350 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 351 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

42.1.3 Factory Calendar

L&T Infotech - Confidential Page 352 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Note: If you select Public Holidays as working, you cannot put holiday calendar.

L&T Infotech - Confidential Page 353 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Select 2011 and .

L&T Infotech - Confidential Page 354 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

42.1.4 Create a Shipping point Calendar & Plant Calendar

L&T Infotech - Confidential Page 355 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Put 99 as the sales organization calendar (all days), 98 as shipping Point calendar (Mon-
Wed) and 97 (Thu-Fri) as the plant calendar.

L&T Infotech - Confidential Page 356 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 357 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

42.2 Use of Calendar in the Sales Order

42.2.1 Effect of Calendar in the route and calendar in the shipping point. –
Transit time calculation.
In the Route, put transit time as 5 days and factory calendar 99 (all working). If the
required delivery date is 26-March-2011, the goods issue calculation date is as follows:

26-March-2011 minus 5 days transit time = 21-March-2011 which is a Monday. However,

our shipping point works only Tuesdays. The next earlier Tuesday becomes the goods
issue date. Which 15-March-2011.

Shipping Point Calendar

L&T Infotech - Confidential Page 358 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

42.2.2 Calendar in Shipping Point but not in Route – Transit Time calculation

With the same example, the transit time is calculated using working days of shipping
point. So, 5 days of transit is taken using the shipping point calendar. 5 working days
here are March (22,15,8,1) and Feb 22. The earlier date of 15 Feb 2011 becomes the
goods issue date.

42.2.3 Loading Date Calculation

The loading date is calculated from the shipping point. If the loading time is 2 days, it
takes it as 2 working days of the shipping point. 15th and 8th are considered as 2 working
days. Loading date is 1st March 2011.

42.2.4 Material Availability Date

Material Availability date is calculated from the shipping point calendar.

42.2.5 Transportation Planning Date

Transportation planning date is calculated from the shipping point calendar.

L&T Infotech - Confidential Page 359 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

42.2.6 Calculation of the required Delivery Date in the Sales Order

The required delivery date is calculated from the sales organization calendar. E.g. if you
put lead time as 2 days, and the calendar working as Wednesday.

If a order is made on 22nd, it is counted as a holiday. The order current date will be
treated as 23rd. Two working days are 23rd and 2nd. The date shown will be 9th.

L&T Infotech - Confidential Page 360 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

42.3 Date Calculation and Calendars in the Sales Order

Date
1. Required Delivery Calculated from the working days in the Sales Organization
Date Calendar.
2. Pricing Date Settings in the Sales document type.

3. Document Date Today’s Date

4. Billing Date Required Delivery Date
5. Service Rendered Not Calculated in the Sales Order
Dates
6. Goods Issue Date First access is the Route Calendar. If route Calendar is not
there, this is taken from the Shipping point Calendar.
7. Loading Date Shipping Point Calendar
8. Material Availability Shipping Point Calendar
9. Transportation Shipping Point Calendar
Planning Date

L&T Infotech - Confidential Page 361 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Day 16: 23-Feb-2011

43.0 Incoming Payment – Tcode F-28

L&T Infotech - Confidential Page 362 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 363 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 364 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 365 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

You get a message ‘correct the marked line items’. Double click and enter the Cost
Center.

L&T Infotech - Confidential Page 366 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The accounting document created directly in FI is seen thru Tcode FB03.

L&T Infotech - Confidential Page 367 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 368 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

44.0 Entering Customer Invoice directly in FI – Tcode FB01

If SD is not implemented, invoices can be directly entered via FI. Obviously, there is no
sales order or delivery information here.

In the first screen, put document date, reference, doc type RV, First line posting key 01
and the customer code.

L&T Infotech - Confidential Page 369 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

You reach the second screen. Put amount for posting key 01.

In the next line item at bottom of the screen, put posting key 50 and G/L account
800000. In the next screen, put the same amount.
Put cost center 1000 and select Profitability Segment.

L&T Infotech - Confidential Page 370 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Don’t enter anything in the next screen. Just Press Continue.

L&T Infotech - Confidential Page 371 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Select Document --> Simulate

L&T Infotech - Confidential Page 372 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The debit entry and credit entry should be the same. The balance should always be zero.
Save the document.

The document can be viewed through Tcode FB03.

L&T Infotech - Confidential Page 373 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Day 17: 24-Feb-2011

45.0 Consignment Processing
Business Scenario: We put our inventory at customer location. The stocks remain ours.
The customer may decide to take it later or return it back to us.

In SAP this is done through a series of business processes

• Consignment Fill Up – Putting the stock at customers location. No Pricing or
Invoicing is carried out here
• Consignment Pick Up – We take the stock back from customers location back to our
plant
• Consignment Issue – The goods are transferred to the customer and Invoicing is
carried out
• Consignment Returns – Reversing the consignment issue

45.1 Consignment Fill up

Standard SD document type KB is used here.

45.1.1 Configuration

L&T Infotech - Confidential Page 374 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Item category KBN is used for consignment fill up.

L&T Infotech - Confidential Page 375 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Item Category Determination

Schedule line category Determination

Schedule line category E1 has movement type 631.

L&T Infotech - Confidential Page 376 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

45.1.2 Transaction

Create a sales order for document type YCFL. The goods issue happens with movement
type 631.

L&T Infotech - Confidential Page 377 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

No accounting document gets generated from the material document.

Let’s look at the stock overview – Tcode MMBE

L&T Infotech - Confidential Page 378 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

45.2 Consignment pick-up

The customer does not want the stocks. The material is taken back by us.

Standard Order type: KA and item category KAN.

L&T Infotech - Confidential Page 379 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Order type has delivery type LR.

L&T Infotech - Confidential Page 380 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The item category KAN has the checkbox Returns active.

The item category KAN determines Schedule line category F1.

L&T Infotech - Confidential Page 381 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The returns delivery has document category T (Returns delivery for order)

L&T Infotech - Confidential Page 382 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Create a sales order and a returns delivery. Note: Instead of a goods issue, you see a
goods receipt button.

L&T Infotech - Confidential Page 383 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The stock position comes back to normal – Tcode MMBE

45.3 Consignment Issue

The customer takes the goods and is invoiced for it.

The sales process here in standard SAP is KE – LF – F2 with item category KEN and
schedule line category C1 (movement 633).

L&T Infotech - Confidential Page 384 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Item Category KEN has special stock indicator W.

Schedule line category determination

L&T Infotech - Confidential Page 385 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Partner determination procedure with partner type SB (special stock partner).

L&T Infotech - Confidential Page 386 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Now the customer consignment stock reduces. The overall stock in the plant reduces by
the quantity. Now the material accounting document gets created.

L&T Infotech - Confidential Page 387 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Note:

The goods issue during fill-up removes from storage location 0001 and put it into
customer consignment stock. This stock is still a part of the company.

The goods issue during issue removes from customer consignment stock and out of the
company.

45.4 Consignment Returns

Reverse Consignment Issue.

Document flow CONR (KRN/D0-Mtype 634) – LR - RE

L&T Infotech - Confidential Page 388 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 389 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

When you do consignment returns with movement type 634, the system brings it back to
customer consignments.

L&T Infotech - Confidential Page 390 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Day 18: 26-Feb-11

46.0 Purchase Process Overview

Procurement of materials or services from a vendor: This process has the following steps
• Creation of Vendor Master
• Creation of a Purchase Order with details that include material, quantity, price,
delivery location
• The Purchase order is given to the Vendor
• The Vendor loads the material in the vehicle which leaves for the customer
location
• An Advance Shipping Notification (ASN) is sent to the customer
• The goods reach our warehouse
• The truck is unloaded at the warehouse. A check whether material and quantity is
correct as per purchase order and undamaged is done. Once this is confirmed a
goods receipt is carried out. In this step, your inventory goes up
• The accounts department raises an Invoice to pay the Vendor. Till the payment is
not done, the vendor figures in the balance sheet as Accounts Payables
• Once the payment is done, the transaction is closed

46.1 Creation of Vendor Master – Tcode XK01

L&T Infotech - Confidential Page 391 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 392 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

46.2 Create a material master with Purchasing View

L&T Infotech - Confidential Page 393 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 394 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

46.3 For a combination of material and vendor, create an

Inforecord – ME11

In the next screen, go to Purchase Org Data 1

L&T Infotech - Confidential Page 395 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 396 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

In the condition screen, the price gets copied.

L&T Infotech - Confidential Page 397 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

46.4 Create a Purchase Order for the Vendor – Tcode ME21N

Put the Purchase Organization, Purchase Group and Company code in the Organization
Data Tab.
In the Item tab, put the material and quantity. The Plant and the Price gets proposed
from the Inforecord. Put in the storage location.

L&T Infotech - Confidential Page 398 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Save.

46.5 Release the Purchase Order

A release strategy can be assigned to a Purchase order. This implies that the Purchase
cannot be processed further till it is released by a higher authority. This controls price
authorization.

L&T Infotech - Confidential Page 399 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

46.6 Create a Goods Receipt – Tcode MIGO

Put the purchase order number and press ENTER.

L&T Infotech - Confidential Page 400 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Check each of the tabs of the item.

L&T Infotech - Confidential Page 401 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 402 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

46.7 In the Good Receipt Transaction MIGO, select item OK

Note: If you try to post the document without selecting item OK checkbox, the system
will not allow it.

A material document gets created when you post Goods Receipt. This has movement type
101.

L&T Infotech - Confidential Page 403 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

46.8 Check the stocks – Tcode MMBE

L&T Infotech - Confidential Page 404 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

46.9 Create a Vendor Invoice – Tcode MIRO

Put the PO number in the PO Reference Tab. The system automatically determines the
Goods Receipt quantity.

Put the Invoice Price manually in the Amount field.

L&T Infotech - Confidential Page 405 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

You see the balance in red .

Select the item and press enter. The balance becomes 0 now.

Save the document. The system creates an accounting document.

L&T Infotech - Confidential Page 406 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Select

L&T Infotech - Confidential Page 407 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

47.0 Purchase order with a Purchase Requisition

47.1 Creation of Purchase Requisition – Tcode ME51N

The actual Purchase order is created by the purchase department. Purchase requisitions
are raised by departments which needs a particular material. These requisitions are then
processed by the Purchase department and subsequent Purchase orders are raised on the
vendors.

Create a purchase requisition. Put in the basic details:

• Material
• Quantity
• Texts

L&T Infotech - Confidential Page 408 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

This purchase requisition has a release strategy assigned to it. This means the PO cannot
be created unless this requisition is released. The release indicator is shown as blocked.

Save. The system creates a purchase requisition .

47.2 Release the Purchase Requisition – Tcode ME54N

L&T Infotech - Confidential Page 409 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The same purchase requisition is seen with additional release options column.

Release codes U1 and U2 using button . After this, the release indictor becomes 2.

Save. Now a PO can be created from the purchase requisition.

L&T Infotech - Confidential Page 410 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

47.3 Converting a Purchase Requisition to a Purchase Order

Select .

L&T Infotech - Confidential Page 411 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Select the item and go to adopt + details.

L&T Infotech - Confidential Page 412 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

48.0 Third Party Sales (Also known as Drop Shipments)

Business Scenario: The customer places an order with the company. This product is not
produced in-house or kept in company warehouses. It is procured from a Vendor. Once
the customer order comes in, the vendor is asked to deliver it directly to the customer.
I.e. the material does not come into the company stocks at all.

SAP Process:
1. Create a Sales Order on the customer.
2. The Sales Order generates a Purchase Requisition. This is controlled by the
schedule line category.
3. The Purchase department processes the purchase requisition and creates a
Purchase Order. This PO is sent to the Vendor.
4. The Vendor sends the material to the customer confirms delivery and sends an
Invoice to the company.
5. No GR is done here. An Invoice receipt is done based on the Purchase Order.
6. The customer is billed based on the sales order. Billing is controlled by the item
Category Billing Relevance Setting.
7. No SD delivery is created.

48.1 Configuration of Item Category TAS

L&T Infotech - Confidential Page 413 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

48.2 Schedule Line Category Determination

48.3 Schedule Line Category CS

In the schedule line category CS, there is no Movement type. Here you can configure the
Purchase requisition type.

L&T Infotech - Confidential Page 414 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

48.4 Copy Control Order – Billing Tcode VTFA

L&T Infotech - Confidential Page 415 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

48.5 Create a Sales Order

Enter the sold to party, Material, Quantity and put Item Category TAS.

L&T Infotech - Confidential Page 416 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Go to the schedule lines of the item.

L&T Infotech - Confidential Page 417 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

You see a fourth tab – Purchase Requisition.

L&T Infotech - Confidential Page 418 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

You see a new field in the Procurement tab – External Procurement number.

L&T Infotech - Confidential Page 419 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Save the order. A purchase requisition number gets generated. This is not seen in the
document flow but can be seen in the procurement tab.

Create a Purchase order with reference to the purchase requisition. Create an Invoice
Receipt directly on the PO without doing a Goods Receipt.

Once the PO is created, it is seen in the order document flow.

Create a billing document with reference to the sales order.

48.6 Invoice quantity less than Order Quantity

The order quantity (and the purchase requisition quantity) is 7. However, only 2 EA has
been delivered and invoiced by the vendor. During Customer billing, only 2 EA is billed.

This is controlled in copy control Sales to Billing at the item level – Field Billing Quantity
F (Invoice Receipt quantity less invoiced quantity).

L&T Infotech - Confidential Page 420 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

48.7 Statistical Goods Receipt (Non Valuated Goods Receipt)

Many times, companies like to record when exactly the customer has received the goods.
This is done using non valuated goods receipt, where stocks are not updated.

Process Flow:
1. Create a Sales Order. Select the checkbox ‘GR’ and ‘GR Non-Val’ in the Purchase
requisition screen of the schedule line.

2. Create a purchase order from the Sales Order Purchase Requisition. The GR & GR
Non-Val checkboxes gets copied from the PR.

L&T Infotech - Confidential Page 421 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

3. Create a non-valuated Goods Receipt. This tracks whether the customer has
received the goods. The storage location field is hidden and the third party
customer is seen.

4. Create a Vendor Invoice Receipt. The invoice receipt quantity is proposed from the
GR document.
5. After the IR happens, the sales order is relevant for billing.

48.8 Sales Order – Billing Copy Control Settings Tcode VTFA

Example: Goods Receipt quantity = 10 and Invoice Receipt quantity = 5.

E Goods receipt quantity less invoiced quantity
If you use Billing Quantity Indicator E, the billing document quantity = 10.

F Invoice receipt quantity less invoiced quantity

If you use Billing Quantity Indicator F, the billing document quantity = 5.

L&T Infotech - Confidential Page 422 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

I - Purchase quantity minus quantity already billed

In the earlier 2 options, the sales order quantity was the base for billing.
Now, if your sales order quantity = 100 and PO quantity has been changed to 200, the
billing will be based on 200 and not 100.

48.9 Monitoring the third party processes of the sales order

Tcode SE38 – SDMFSTRP.

L&T Infotech - Confidential Page 423 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

You can now monitor the sales order, purchase order, vendor IR and customer invoices
quantities.

49.0 Serial Numbers

49.1 Maintain Serial Number Profile – Tcode OIS2

L&T Infotech - Confidential Page 424 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

49.2 Maintain Serial number profile in the material master in view

Sales: General/Plant

49.3 Create a Goods Receipt using movement type 501 – Tcode

MB1c
You get a popup screen in which the system prompts you to put the Serial numbers.

L&T Infotech - Confidential Page 425 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

49.4 Checking material stocks – Tcode MMBE

L&T Infotech - Confidential Page 426 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 427 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

49.5 An equipment master is generated for each combination of

material & Serial Number – Tcode IE03

49.6 Create a sales order and delivery

L&T Infotech - Confidential Page 428 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

In the delivery where the serial number maintenance is obligatory, if you try to do a
goods issue you get the following message.

L&T Infotech - Confidential Page 429 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

49.7 Check the equipment master for serial number 7 of material

M-266

The delivery information is carried over into the equipment master.

L&T Infotech - Confidential Page 430 of 730
 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 431 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

50.0 Product Hierarchy – Tcode OVSV

L&T Infotech - Confidential Page 432 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

50.1 Product Hierarchy structure is seen in structure PRODHS –

Tcode SE11

Standard Product hierarchy has 3 levels: 5-5-8. The product hierarchy field is 18 digits.

50.2 Maintenance of Product Hierarchy – Tcode V/76

L&T Infotech - Confidential Page 433 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

50.3 Maintain Product Hierarchy in the material Master

In the product hierarchy dropdown, the first screen you see is the level one – This is
termed as main group.

L&T Infotech - Confidential Page 434 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Put your cursor on the main group and select Next Level. We enter the level 2 screen.

L&T Infotech - Confidential Page 435 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Again Select the group and go to Next level.

L&T Infotech - Confidential Page 436 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Now choose the final subgroup.

L&T Infotech - Confidential Page 437 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Product hierarchy can also be maintained for a specific distribution chain.

L&T Infotech - Confidential Page 438 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

50.4 Product Hierarchy in the sales order

The product hierarchy is picked up from the Sales Org 2 view of the material master. It is
seen in the Item level in Sales B tab. If no value is maintained in the sales org2 view of
the material master, the product hierarchy does not get picked from the basic data
screen.

L&T Infotech - Confidential Page 439 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Product hierarchies are used in 2 places:

• Reporting
• Pricing

51.0 Finding Customizing Transaction codes using table TSTCP

Find the Customizing table name using F1-F9.

Go to Tcode SE16 – Table TSTCP

When you execute, you get the Transaction code.

L&T Infotech - Confidential Page 440 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Customizing Activity Transaction Code

1. Create Sales Organization OVX5
2. Create Distribution Channel OVXI
3. Create Division OVXB, OMSP
4. Maintain Sales Office OVX1
5. Maintain Sales Group OVX4
6. Create Shipping Point OVXD
7. Assign Sales Organization to company code OVX3N
8. Assign distribution channel to sales organization OVXKN
9. Assign Division to sales organization OVXAN
10. Set up Sales Area OVXGN
11. Assign Sales office to sales area OVXMN
12. Assign sales group to sales office OVXJN
Assign sales organization - distribution channel -
13. OVX6N
plant
14. Assign Shipping point to Plant OVXC
Define Scheduling By Sales Document Type
15. OVLY
(Transportation & Delivery Scheduling)
16. Pick/Pack times for Shipping Point + Route
OVLV
Combination
Loading times for Shipping Point + Route
17. OVLL
Combination

L&T Infotech - Confidential Page 441 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Day 19: 28-Feb-11

52.0 Intercompany Sales Order Processing

Business Scenario:
We have 2 company codes 1000 and 3000. These represent the German and US operations
of the same entity i.e. P&G Germany and P&G USA.

P&G Germany receives an order from its customer in Germany for product M-862.
However, this product is not made in Germany and is available with P&G USA. P&G
Germany asks its USA office to deliver the product to the customer. In return, P&G USA
bills P&G Germany on an internally agreed price.

SAP Process:
1. P&G Germany raises a sales order on its customer in Sales Area 1000-10-00.
(ordering company code)
2. The plant determined in the sales order is P&G USAs plant 3000.
3. The delivery is carried out from P&G USAs Plant 3000 to the customer. The
delivery document is done in sales area 1000-10-00.
4. P&G Germany raises an invoice on its customer in sales area 1000-10-00.
5. P&G USA raises an intercompany invoice on P&G Germany in Sales area 3000-10-00
on a transfer price. P&G Germany is defined as an Intercompany customer in sales
area 3000-10-00.

L&T Infotech - Confidential Page 442 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

52.1 Overview – Prerequisites

• Maintain IC Billing Sales Organization to Delivering plant of delivering organization
• Maintain IC customer for Ordering Sales Organization in the above sales
organization.
• Maintain billing type IV in definition of Sales doc type.
• Maintain IC transfer price in pricing procedure (PI01 condition type). This has
condition category 5(Intercompany).
• Maintain material master for IC Billing Distribution Chain.

52.2 Process Summary

• Ordering Sales Organization - 1000 in company code 1000: The end Customer - 862
(maintained in 1000-10-00), Material - M-862 (maintained in 1000-10) – Also
maintained in 3000-01 else business area determination error comes up)
• Delivering Plant 3000 (maintained in company code 3000): When delivering plant
3000 supplies to sales organization 1000, the sales org has to be first defined as an
Intercompany customer. e.g. XYZ. This IC customer has to be maintained in the
sales area 3000-01-01.This setting is maintained in Tcode OVV9.
• Delivery is created for the sales order. In the LIKP table, we see the IC Billing Sales
area and IC-Customer 3000-01-01 and customer XYZ. If the customer master is not
maintained in the area, all these fields come blank.
• Carry out normal billing of customer 862 delivery in company code 1000.
• Carry out Intercompany billing of customer XYZ in company code 3000. The header
shows sales area 3000-01-01. The item shows sales area 1000-10-00. The partner
shows the SH as 862.
• IC billing type IV is maintained in the definition of Sales doc type in Tcode VOV8.
(field
• intercompany billing type). The price is picked up from condition type PI01.

52.3 Base Settings – Ordering Company code

The ordering company code is the company code of the sales organization which brings in
the customer order. The ordering company code is 1000 and its sales organization is
L&T Infotech - Confidential Page 443 of 730
 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

1000. All its customers are maintained in 1000-10-00 and materials are maintained in
1000-10 distribution chain.

All sales to its customers are made in sales area 1000-10-00.

52.4 Base Settings – Delivering Company Code

Delivering company code is 3000. It has plant 3000 and sales organization 3000.

52.5 Defining the IC Billing Sales Area – Tcode OVV9

L&T Infotech - Confidential Page 444 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The Intercompany customer master has to be maintained in this sales area if delivering
plant is 3000.

52.6 Define an intercompany customer IC-1000 in the delivering

company sales area 3000-10-00 and company code 3000.

52.7 Assign this customer number to Sales Organization 1000 –

Tcode OVVA

L&T Infotech - Confidential Page 445 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Sales organization 1000 is defined as an internal customer IC-1000.

52.8 Assign delivering plant 3000 to Ordering Distribution Chain

1000-10

52.9 Define Intercompany Billing type – Tcode VOFA

The intercompany billing type has SD document category 5 (Intercompany Invoice)

L&T Infotech - Confidential Page 446 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

52.10 In Order type OR, maintain intercompany billing type Tcode

VOV8

52.11 Pricing Procedure Settings

Add condition type PI01 in the pricing procedure. This is the intercompany price (transfer
price).

L&T Infotech - Confidential Page 447 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Condition type PI01 has condition class B and Condition category I.

52.12 Create Condition records for PI01 – Transfer Price

The transfer price is maintained in condition type PI01.

52.13 Maintain Customer Price

L&T Infotech - Confidential Page 448 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 449 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

52.14 Create a customer order in Ordering Company Code

In this order, put delivering plant as 3000.

52.15 Customer Delivery is done from shipping point 3000 and Plant
3000

L&T Infotech - Confidential Page 450 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Post the goods issue.

Note: This delivery is belongs to sales organization 1000 with shipping point 3000.

L&T Infotech - Confidential Page 451 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Note 2: The system recognizes that a intercompany billing has to be done from 3000 to
1000. This is taken from the configuration setting in Tcode OVV9.

The material document gets posted in company code 3000.

52.16 Customer Billing

As far as the customer is concerned, the billing is done in the company code of the
Ordering Sales Organization.

L&T Infotech - Confidential Page 452 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The billing is done in sales area 1000-10-00.

L&T Infotech - Confidential Page 453 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

52.17 Intercompany Billing Document

The Payer is IC-1000 (as maintained for the sales organization). This maintained in sales
area 3000-10-00 (as maintained in OVV9).

The material master has to be maintained in 3000-10 (OVV9).

L&T Infotech - Confidential Page 454 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The intercompany billing document is done in sales area 3000-10-00 (header).

The ordering party sales area is seen in the item level.

The item level partner screen shows the original customer the material was shipped to.

L&T Infotech - Confidential Page 455 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The intercompany pricing is picked up here.

This billing document is posted in company code 3000.

L&T Infotech - Confidential Page 456 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

52.18 Business Area Link

In OVV9, the sales area you maintain is used in Business Area determination in the
Ordering Sales Order.

52.19 Billing Error

This error has occurred because the IC billing sales area and IC customer has not got
determined during billing.

L&T Infotech - Confidential Page 457 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

This error means Sales Organization Internal customer is not maintained in the sales area
defined in OVV9. In our example 3000-01-01.

Note: Before the first sales order is created, the IC customer has to be maintained in the
sales area of the delivering plant as defined in Tcode OVV9.

Day 20: 01-Mar-11

53.0 Definition of a Fiscal Year – Tcode OB29
Some companies operate in the January to December financial cycle with 12 periods.
Each period corresponds to a calendar month. This is typically followed in Europe.
Other companies operate in the April to March financial cycle with 12 periods. Each
period corresponds to a month.
There are companies which has the concept of having 13 periods. Each period may have
say 25 days.

53.1 Calendar Year with Number of Posting Periods = 12

L&T Infotech - Confidential Page 458 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

53.2 April to March with 12 Periods

+1 if the fiscal year is later than the calendar year

-1 if the fiscal year (2011) is before the calendar year (2012).

L&T Infotech - Confidential Page 459 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

53.3 Year Dependent Fiscal Year with 12 periods

L&T Infotech - Confidential Page 460 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Note: Do not try to create Fiscal years on your own!!!!

53.4 One company code can have only one fiscal year – Tcode OB37

L&T Infotech - Confidential Page 461 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

54.0 Closing MM Periods

MM Periods are defined for a fiscal year. The end of a fiscal period may correspond to the
end of the month depending on how you configure it.

In SAP, at the beginning of every period, the earlier period has to be closed and a new
period has to be opened for Inventory Posting to be allowed. If you do not do this, the
system will not allow posting into the new period.

Period 01/2011 ends on 25th Jan 2011 according to the fiscal year calendar definition. On
26th Jan 2011, period 2 starts. The MM Period has to be opened on 26th Jan.

L&T Infotech - Confidential Page 462 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

54.1 Allowing Posting to earlier period & Viewing current Period

At any point of time, maximum 2 periods are available for inventory posting. To see
which periods are available, go to Tcode MMRV.

If you do not allow posting to previous period, the system will allow posting only to the
current period.

L&T Infotech - Confidential Page 463 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Note: The current Period should always correspond to the current month. The current
period is 02-2011 but the current month is 03-2011. This means that 02-2011 has to be
closed and 03-2011 has to be opened.

54.2 Closing Period: Tcode – MMPV

L&T Infotech - Confidential Page 464 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

54.3 Danger – Period Closing

• The system will allow opening of future periods. If that is done, you cannot post in
the current period
• Be very careful with transaction code MMPV
• In Projects, leave this to the P2P consultants

L&T Infotech - Confidential Page 465 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

55.0 Moving Average Price in the Material Master

A constant price at which a material is valuated without taking goods movements and
invoices into account.

A price that changes in consequence of goods movements and the entry of invoices, and
which is used to valuate a material. The moving average price is calculated by dividing
the value of the material by the quantity of material in stock. It is automatically
recalculated by the system after each goods movement or invoice entry.

L&T Infotech - Confidential Page 466 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Create a purchase order for quantity 1 and price 100. Do a goods receipt. The incoming
inventory valuation is updated with 100 EUR. The Moving average price in the material
master is now 100.

Create a second Purchase order for quantity 1 and price 200. Do another goods receipt
for this purchase order. The incoming inventory valuation is updated with 200 EUR. The
moving average price is now (100 x 1 + 200 x 1)/2 = 150.

L&T Infotech - Confidential Page 467 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The goods issue is done at the Moving average price value.

L&T Infotech - Confidential Page 468 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

55.1 Changing the Moving Average Price – Tcode MR21

The MAP cannot be changed manually in the material master.

L&T Infotech - Confidential Page 469 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The system creates a price change document along with accounting documents.

L&T Infotech - Confidential Page 470 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 471 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

56.0 Intercompany Stock Transport Order with SD Delivery

Business Scenario: We have 2 company codes 1000 (Germany) and 3000 (USA). Company
Code 1000 requests Company code 3000 for material XYZ. Company Code 3000 ships the
material to company Code 1000 Plant and bills Company code 1000 on a transfer price
basis.

56.1 MM configuration

56.1.1 Company Code 3000 is a vendor to Company Code 1000

Create a Vendor Master for plant 3000 and assign it to the plant 3000 – Tcode XK01.

L&T Infotech - Confidential Page 472 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 473 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Stock Transport Order Settings

56.1.2 Assign document type NB to supplying plant and receiving plant

Assign Document Type, One-Step Procedure, Underdelivery Tolerance

56.1.3 Assign Delivery type NLCC to purchase document type NB

Assign Delivery Type and Checking Rule

L&T Infotech - Confidential Page 474 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

56.1.4 Define Shipping Data for Plants

Maintain the delivering sales area in the delivering plant.

Maintain the customer number of the receiving plant. Extend the customer to 3000-10-
00.

L&T Infotech - Confidential Page 475 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

56.2 SD Configuration

56.2.1 Assign IC Sales area to supplying Plant

The IC customer in receiving plant has to be maintained for this sales area.

L&T Infotech - Confidential Page 476 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

56.2.2 Delivery type NLCC – Purchase order required

The delivery type NLCC has a default Sales order type DL.

56.2.3 Item Category NLC

Billing relevance D - Proforma

L&T Infotech - Confidential Page 477 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

56.2.4 Schedule line category NC

L&T Infotech - Confidential Page 478 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

56.2.5 Delivery Item Category Determination – Tcode 0184

56.2.6 Schedule line category Determination – Tcode VOV5

56.2.7 Billing type IV must be set up for order type DL

L&T Infotech - Confidential Page 479 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

56.2.8 Copy Control: Delivery to Billing Tcode VTLF

L&T Infotech - Confidential Page 480 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

56.3 Create a Purchase Order

• Create a purchase order with vendor CC-3000 and receiving plant 1000.
• The system reads supplying plant 3000 from the vendor master and checks if the
material has been maintained for that plant
• The system carries shipping point determination - 3000 and Route determination.
• It finds the delivery type NLCC & Customer 1185 (assigned to receiving plant). The
customer has to be maintained in sales area defined in Tcode OVV9
• It also finds the delivery sales area (assigned to supplying plant)
• All the delivery details are seen in the Shipping Tab

L&T Infotech - Confidential Page 481 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

56.4 Process Delivery Due List using Tcode VL10D in company code
3000.

L&T Infotech - Confidential Page 482 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The system creates a delivery with movement type 643.

L&T Infotech - Confidential Page 483 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

56.5 Check stock position in Plant 1000 – Tcode MMBE

The delivery from company code 3000 is seen as stock in transit in Plant 1000.

L&T Infotech - Confidential Page 484 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

56.6 Do a goods receipt in Plant 1000 – Tcode MIGO

L&T Infotech - Confidential Page 485 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

56.7 Check the stock status in plant 1000.

The material is taken into unrestricted stocks. The stock in transit (CC) disappears.

L&T Infotech - Confidential Page 486 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

56.8 Create Intercompany billing document based on the delivery

56.9 Goods Issue at plant 3000 and goods receipt at plant 1000
simultaneously

L&T Infotech - Confidential Page 487 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Day 21: 02-Mar-11

57.0 Stock Transport Processing between Plants of same
company code
Business Scenario: Inventory is transferred across plants using stock transport order.
There is no billing done in the process.

Receiving Plant 1000 and Supplying plant 1100 belong to the same company code.

L&T Infotech - Confidential Page 488 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

57.1 Define Purchase document type UB

L&T Infotech - Confidential Page 489 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

57.2 Define Shipping Data for Plants

L&T Infotech - Confidential Page 490 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

57.3 Assign Delivery Type and Checking Rule

Stock transport order type UB is used for inter plant transfer with a company code.

57.4 Assign Document Type, One-Step Procedure, Underdelivery

Tolerance

57.5 Delivery Item Category Determination – Tcode 0184

L&T Infotech - Confidential Page 491 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

57.6 Schedule line category Determination – VOV5

57.7 Create Purchase Order

At the item – Shipping screen, all details are seen.

57.8 Create delivery using Tcode VL10D

L&T Infotech - Confidential Page 492 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 493 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Post goods issue.

The system does goods issue from plant 1100 and goods receipt into plant 1000 in a single
step using movement type 641.

L&T Infotech - Confidential Page 494 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

57.9 One Step Process – Goods Issue and Goods receipt in a single
jhatka

L&T Infotech - Confidential Page 495 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

58.0 Individual PO Cycle

Business Scenario: The customer asks for a material which is not in your stocks and has
to be procured externally from the Vendor. We ask the Vendor to ship it to our plant.
From our plant, we deliver it to our customer and bill him.

58.1 SAP Process Overview

• Create a sales order with item category TAB (with indicator E)

• This triggers a purchase requisition with indicator E (orders on hand). The
purchase requisition is controlled in the item category.
• Create a PO based on this PR (with special stock indicator E)
• The vendor sends us the goods. (Do a GR with 101E)
• The stocks are stored as sales order stock for the specific sales order number. No
one else can use this stock
• Create a delivery from the sales order and do goods issue of movement type 601

58.2 Standard item category – TAB Configuration

L&T Infotech - Confidential Page 496 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

58.3 Schedule line category CB Configuration

The schedule line category for TAB is CB.

Note: Apart from regular movement type 601, this also has Purchase requisition details.

L&T Infotech - Confidential Page 497 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

58.4 Create sales order with Item Category TAB

Check the Purchase requisition in the sales order.

L&T Infotech - Confidential Page 498 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The system generates a Purchase requisition number on saving the order.

L&T Infotech - Confidential Page 499 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

58.5 Create a Purchase order from the Purchase Requisition –

Tcode ME21

L&T Infotech - Confidential Page 500 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 501 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

58.6 Post Goods Receipt for the PO

The Vendor sends the material to our plant.

Note: GR is done with Movement type 101E. The sales order number can be seen during
GR.

L&T Infotech - Confidential Page 502 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

58.7 View Sales Order Stock – Tcode MMBE

L&T Infotech - Confidential Page 503 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The material is received as sales order stock. This is reserved for this particular
customer’s order and cannot be used for other customers.

L&T Infotech - Confidential Page 504 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

58.8 Create a delivery for the sales order

Post Goods Issue with movement type 601E.

L&T Infotech - Confidential Page 505 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

58.9 Carry out billing for the delivery

59.0 Returns Processing

59.1 Returns Processing with reference to Billing doc / credit memo

Business Scenario: The customer returns the product. After this, you either return his
money through a credit memo or give him a replacement product free of charge.

59.1.1 Create Returns Sales Order with reference to a billing document

L&T Infotech - Confidential Page 506 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Put the Returns Materials Authorization (RMA) Number and the reason for returns.
L&T Infotech - Confidential Page 507 of 730
 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The system determines Item Category REN. The system determines schedule category DN
with movement type 651.

L&T Infotech - Confidential Page 508 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Note: Item Category REN is marked for Returns with Order related billing indicator.

59.1.2 Create a Returns Delivery for the Returns Order & Post GR

L&T Infotech - Confidential Page 509 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The goods receipt has been done with movement type 651.

L&T Infotech - Confidential Page 510 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

An accounting document is not generated at this stage from the GR.

59.1.3 View Returns Stock – Tcode MMBE

On Goods receipt, the stocks are put in Returns stock.

59.1.4 Transfer stocks from returns stocks to Unrestricted Stocks

L&T Infotech - Confidential Page 511 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Tcode MB1B – Movement type 453.

On goods posting, the stocks go into unrestricted stocks. Now the accounting document is
generated.

L&T Infotech - Confidential Page 512 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

59.1.5 Create a Returns Credit Memo – Tcode VF01

The credit memo goes and reverses all initial customer debits.

L&T Infotech - Confidential Page 513 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

59.1.6 Returns Configuration - Maintain Copy Control from Billing document

type F2 to Returns order RE

59.2 Returns Process with reference to a sales order

L&T Infotech - Confidential Page 514 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 515 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Create a returns delivery.

L&T Infotech - Confidential Page 516 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

59.3 Scrapping the material instead of taking it back in goods stocks

After the stocks have come into Returns, an inspection has been carried out and it has
been decided to scrap the whole stocks.

Tcode MB1A – Transfer first to blocked stocks.

L&T Infotech - Confidential Page 517 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

An accounting document gets generated when it goes into blocked stocks.

L&T Infotech - Confidential Page 518 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The earlier entry gets reversed.

L&T Infotech - Confidential Page 519 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

59.4 Creating Returns without Reference

Returns can also be created without reference of a preceding document.

L&T Infotech - Confidential Page 520 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Note: Many times the returned materials cannot be identified with any single product.
E.g. damaged materials all mixed up. In this, the business may take a decision to make a
completely new product code, take in stocks and scrap it. A credit memo will be issued
to the buyer.

59.5 Giving Customer Free of Charge Subsequent delivery instead

of credit memo
Business Scenario:
• The customer returns the material
• We either repair the material or give him new stocks

SAP Process:
1. A returns order and GR is created.
2. The material is repaired and put back in stocks. Tcode MB1B – Movement type 453.
3. A free of charge subsequent delivery is created with reference to the returns
order.
4. A regular delivery of movement type 601 is carried out.
5. No billing is done.

L&T Infotech - Confidential Page 521 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 522 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 523 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Note:
• Document type SDF has SD Document category I (order w/o charge)
• Item Category KLN – Not relevant for Billing
• Schedule Line Category CP with movement type 601

L&T Infotech - Confidential Page 524 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

60.0 Material Type Configuration – Tcode OMS2

L&T Infotech - Confidential Page 525 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 526 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

60.1 User Departments

The views which you select here are seen during creation of material master with this
material type.

L&T Infotech - Confidential Page 527 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

60.2 Price Control

Whatever you put here is proposed in the material master.

L&T Infotech - Confidential Page 528 of 730
 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

If you do not select checkbox Price control is mandatory, the system allows you to
change the price control in the material master.

L&T Infotech - Confidential Page 529 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

60.3 Quantity / Value Updating

L&T Infotech - Confidential Page 530 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 531 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 532 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

60.4 Proposal of Item Category in Material Master

Item category is defaulted in DC Item Category group and not in General Item category
group.

Day 22: 04-Mar-11

61.0 Free Goods Determination

Business Scenario: It is common to provide goods free of charge, or not charge the
customers for some of the goods sold.

There are 2 kinds of Free goods processing in SAP:

• Inclusive Free Goods
• Exclusive Free Goods

Inclusive Free Goods: The customer buys 10 bottles of beer, but pays for only 8 bottles
of beer. i.e. 2 bottles of beer are free. i.e. part of the quantity bought is designated as
free and no billed.

Exclusive Free Goods: The customer pays for the goods sold and receives additional
goods. More is delivered than ordered and no additional billing is done.

L&T Infotech - Confidential Page 533 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

61.1 Define Number Range for Free Goods – WC07

61.2 Free Goods Condition technique

61.2.1 Define Condition table V/N2

Free goods condition tables are stored in KOTN***

L&T Infotech - Confidential Page 534 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

61.2.2 Define Free Goods Condition type & Access Sequence

61.2.3 Define Free Goods Procedure

L&T Infotech - Confidential Page 535 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

61.3 Activating Free Goods Determination – V/N6

61.4 Sales Order Pricing with condition type R100 – Tcode V/08

Condition type R100.

L&T Infotech - Confidential Page 536 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Requirement type 55 – means if the item is free goods, only then value of R100 should be
used in the calculation.

Value of this condition type is controlled by the Routine 28 – This calculates the discount
as 100%.

Determine Pricing in the sales order – Tcode OVKK

L&T Infotech - Confidential Page 537 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

61.5 Inclusive Free Goods Sales Order Processing

61.5.1 Maintain Free Goods Master Records – Tcode VBN1

Minimum Quantity – The minimum quantity customer should be buy in order to be eligible
for free goods.

From X Unit FG / are Free goods Y Unit FG: These 2 fields work together. It says that for
every X units of goods sold, Y are free. E.g. for every 5 PCs sold, 2 are to be given free.
The system does a pro-rata calculation. i.e. for 10 items 2 are free, 20 items 4 are free,
100 items 20 are free and so on.

L&T Infotech - Confidential Page 538 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Free Goods Category:

Free Goods Delivery Control:

The delivery controls tells us whether the free goods are delivered with the main item or
are delivered alone.

61.5.2 Create Sales Order

When you enter a sales order, if the minimum Quantity applicable of rebate has not been
entered, the system gives an information message. This is to tell the customer that he
will be eligible for free goods if he buys more.

L&T Infotech - Confidential Page 539 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

61.5.3 Enter Quantity 10 in the sales order

The system splits the quantity of 10 into 2 a main item and sub item.. The billed quantity
of 8 is put in the main item and the calculated free quantities of 2 is put in the sub-item
to the first item.

L&T Infotech - Confidential Page 540 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The system determines Item Category TAN for the first item and item Category TANN for
the free good item.

Note Item 11 refers to item 10.

The system recognizes free goods based on free goods determination procedure NA0001
for the combination of Sales area, DOPP and CUPP. i.e. Free goods has to be active for
the document.

L&T Infotech - Confidential Page 541 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Environment - - > Analysis

61.5.4 Pricing in Inclusive Free Goods

The first item is billed completely as per the price.

The second item total is zero. i.e. a 100% discount is calculated.

L&T Infotech - Confidential Page 542 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

61.5.5 Billing

L&T Infotech - Confidential Page 543 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

61.6 Item Category Determination for inclusive free goods with

item generation & Exclusive Rebates

Item Category Determination – First item .

Item Category determination for 2nd item

61.7 Inclusive Rebate without Item Generation

L&T Infotech - Confidential Page 544 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

When you enter the quantity in an order, the system does not generate an addition sub
item. It just calculates the discount to be given for the free goods.

L&T Infotech - Confidential Page 545 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 546 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The billing document generates the following accounting entries.

61.8 Exclusive Rebates

During Creation of Free goods condition records select . The initial screen is
always defaulted to Inclusive. This has to be changed to Exclusive.

During Creation of Sales Order, the system generates a sub item with the additional free
goods. The difference between this and inclusive with item generation is
• The quantity does not get split between main and sub item. The main item
quantity remains the order quantity input. Additional quantity gets added in the
sub item
• A separate material is possible at the sub item level.

L&T Infotech - Confidential Page 547 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Free goods Processing:

1. Define a free goods determination procedure NA00001 with free goods condition
type NA00. Activate it for a document type similar to OVKK.
2. In the Pricing Procedure put 2 condition types – R100 and NRAB. This controls
inclusive free goods with item generation (R100) and without item generation
(NRAB). Both the condition types calculate 100% (-) of the document item value
and make the net value of the item zero.
3. Create a free goods condition record for condition type NA00. You mention here
whether it is an inclusive or exclusive free goods. Specify the minimum order
quantity for which free goods is to be given. Also, for inclusive free goods specify
the ratio of free goods to be given. E.g. for every 10 give 1 free good. This ratio
will work in multiples.
4. When inclusive free good is created in the order with item generation, the system
splits the quantity into main item and sub-item. The sub-item category TANN is
determined based on item Category Usage FREE.

L&T Infotech - Confidential Page 548 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

5. When exclusive free goods is created in the order, the system behaves like
inclusive free goods. The key difference is the original order quantity remains in
the main item while a sub-item is generated for extra goods to be given.
6. Delivery of free goods can be controlled in the free goods condition record.
7. Free goods analysis can be carried out in the sales order.

62.0 SD Bill of Material (BOM) Processing

A bill of material (BOM) describes the different components that together create a
product. A BOM for a PC consists of all the parts that make the PC: The CPU, the
monitor, key board and mouse.

PC does not exist as a physical product. It is term given for the entire group of products
which work as one.

62.1 Create a SD BOM – Tcode CS01

L&T Infotech - Confidential Page 549 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Go to .

The BOM status is automatically active. If this is inactive it will not work.

L&T Infotech - Confidential Page 550 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

62.2 Processing of SD BOM in a sales order

There are two ways to process a BOM in SD. Once you enter a BOM in a sales order, the
system runs pricing, Inventory Control and delivery processing at:
• Main item Level if the material is assembled
• Component level if the material is not assembled

62.3 Main Item Level – Sales Order Processing

If you want the system to carry out pricing, inventory control and delivery processing at
main item level, maintain standard item category group ERLA. This ensures item category
TAQ at main item level and sub-item level TAE. Here, the components only function as
text items and are not relevant for delivery.

L&T Infotech - Confidential Page 551 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The Main-item category TAQ determines schedule line category CP with movement type
601.

L&T Infotech - Confidential Page 552 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The sub-item category TAE determines schedule line category CT which has no movement
type in it.

L&T Infotech - Confidential Page 553 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

62.3.1 Pricing

The pricing is carried out at the header level. The system does not take the prices of the
components even if it is maintained.

62.3.2 Delivery

L&T Infotech - Confidential Page 554 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 555 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

62.3.3 Billing

Billing is carried out for the main item.

The sub-items or components is not relevant for billing.

L&T Infotech - Confidential Page 556 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

62.4 Main item – Configuration (TAQ)

The item category TAQ and TAE controls the entire processing at main item level.

62.4.1 Key Controls in Item Category TAQ

The BOM explosion is controlled by the field structure scope A (Explode single-level bill
of material) and Application SD01 (Sales & Distribution)

62.4.2 Pricing control – This works with the requirement routine

L&T Infotech - Confidential Page 557 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

62.4.3 Billing relevance A (delivery related billing)

62.4.4 Schedule line allowed – Only then delivery is allowed

62.4.5 Schedule line category CP is determined with movement type 601

62.5 Sub item – Configuration (TAE)

62.5.1 Item not relevant for billing

62.5.2 No Pricing is carried out – Statistical value X

L&T Infotech - Confidential Page 558 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

62.5.3 No BOM Controls

62.5.4 Delivery Processing

Delivery processing is controlled by the schedule line category. No movement type here
ensures no inventory processing happens.

ensures that sales order components are carried over in the delivery
document as line items for information only.

L&T Infotech - Confidential Page 559 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

62.5.5 Item Category Determination

62.6 Processing at Component level

If you want the system to carry out pricing, inventory control and delivery at the
component level, enter standard item category group LUMF. In this case, only the
components are relevant for delivery. During processing, the system automatically
creates a DELIVERY GROUP. All the items have to be delivered together. If stocks are not
available, the latest delivery date among all the components becomes the delivery date
for the entire delivery group.

L&T Infotech - Confidential Page 560 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Create a sales order. The main item takes item category TAP and sub-item takes item
category TAN.

Pricing is carried out at the item level.

L&T Infotech - Confidential Page 561 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Note: Where is no movement type, the system creates a confirmation of service

document.

L&T Infotech - Confidential Page 562 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Billing

L&T Infotech - Confidential Page 563 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

62.7 Processing at component level – Configuration

Yeh sab item category ka leela hai.

The main level item category is TAP and sub-item is TAN.

TAP Characteristics:
1. BOM Explosion allowed
2. Pricing is not allowed – Statistical value
3. Create Delivery Group
4. TAP determines schedule line category CT which has no movement type

L&T Infotech - Confidential Page 564 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The delivery group is found in the shipping tab in the sales order. The delivery date of all
the items is taken into account during calculation of material availability date.

62.8 Pricing at the header level and inventory and delivery control
at item level

Homework.

L&T Infotech - Confidential Page 565 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

63.0 Cross Selling

Business Scenario: A customer has come to buy a Music System. You want to sell him the
related accessories too. E.g. Speaker Covers, CDs, Head Phones, etc. The system should
automatically propose the items during the sale.

63.1 Condition technique for Cross Selling

L&T Infotech - Confidential Page 566 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The condition tables are stored with name KOTD***

L&T Infotech - Confidential Page 567 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

63.2 Maintain Customer/Document Procedures For Cross Selling

63.2.1 Define customer procedure for cross selling

63.2.2 Define document procedure for cross selling

63.2.3 Assign document procedure for cross selling to sales document types

L&T Infotech - Confidential Page 568 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

63.3 Define And Assign Cross-Selling Profile

The cross selling procedure is not directly assigned or determined. It is first put into a
cross selling profile. This Profile is then determined using Sales area + CS CUPP + CS
DOPP.

63.3.1 Define cross-selling profile

63.3.2 Assign cross-selling profile

63.4 Maintain CUPP for cross selling in the customer master

L&T Infotech - Confidential Page 569 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

63.5 Maintain Cross Selling Condition Records – Tcode VB41

L&T Infotech - Confidential Page 570 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Double Click into the line item and enter other alternate items.

L&T Infotech - Confidential Page 571 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

63.6 Create a Sales Order

During Creation of a sales order, the system proposes the cross selling products. You can
select additional products depending on the customer agreeing to it.

The cross selling items are treated as sub-items to the main products. This helps keep
track of cross selling sales.

L&T Infotech - Confidential Page 572 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

63.7 Item Category determination for Sub-item

63.8 Cross Selling Dialog box appears only on request

During Sales Order entry, the cross selling dialog box has to be specifically selected.

Select at the bottom of the screen.

L&T Infotech - Confidential Page 573 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

63.9 Cross Selling and Dynamic Product Proposal

Cross Selling and Dynamic Product Proposal are determined by the same Profile.

64.0 Dynamic Product Proposal

64.1 Maintain Table of Origin for Product Proposal

L&T Infotech - Confidential Page 574 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

64.2 Define Product Proposal Procedure and Determine Access

Sequences

L&T Infotech - Confidential Page 575 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

64.3 Maintain Procedure Determination (Online) for Product

Proposal

Day 23: 05-Mar-2011 – Saturday

65.0 Tax Determination

Every country has its own Tax structure. For example, India has Sales Tax, Excise Duties,
and Octroi etc.
Each tax is represented by a Tax Condition Type in SAP.
A Tax determination procedure (similar to the pricing procedure with only tax condition
types) is created in FI and assigned to Country.

FI Settings – Tax Determination

65.1 Define Country specific Tax Procedure in FI – Tcode OBQ3

This is similar to SD Pricing procedure. The only difference is application TX.

L&T Infotech - Confidential Page 576 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Note: Our Tax condition types JMOD and JIN2 should not be statistical and should be
assigned to a account key. (MWS and MW3 are FI account keys defined in OBCN).

L&T Infotech - Confidential Page 577 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

65.2 Define FI account keys – Tcode OBCN

65.3 Assign Country of company code to Tax Procedure – Tcode

OBBG
Assign Tax Procedure to Country of company code.

65.4 Tax Condition types in FI are defined in Tcode OBQ1

This screen looks similar to the SD Condition type screen, but it is not the same.

L&T Infotech - Confidential Page 578 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

65.5 Tax Access Sequence in FI – Tcode OBQ2

We have access sequence TAXJ assigned to tax condition type JIN1.

L&T Infotech - Confidential Page 579 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

SD Settings – Tax Determination

65.6 Define Tax Condition type separately in SD Tcode V/06

The SD tax condition type has to have the same name. E.g. JMOD (excise duty) and JIN2
(Local Sales Tax) in FI has also to be defined as JMOD and JIN2 in SD. However, no Access
sequence is defined for this condition type.

L&T Infotech - Confidential Page 580 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

65.7 Define a tax Category e.g. UTXJ in SD which triggers Tax

calculation
Tax Category is a Tax condition type which does not store tax data but helps determines
all SD Taxes. Only this condition type will have an access sequence. UTXJ becomes a tax
category only when you assign it to a county in Tcode OVK1.

L&T Infotech - Confidential Page 581 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

65.7.1 Create a condition type UTXJ

65.7.2 Define access sequence for condition type UTXJ

L&T Infotech - Confidential Page 582 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 583 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

65.8 Define Tax Determination Rules – Tcode OVK1

Assign the special tax condition type to the Country.

65.9 Define Tax Relevancy of Master Records

Taxes are dependent on the customer master and in some cases, the material master. We
maintain customer tax classification in the customer master and material tax
classification in the material master.

65.9.1 Define Customer Tax Classification – Tcode OVK3

65.9.2 Define Material Tax Classification – Tcode OVK4

L&T Infotech - Confidential Page 584 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

65.10 SD Pricing Procedure Configuration – V/08

Put the Tax Category UTXJ and the Tax condition types JMOD and JIN2. Both are
percentage condition types and refer to PR00 condition type.

Notes:
• Account keys for taxes are not maintained in SD Pricing procedure. It gets picked
from the tax code
• Tax Condition types have to be marked as manual, else they come twice in the
sales order pricing. Note that Tax conditions are determined automatically even
though they are marked as manual.

Tax Master Data Maintenance & Sales Order Creation

All tax percentages are maintained in a Tax Code. Tax codes contain tax rates of one or
more tax condition types as well as tax account determination.
Example: Tax Code V1 is an output Tax i.e. sales related tax and has Excise duty 12% and
sales tax 15%. This tax code is to be used specifically for Material X and Customer Y.
These tax codes are determined in the sales order and the tax rates maintained here are
used for Tax calculations in the sales order.

Note: Output Taxes are Sales Related Taxes and are applicable to customers. Input taxes
are purchase related taxes and applicable to Vendors.

L&T Infotech - Confidential Page 585 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

65.11 Tax Jurisdiction Codes

65.11.1 Define Tax Jurisdiction Structure

Tax Jurisdiction Code is a field in the customer master to help determine taxes. For
every Tax Procedure, first a tax jurisdiction structure is defined in Tcode OBCO.

65.11.2 Define Tax Jurisdiction

65.12 Tax Master Data is maintained in FI tax codes – Tcode FTXP

L&T Infotech - Confidential Page 586 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

In the next screen, select Level to see the tax condition types.

L&T Infotech - Confidential Page 587 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 588 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Now put the tax Rates for Excise duty and Local Sales Tax Condition types.

L&T Infotech - Confidential Page 589 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Note: Only these 2 lines should be active. A blue color denotes active lines. Others
should remain inactive otherwise you’ll get an error in pricing (if those condition types
are not maintained in SD pricing).

When you go back to the Jurisdictions view, you see the jurisdiction code copied into the
2 condition types.

L&T Infotech - Confidential Page 590 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Next Select,

L&T Infotech - Confidential Page 591 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Assign the accounting keys of JMOD and JIN2 to G/L Accounts.

L&T Infotech - Confidential Page 592 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

65.13 Maintain SD Condition Records for UTXJ to find the Tax Code –
Tcode VK11

65.14 Maintain Customer Tax Classification 3 in the customer Master

L&T Infotech - Confidential Page 593 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 594 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

65.15 Maintain Material Tax Classification in the Material Master

L&T Infotech - Confidential Page 595 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

65.16 Maintain Tax Jurisdiction Code in the Ship-to Party

L&T Infotech - Confidential Page 596 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

65.17 Create a Sales Order & checking Tax Calculations

L&T Infotech - Confidential Page 597 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Note: The Tax is seen in the Net Value at the item level.

Tax is not seen in the Header.

L&T Infotech - Confidential Page 598 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

65.18 Create the Billing document & checking Tax Accounts

In the Sales Order, Tax Determination in the following way:

• The system reads condition type UTXJ and finds the tax code based on customer
classification and material classification
• It goes to the Tax code and for a combination of Country of the Ship to Party and
Tax Jurisdiction code of the ship to party, it reads the percentages and calculates
in the order
• During Accounting, the system reads the Tax Code G/L accounts assigned to the FI
account keys of JMOD and JIN2

L&T Infotech - Confidential Page 599 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

66.0 Pricing Settings

66.1 Condition type Control in Tcode OVKK

You have an option of maintaining condition type during pricing procedure

determination. The condition type you put here is seen in the line item level (scroll to
the right). You can enter the value here directly instead of going to the pricing screen.
Only one condition type per pricing procedure is allowed with this functionality.

L&T Infotech - Confidential Page 600 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

66.2 Structures KOMK and KOMP

Tables store values after saving a document. Structures don’t store values. They are
populated and discarded continuously at runtime. I.e. they are populated with values
programmatically and used for calculations and then refreshed immediately.

In SD, all pricing is carried out with the help of structures. The header structure is KOMK
and the item level structure is KOMP. The sales order tables are VBAK and VBAP. For
example, plant is stored in table VBAP-WERKs. If plant is used for pricing, the value of
VBAP-WERKS is transferred to KOMP-WERKS and pricing is carried out.

There is no concept of key fields and data fields in a structure. There is no hierarchy of
fields. Every field is unique and used when required.

L&T Infotech - Confidential Page 601 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

66.3 Additional settings in Access Sequence

66.3.1 Manipulating Pricing Fields via KOMK and KOMP

In the access sequence, the system tells it that condition table field VKORG is to be
populated from pricing structure KOMK-VKORG.

We replaced KOMK-VKORG with KOMP-WERKS by selecting the item and choosing

at bottom of the screen.

We are now telling the system, the field VKORG is to be populated by the Plant at the
item level. During Pricing, the system now populates VKORG with KOMP-WERKS at
runtime.

L&T Infotech - Confidential Page 602 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Note: This example is illogical and not to be used anywhere!!!!!

66.3.2 Constants in the Access Sequence

We put a constant value 3000 in VKORG. Note that KOMK-VKORG has automatically
disappeared the moment the constant is put. During sales order creation, the system now
will always look for a condition record with sales organization value 3000, irrespective of
whether the order is created in sales organizations 1000,2000,3000, 4000 etc. i.e. the
sales organization value is hardcoded for pricing.

L&T Infotech - Confidential Page 603 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 604 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

67.0 Customer Hierarchy

67.1 Business Scenario

A company sells a product in North, East, West and South. All customers in North are to
be given a special discount of 5%. You don’t want to go and maintain individual discounts
for every customer.

Customer hierarchy is used in pricing and reporting,

Customer hierarchy consists of nodes. Each node can be connected to a higher level
node.
Each node has one or more customers under it.
Pricing simplification - If discounts are maintained at a node level, the discount is
automatically passed on to all the customers in the node.
Examples:
Scenario 1 - DG&D has lots of sold-to parties but one single payer. We can define Payer as
a node and put all the sold to parties under it. The price maintained for the payer gets
distributed to all the customers under it.

Scenario 2 - DG&D has lots of sold-to parties who also act as payer for some of its
products. But at the global level all pricing is to be kept constant. Here you can define a
node as DG&D Central and maintain all sold-to parties under it.

L&T Infotech - Confidential Page 605 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

67.2 Define Customer Hierarchy Partner Functions

67.3 Define Hierarchy Types

67.4 Set Partner Determination for Hierarchy Categories

Create a Partner determination procedure with partner functions 1A to 1D (apart from

the regular partners like SP, SH, BP and PY)

L&T Infotech - Confidential Page 606 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The origin of the partner function 1A to 1D is B (Customer Hierarchy)

67.5 Assign Account Groups to higher level account groups

L&T Infotech - Confidential Page 607 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

67.6 Assign Sales Areas

67.7 Assign Hierarchy Type for Pricing by Sales Document Type

L&T Infotech - Confidential Page 608 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

67.8 Pricing Procedure – Condition types HI01/HI02

L&T Infotech - Confidential Page 609 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

67.9 Create a hierarchy node – Tcode V-12

This creates a customer with account group 0012.

Maintain Relevant for Pricing Indicator in the billing screen.

L&T Infotech - Confidential Page 610 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

67.10 Create Customer Hierarchy – Tcode VDH1N

L&T Infotech - Confidential Page 611 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 612 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Select Create Assignment .

In the higher level customer, put the node – 669. In the lower level customer put C-801
and 1000.

L&T Infotech - Confidential Page 613 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

To select a customer select icon . The whole line gets highlighted.

The relevance for pricing can be seen by scrolling to the right.

L&T Infotech - Confidential Page 614 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

67.11 Maintain Condition records for HI01 condition type. Tcode

VK11

Maintain a discount for the Hierarchy node.

67.12 The customer hierarchy is seen in the Partner Screen of the

Sales Order Header

L&T Infotech - Confidential Page 615 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 616 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

68.0 Billing Calendar – Tcode OVR4

Business Scenario: So far we have seen billing dates getting determined from the goods
issue date (services rendered date). In many businesses, deliveries are done throughout a
month or a time period and invoicing is carried out on specific dates. E.g. April Deliveries
are billed on 31st April.

68.1 Define Billing Schedule

L&T Infotech - Confidential Page 617 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Select .

L&T Infotech - Confidential Page 618 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 619 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 620 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

68.1 Assign Billing Schedule to the Payer

68.2 Impact of Invoicing Calendar on billing

When you create an invoice with a billing schedule, the system looks at the delivery
dates; checks when the next billing date is due based on the billing schedule and create
a billing document with that billing date.

L&T Infotech - Confidential Page 621 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

69.0 Credit Management

Credit Management is done in ECC or in FSCM (Financial supply Chain Management which
is another product of SAP). If FSCM credit management is active, you cannot do the ECC
Credit Management.

Business Scenarios:
• New Customers are not allowed Credit. i.e. they have to pay on cash only
• Customers are only allowed a fixed credit limit on every order
• If the customer has not paid his earlier dues to the company, no new goods are to
be given to him
• If the customers receivables are over a certain number of days, no new goods are
to be given to him

69.1 Organization Structure – Define Credit Control Area (Tcode

OB45)
A credit control area represents the organizational unit responsible for monitoring
customer credit. This is a freely definable organization. For Example
• The finance manager of West India is responsible for monitoring credit of
customers in Maharashtra, Gujarat, and Rajasthan while Finance Manager of North
India is responsible for Delhi, Chandigarh and Pathankot. – In this case we have 2
credit control areas with its own credit policies
• The UK office monitors the credit limits and control of entire Great Britain. In this
case, the credit control area will be one – Great Britain

L&T Infotech - Confidential Page 622 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

69.2 Permitted Credit Control Areas per company code – Tcode

OBZK

L&T Infotech - Confidential Page 623 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

69.3 Assign Credit Control Area to Company Code – Tcode OB38

A credit control area can be assigned to multiple company codes

69.4 Assign Credit Control Area to the Sales Area

69.5 Credit Settings in the Pricing Procedure

Sub-total A is used to determine the price against which credit check happens. This may
be put against the Price, Price less discounts, Prices less discounts less Taxes or whatever
policies the company may have.

L&T Infotech - Confidential Page 624 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

69.6 Activate Credit Check for Item Category

69.7 Configuring Simple Credit Check for document type

Activate simple credit check for the sales document type.

L&T Infotech - Confidential Page 625 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

69.8 Maintain Credit Limit for Customer – Tcode FD32

L&T Infotech - Confidential Page 626 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

A customer can belong to multiple credit control areas. Each credit control area gives
maximum credit limit of 5000 EUR. If this customer belongs to 4 different credit control
areas, his credit limit would go to 5000x4 = 20,000 EUR. However, the company policy no
customer should get over 5000 EUR credit irrespective of how many credit control areas a
customer belongs to.

The total amount field controls the total credit limit which a customer is allowed across
credit control areas. The Individual Limit tells the maximum credit allowed for any single
credit control area. These are global level settings for the customers.

If a maximum credit limit for a customer for a credit control area has been designated as
4000 EUR and if you try to give him a credit limit of 4500 EUR you get the following error.

L&T Infotech - Confidential Page 627 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Specify the credit limit for the credit control area.

L&T Infotech - Confidential Page 628 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

In the screen, put the risk Category.

69.9 Sales Order with Simple Credit Check

When you create a sales order and put order value over 3000 EUR, the system gives you
an error. The options for simple credit check are:

L&T Infotech - Confidential Page 629 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

69.9.1 Simple Credit Check and Error Message

In this case, the system does not allow saving the order. Once you reduce the value to
the credit limit allowed, then you can carry on the transaction.

L&T Infotech - Confidential Page 630 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

69.9.2 Simple credit check with delivery block

The system automatically puts a delivery block on saving the order.

When you remove the delivery block, the system allows delivery.

69.10 Updates credit exposure on saving a sales order

If you create a sales order of 4000 INR and save it, the system updates the credit
exposure. This can be seen in FD32.

L&T Infotech - Confidential Page 631 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

This is stored in Sales Information System table S066.

L&T Infotech - Confidential Page 632 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

69.11 Define Credit Group for Sales Order

First, define a credit group.

69.12 Activating Automatic Credit Control – Tcode OVAK

Assign Sales document to the credit group.

69.13 Define Automatic Credit Check – OVA8

Automatic Credit control is defined for a combination of credit control area (determined
in the sales order), Risk Category group (defined for the credit customer) and Credit
group (defined for the sales document type)

L&T Infotech - Confidential Page 633 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

69.14 Static Credit Check

Within Automatic Credit Control, you either have the static or dynamic Credit limit
check.

Reaction (both for static and dynamic credit check)

Status – Sets Credit block

Credit control with static check includes open orders and open deliveries.

The moment you put the customer in the sales order, you get a message if the credit
limit has been exceeded.

L&T Infotech - Confidential Page 634 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

When you use Reaction C, you get the following message:

L&T Infotech - Confidential Page 635 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

If you try to create a delivery, the system gives an error.

L&T Infotech - Confidential Page 636 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

69.15 Releasing Credit Check – Tcode VKM1 and VKM3

Tcode VKM1

Tcode VKM3

L&T Infotech - Confidential Page 637 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Select .

Now Save.

69.16 Viewing Changes in the sales order

L&T Infotech - Confidential Page 638 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 639 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Note: The credit exposure gets updated only after the credit block has been released.

Day 24: 08-Mar-11

70.0 Billing document number = Accounting document number

Tcode FBN1 – Maintain accounting document number range and mark it external.

L&T Infotech - Confidential Page 640 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Assign Number range to accounting document type RV – Tcode OBA7.

In Tcode SNRO – RV_BELEG – Maintain the same number range but internal and assign it to
the billing type.

L&T Infotech - Confidential Page 641 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

71.0 Customer Master – Changing account groups: Tcode XD07

L&T Infotech - Confidential Page 642 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 643 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The fields available in account group 0003 are suppressed in new proposed account group
0001. If you want to continue, go and un-supress these fields in account group 0001.

L&T Infotech - Confidential Page 644 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Continue.

L&T Infotech - Confidential Page 645 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

72.0 Shipping conditions in Customer vs. Sales Document type

For Cash Sales and Rush Orders, which are essentially counter sales, customers
preferences are not taken into account. In this scenario, we put shipping condition in
the sales document type. This overrides the setting in the sold-to party.

73.0 Rush Orders

In rush order, create a sales order. The sales order automatically generates a delivery
document. This delivery is processed, goods issue posted and normal credit sales
invoicing in done.

L&T Infotech - Confidential Page 646 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Difference with Cash Sales: Create a sales order. The sales order automatically generates
a delivery document. The delivery is processed, goods issue is carried out and cash
account determination takes place.

74.0 Free of Charge Delivery

Business Scenario: You want to give samples to customers free of charge.
Create sales order FD and carry out delivery. No Invoicing is done.

L&T Infotech - Confidential Page 647 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Create a free of charge sales order and put the Order Reason. The system determines
item category KLN and schedule line category CP.

L&T Infotech - Confidential Page 648 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The system does not allow billing.

L&T Infotech - Confidential Page 649 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

75.0 Scheduling Agreements

Business Scenario: You have an agreement with your customer to deliver him
fixed quantities on specific dates.

L&T Infotech - Confidential Page 650 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 651 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 652 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

75.1 Create Scheduling Agreement – Tcode VA31

In the schedule agreement, you have validity period and target quantity.

L&T Infotech - Confidential Page 653 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Note: The pricing gets activated after you put the schedule lines. This is because the
order quantity is maintained in the schedule line screen and not the overview screen
(which has target quantity).

75.2 Create delivery for scheduling agreement

On the delivery date, only the schedule line quantity is delivered.

After delivery, the quantity gets updated in the schedule line category.

L&T Infotech - Confidential Page 654 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

76.0 Pricing - Condition Supplements

Business Scenario: Condition supplements are given when discounts are to be triggered
automatically for a specific condition type. Example, Every time we give a special price
PR00, we need to give special discounts K004, K005 and K007.

76.1 Create a pricing procedure for condition supplement

76.2 Put the supplement pricing procedure in the condition type

PR00

L&T Infotech - Confidential Page 655 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

76.3 Assign all supplement condition types to regular pricing

procedure

L&T Infotech - Confidential Page 656 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

76.4 Create condition record for Condition type PR00

L&T Infotech - Confidential Page 657 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

76.5 Create Sales Order

During creation of the sales order, the system automatically picks up all the prices in the
PR00 condition supplement.

L&T Infotech - Confidential Page 658 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The system does not look at the individual access sequences of the condition types in the
condition supplement procedure.

77.0 Outline Agreements message during VA01

If you have open scheduling agreements and yet try to create sales order for a
customer, the system gives a pop-up message.

L&T Infotech - Confidential Page 659 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

This is configured in the sales document type.

L&T Infotech - Confidential Page 660 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

78.0 Introduction to RICEF

RICEF is an acronym for Reports, Interfaces, Conversions, Enhancements and
Forms. It represents all the technical developments in a project and is also
sometimes referred to as FRICE.

78.1 Reports
There are different types of Reports
• ABAP Reports are used for operational reporting
• BI (Business Intelligence) Reports are used for analytical or strategic
• ABAP/4 Queries
• Report Painter
• Logistics Information System

ABAP/4 Reports have a selection screen

Selection Screen consists of

L&T Infotech - Confidential Page 661 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Parameter i.e. single value entry

Select options i.e. multiple value entry

We can also have

 Checkboxes
 Radio buttons

The report is seen as Classical report layout or ALV (ABAP List Viewer)

ABAP List Viewer

L&T Infotech - Confidential Page 662 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

All technical developments are initiated by functional consultants using a document

called functional specifications. Based on the functional specification document, the
technical consultants create technical specifications.

The functional specification for a report consists of:

• Visualizing the selection screen of the report
• Report Body – What the report is going to contain
• Which tables and fields are going to be used in the report

Things to remember while preparing functional specifications/developing:

• Understand the client requirements thoroughly – put yourself in the end users
shoes
• Remember that rework of any ABAP development is time consuming – Get it right
the first time
• Try to put the report in a visual format
• Explain the SAP transaction behind the report. E.g. creation of sales order with
sample data
• Always put mandatory fields. This will help system performance
• Selection screen should always have the key field of the table

L&T Infotech - Confidential Page 663 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

• Validation of input fields. E.g. blocked customers are not to be shown in the
report
• Does the report require authority checks?

78.2 Interfaces

Interfaces are built when business transactions run across systems. E.g. I2
Transportation Planning data gets sent to SAP as shipments.

SAP is interfaced with other systems using XI/PI (Process Integrator). PI is a SAP
product. Interfaces can also be done using middleware like TIBCO, BIZTALK etc.

Key Problems with Interfaces:

Example: Data transfer has suddenly stopped from legacy system to SAP. The whole
world is blaming you. You find that the upstream systems feeding data has had a
software patch applied or changed customizing there and this has resulted in changed
settings.

An impact analysis of any changes on upstream/downstream systems is essential. A

continuous channel of communication is important between the managers of multiple
systems in a landscape.

Things to consider when designing Interfaces:

• Field mapping across systems should be foolproof. Example, customer master in
legacy system might have a different structure /code in SAP
• Error Handling techniques have to be built in. If data transfer fails, you have to
build a logic to capture and analyze the whys
• Data Volumes

78.3 Conversions
Data Conversion programs are built to upload e.g. excels data into SAP. Data
Conversion programs are typically BDCs (Batch Data Communication) and BAPIs
(Business Application Programming Interface).

L&T Infotech - Confidential Page 664 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Conversions are also done via LSMW (legacy system migration workbench) which does
not require programming and are done by functional consultants.

Things to consider while designing Conversion programs:

• Field Validations: e.g. your excel sheet may have an invalid sales area. If this is
not checked in customizing, you get an error during posting

78.4 Enhancements
Enhancements form the bulk of all developments in most Projects. Whenever a business
requirement comes in, a fit-gap analysis is carried out. I.e. the requirement is first
checked whether it can be mapped to standard SAP. The functionalities which cannot be
mapped completely are identified as system gaps. These gaps are either closed through
Enhancements or the client is told it is not possible in SAP.

Knowing enhancements to the SAP system is a key success factor of all consultants.
E.g. in Standard SAP, required delivery date is determined from the sales organization
Calendar. The business requirement is that this date has to be determined from
customer specific calendar.

Enhancements are of broadly 3 types:

• Changing elements of standard functionality. E.g. item category getting
determined programmatically
• Creating completely new business functionalities – Sales form tracking
• System validations and checks – e.g. only the person creating a sales order is
allowed to change it

Enhancements are achieved using

• User Exits: Points within SAP standard code where you can write your own logic.
These are pre-defined points
• BADIs – Business Add-ins. Similar to user exits and are replacing user exits
• Changing standard SAP Code – Changing SAP code requires access key

L&T Infotech - Confidential Page 665 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Note: The moment you touch SAP standard code, SAP ceases to take any
responsibility for the system. These changes get lost during a system upgrade from
one version to another.

Changing standard SAP code is to be avoided!!

78.5 Forms
Forms are the print outputs e.g. Delivery challans, Invoices. This are handled in
SAP using
• SAP Scripts
• Smartforms

This process consists of creation of Layouts which is how the physical output looks as well
as the logic of filling in data in the layout. It consists of a layout as well as processing
logic.

Things to remember while working with forms:

• If forms don’t work, then business can come to a standstill
• Normally Billing printouts are taken en masse while delivery printouts are taken
individually for every delivery
• Be very careful with mass printing. Typical problems that occur are: Invoice 1, 2,
3…15 gets printed properly. On the 16th invoice, suddenly the printer skips half
page and printing starts from middle of the document
• Testing is vital
• Understand any form’s legal requirements carefully. These are essentially texts
items which can be easily overlooked

L&T Infotech - Confidential Page 666 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

• Rounding errors can occur. Always test forms with different combinations of
pricing, decimal places, small quantities/large quantities. Do not assume that the
final value will come automatically
• Do not assume that SAP transaction data will get automatically transferred to
forms

L&T Infotech - Confidential Page 667 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Day 25: 09-Mar-11

79.0 Output Determination

79.1 Assign Output Determination to Billing type: v/25

79.2 Maintain output determination procedure

L&T Infotech - Confidential Page 668 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

79.3 Create Smart Forms – Tcode SMARTFORMS

79.4 Maintain output types Tcode V/40

L&T Infotech - Confidential Page 669 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 670 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

79.5 Maintain output condition records – Tcode VV31

80.0 System Landscape

System landscape refers to the number of servers in scope of the project. Normally in a
ECC implementation, there are separate servers for development, quality and
Production.
• The production server is where the actual business runs
• All configuration and technical developments are done in the development server
• All configuration / developments are transferred to the quality server through a
request transport management process. All testing done in the quality server and
no Independent configuration/development is allowed in the quality server

A typical production landscape could be:

• ECC 6.0 – Client 500
• BI 7.0 – Client 100
• CRM 7.0 – Client 300

L&T Infotech - Confidential Page 671 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Development / Quality Landscape

• Separate Development / Quality servers
• Development/Quality in one server with different clients. (Danger: Client
independent changes happen automatically in the Quality server)
• Development/Quality in one server with different instances. Each instance has SAP
loaded separately.

Two system & three system landscape

• A two-system landscape refers to Development/Quality in one server and
Production in separate server
• A three-system landscape refers to separate servers for development / Quality /
Production.

81.0 Client

When SAP is installed, first client 000 is created. This client is then copied into the client
where we work. Every client is an independent SAP system with its own configuration
data, master data and transaction data. Client independent tables are same across all
clients in a single system.

L&T Infotech - Confidential Page 672 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

82.0 Implementation Projects

82.1 ASAP Methodology

SAP Projects follow a 5 phase implementation methodology. This is also known as
ASAP methodology (Accelerated SAP).
• Phase 1 – Project Preparation
• Phase 2 – Blueprint
• Phase 3 – Realization
• Phase 4 – Final Preparation
• Phase 5 – Go Live & Support

82.2 Phase Wise Project Activities

Phase Activities Deliverables
Project Preparation • Define the system • Project Management Plan
Landscape • Level 0 training
• Project Management Plan
Preparation
• Level 0 Training
Business Blueprint • Development System Setup • Business Blueprint Document
• Business Process Mapping • Gap Analysis Document
• Testing/Training/Data
Migration Strategy document
Realization • QA system Setup • Configuration Document
• Configuration • Functional Specifications
• RICEF Developments • Technical Specifications
• System Authorizations • Authorization Matrix
• Testing • Test Scripts
• Configured SAP System
Final Preparation • Production System Setup • Configured and tested
• Data Migration (Cutover) production system with
• End User Training master data

L&T Infotech - Confidential Page 673 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

• End User Documentation • End User Training document

Go Live and Support • System Administration • Issue Logs
• Application Support
• Data Archiving

Notes:
• A deliverable is pre-agreed work package mentioned in the contract
• End of each phase is marked by sign-off of the phase deliverable by the client
• It is critical that each phase has a proper sign-off before moving on to the next
phase
• Every project is bound by a written statement of work and contract. Never
attempt to go beyond that without involving the Project Management
• Correct and relevant documentation of a project is one of the key success factors
• Any changes in requirement has to go through Change Request Process
• Hypercare is a term given to the support phase of an implementation project. In
this phase all product bugs are resolved
• Across all project phases, Project administration, Issue Monitoring, Tracking and
Project Metrics report is done by the Project manager

82.3 Forrester Analysis of SAP Onsite-offshore Model

Phase Percentage of project Offshore Component

Project Preparation 3% 0%
Business Blueprint 20% 0%
Realization 40% 70%
Final Preparation 15% 50%
Go-live 10% 50%
Hypercare 12% 70%

• How to create a business Blueprint/Functional specifications

• Test Strategies & Preparing a test Script
• Data Migration and Cutover Activities
L&T Infotech - Confidential Page 674 of 730
 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

• Risk Mitigation

82.4 Report Variant

The selection screen of a report can be controlled in terms of which fields to hide, which
to protect etc. using a report variant.

Choose Save.

L&T Infotech - Confidential Page 675 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Options:
Protect Field: The field gets disabled.

Hide Field: The field disappears. In the example below field order date disappears.

Hide Field with BIS: The select option disappear and becomes Parameters with multiple
selects.

L&T Infotech - Confidential Page 676 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Required Field: The field becomes mandatory.

82.5 Assigning Reports to Transaction codes – Tcode SE93

Reports are written in ABAP which are executed via Tcode SE38 or SA38. We can assign
this to a Z-Transaction code so that the user does not have to remember the report
name.

L&T Infotech - Confidential Page 677 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 678 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Note: You can assign a report variant to the transaction code.

L&T Infotech - Confidential Page 679 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

83.0 Authorization Matrix

In any new implementation, authorization problems can bring a project standstill on go-
live. This is one of the most neglected areas of a project.

Process of creating an Authorization Matrix:

1. Make a listing of all Transaction codes that will be used in the Project. This
includes creation, change, display, cancel, delete.
2. Make a listing of all reports that will be required in the project.
3. With the help of the customer, make a list of business roles. E.g Business Role –
Warehouse operations, ordering Department. The existing system users should be
mapped to the business roles.
4. For each business role, assign the list of transaction codes and reports.
5. Once this is finalized, the business roles and list of transactions should be given to
the Basis team. The basis team creates an authorization profile.
6. The authorization profile is then assigned to individual user IDs.
7. Authorization check is run in the system using Tcode SU53

Example: Users are to be allowed only VF01 and no other transaction in SAP.

84.0 Create a Role – Tcode PFCG

L&T Infotech - Confidential Page 680 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Select

84.1 Assign required transaction code to Role

Select

L&T Infotech - Confidential Page 681 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

84.2 Assign Authorization to Authorization Activities

Next, Go to Authorizations Tab.

Select

L&T Infotech - Confidential Page 682 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

If you select full authorization, everything is (*)

L&T Infotech - Confidential Page 683 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Activity

L&T Infotech - Confidential Page 684 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

The authorization profile should be green else it will not be generated.

When you save, a new profile name gets generated.

L&T Infotech - Confidential Page 685 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

84.3 Generate the authorization Role

Generate by selecting .
The status changes to generated.

Now go the User Tab.

84.4 Assign User and select User Comparison.

L&T Infotech - Confidential Page 686 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

84.5 Adding a role manually.

L&T Infotech - Confidential Page 687 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Select

L&T Infotech - Confidential Page 688 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Select

When you see the user using Tcode SU01D.

L&T Infotech - Confidential Page 689 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

84.6 Checking Authorization Object in SAP – Tcode SU53

L&T Infotech - Confidential Page 690 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 691 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

85.0 Use of Currencies in Sales Documents

85.1 Maintain document Currency in Customer Master
Maintain Sold to party currency as USD. Note that the currency of the company code is
EUR.

85.2 Document currency in the sales order

The currency maintained in the customer master is used as the document currency in the
sales order.

L&T Infotech - Confidential Page 692 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 693 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Check the accounting document.

Select Display currency.

L&T Infotech - Confidential Page 694 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

85.3 Maintaining exchange rates manually in the sales Order

Local currency = EUR

1 USD = 2 EUR

L&T Infotech - Confidential Page 695 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

85.4 Copy Control Settings – Delivery to Billing Tcode VTFL

Maintain Pricing Exchange Rate type in Billing as A.

L&T Infotech - Confidential Page 696 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

85.5 Exchange rate in Billing

At the item level the sales order exchange rate is copied.

At the header level, the system shows exchange rate type of the sold to party.

L&T Infotech - Confidential Page 697 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

85.6 Maintenance of Currency Exchange Rates – Tcode F-62

Day 26: 10-Mar-11

86.0 Project
86.1 Business Overview
Sigma International is a leading market player in the power generation industry. Its
products include Diesel and Gas generators. Its revenues were $ 250 Million in the year
2010 with a headcount of 200 employees. Its corporate headquarters is based in Pune
with regional offices in Kolkata, Delhi, Chennai and Hyderabad.

Key Business Processes include:

• Sigma’s business model includes procurement of generators from Original
Equipment Manufacturers. Its key supplier is Gamma Genco
• Gamma Genco sends its products to Sigma’s warehouses in Pune and Chennai. It
may also send products directly to the end Customers
• Sigma’s customers include the Industrial sector
• Sigma does not do Servicing of its products. This is outsourced to a third party
service provider who deals directly with the customer

SAP Business Processes are:

• Procurement of Generators from Gamma Genco
• Sales to Domestic Customers from Warehouse
• Sales to Domestic Customers directly through the vendor
• Export Sales from Chennai Warehouse
• Complaints & Returns Processes

Key Business Drivers

Currently, Sigma International is working with legacy system applications. It’s key
problems which impact the revenue have been identified as:
• Poor credit management result in receivables getting piled up
• Customer dissonance due to long Order to Cash cycles
• Poor transparency of inventory resulting in revenue blockage

L&T Infotech - Confidential Page 698 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

• Poor Forecasting and lack of early warning in sales dip due to inefficient business
analytics

Problems with current systems – the IT Managers

• Disparate systems for Order Management, Shipment and Invoicing resulting data
redundancy and high cost of maintenance of current systems
• Inability to respond to market changes – adding a new processes is not easy in the
current systems
• Current systems unable to take the load of business – transactions have grown over
the past few years and the systems are not geared up for it

L&T Infotech - Confidential Page 699 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

86.2 Deliverables

Phase Activities Deliverables Owners

Project • Define the • Overview of Smita/Subhalakshmi/Partha
Preparation system the Project
Landscape Management Project Presentation: Kirti/Atul
• Project Plan
Management • Project
Plan Presentation
Preparation
• Level 0
Training
Business • Development • Business Ashwin/Sujoy/Raja
Blueprint System Setup Blueprint
• Business Document
Process • Gap Analysis
Mapping Document
Realization • QA system • Configured Shikha/Umesh/Rajasekhar/
Setup System Rekha/Sumita (system
• Configuration • Configuration configuration + configuration
• RICEF Document document)
Developments • Functional
• System Specifications Functional Specs /
Authorizations • Technical Technical Specs – (Ashwini &
• Testing Specifications Lenin)
• Authorization
Matrix
• Test Scripts
Final • Production • Configured Testing / Data Migration & cutover
Preparation System Setup and tested (Harsha, Ravi, Kamili)
• Data Migration production
(Cutover) system with LSMW - Umesh

L&T Infotech - Confidential Page 700 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

• End User master data

Training • End User
• End User Training
Documentatio document
n
Go Live and • System • Issue Logs Gajanan/Deepak/Manideep/Shelke
Support Administration
• Application
Support
• Data Archiving

L&T Infotech - Confidential Page 701 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

86.3 Configuration Decisions

Organization Structure
• One Sales Organization would cater to both domestic and export Sales
Pros:
o Ease of use during creation of Sales Order / Master Data
• Two distribution Channels – Direct Sales / Exports
Pros:
o Same Products are priced differently for exports
o Exports have a different set of users requiring different authorizations
o Credit is managed differently for India and Export Sales
o Leverage standard SAP reports with Sales Area
o Master Data maintenance will still remain easy if we use common
distribution channels/division
• One header division & Item divisions: Diesel & Gas
Pros:
• Common header division ensures ease of order entry
• Item Divisions will help in reporting and pricing
• Sales Offices: Pune, Kolkata, Hyderabad, Delhi and Chennai

L&T Infotech - Confidential Page 702 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

86.4 System Configuration Requirements

Item Process Dependency Responsibility
C-01 Setting up Organization Structure
Sales Organization – SG00 Rekha
Distribution channels:
DS – Direct Sales
EX – Exports
Header Division - SG
Item Division - DG, GG
Sales Areas: SG00-DS-SG
SG00-EX-SG
Sales Office: KOL, PUN, DLH, EXP
Sales Group: SG
C-02 Plants – CHEN, PUNE
Assign SG00-EX to CHEN Umesh
And SG00-DS to Pune
Shipping Points – CHEN, PUNE
Assign Shipping to Plants same to same
C-03 Master Data Creation: C-01
Customer Master – C-02 Rekha
Domestic : D-1000
Exports : X-1000

Domestic – DG-1000
Exports – NGK-1000,

Vendor Master: V-1000 (Gamma Genco)

C-04 Procurement of Generators from Gamma C-03
Genco: Purchasing Info record/ Purchase Shikha
Order – GR - IR
C-05 Sales to Domestic Customers from C-01/C-02/C- Rajasekhar
Warehouse 03/C-04

L&T Infotech - Confidential Page 703 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Order type : YDIR/TAN /CP/LF/F2

C-06 Sales to Domestic Customers directly C-01/C-02/C- Sumita
through the vendor 03/C-04
YDIR/TAS/CS/F2 including non valuated
MIGO/MIRO
C-07 Export Sales from Chennai Warehouse C-01/C-02/C- Shikha
YEXP/TAN/CP/LF/F2/F8 03/C-04
C-08 Returns Processes wrt Billing document C-01/C-02/C- Umesh
RE-REN-CN-LR-G2 03/C-04

Common Configuration
C-09 Pricing YSG00 (PR00) Creation of doc Shikha
types YDIR &
YEXP & RE
C-10 Partner Determination YSGPR Creation of doc Sumita
(SP,SH,PY,BP) types YDIR &
YEXP & RE
C-11 Incompletion Log (use standard) Creation of doc Rajasekhar
types YDIR &
YEXP & RE
C-12 Revenue Account Determination (A/c F2 Document Rajasekhar
800000) type
C-13 Reconciliation Account Determination F2 Document Rajasekhar
(Exports – 140020, Domestic - 140000) type
C-14 Shipping Point Determination Plant Rekha
C-15 Storage Location Determination Plant / Shipping Rekha
Point
C-16 Route Determination Customer Shikha
Master/Shipping
Point/Material
Master
C-17 Serial Numbers Material Master Sumita

L&T Infotech - Confidential Page 704 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

86.5 Technical Enhancements

Item Process Dependency Responsibility
T-01 Delivery Report
Selection Screen Functional
Shipping Point (parameter)- X Specs – Lenin
Delivery Number (sel)
Customer (sel) Technical
Sales Area (parameter) Specs –
Delivery Creation Date (sel) - X Ashwini

Report Layout Development

Delivery Number – Ashwini
Ship to party
Item Test Script
Material - Harsha
Quantity
Goods Issue Status
Goods Issue Date

Tcode: ZDEL

L&T Infotech - Confidential Page 705 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Day 27: 11-Mar-11

87.0 Creating a Business Blueprint

We document the business process requirements of the company in the business blueprint
phase. The key objectives of this phase are:
• Clarify Scope to a working level
• Gather and validate requirements
• Drive Decision on solution design
• Get enough detail to begin configuration
• Control changes going forward by freezing requirements

At a very broad level, the process consists of analyzing the customer business processes
and mapping it with SAP delivered processes. What cannot be mapped comes out as Gap
Analysis. This is also fit-gap analysis.

The process of blueprinting consists of:

1. Start with pre-blueprint knowledge i.e.; the project scope document / statement
of work
2. Make a listing of broad level business processes in the organization
3. Subject Matter Experts are assigned to the business processes
4. Brainstorming sessions are held on each of the business processes
• Note1: Audience should include both Managers and operating level employees.
Operating level employees have an in-depth knowledge of specific processes,
while managers have an overview of end to end processes as well as the
controls required and the Key Performance Indicators (KPI)
• Note2: Process requirements differ depending on the audience. The operating
level is more concerned on transactions and basic reporting; Management is
more tuned towards control and strategic reporting. KPIs of both these groups
are very different. It’s equally important to understand the requirements of all
stakeholders in the project.
• Note3: All business transactions are financial transactions and are visible
throughout the order to cash cycle. It could be price, rebates, inventory,
payment terms, discounts, taxes Audits, etc. Having a full time involvement of
a financial expert of the organization brings a lot of value to the process.
L&T Infotech - Confidential Page 706 of 730
 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

5. Brainstorm Solutions in SAP vis-à-vis the requirements

6. Develop the To-Be Processes
7. Convert the solutions to specific requirements.
8. The outcome of the business blueprint is a baseline configuration document and
technical developments to be done.

Requirement gathering Workshops:

• Workshops are conducted during which business processes and individual
functional requirements are defined and analyzed
• In addition, the workshops serve to refine the original project goals as well as to
revise the overall project schedule
• Note: There are nice-to have functionalities and must-haves functionalities. All
functionalities have to be analyzed and prioritized.

87.1 Business Scenario Requirements

This determines the business scenarios and the company’s high level requirements of the
to-be solution. In addition, you define the business organizational structure, together
with the general settings and master data settings.
• Analyze the company’s current processes before defining the Organizational
structure. The organizational structure needs to be defined before business
process requirements and general information can be documented
• Identify the business scenarios in scope, and document the high level requirements

The different views of a company must be shown by the Organization Structure

• Legal View
• Fiscal View
• Functional View
• Product Oriented View
• Regional and geographical View
• Customer Group View
• Distribution Channel View
• Purchasing Channel View

L&T Infotech - Confidential Page 707 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

From this workshop, we get the following:

• Number of legal entities and organizational Elements
• Identification of geographic and hierarchical scope
• A baseline for process analysis (which organizational structure is affected by which
process)

After the requirements are analyzed, they should be harmonized. This is done in 2
steps:
• The first workshop can be in the format of interviews with Q&A session,
culminating in a high level design of the organizational structure of the
business. All discovery work is done here
• The second workshop presents a design for approval and confirmation

What happens if you don’t do this?

• Organization elements in SAP won’t get defined
• Master Data Design
• Business Process Design
• Data Conversions

In an imperfect world, it makes sense to first make assumptions and then confirm these
assumptions during the business process design. It is possible that additional
requirements will be discovered during the realization phase that has an impact on the
organization structure.

L&T Infotech - Confidential Page 708 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Day 28: 12-Mar-11

88.0 Planning the final case study presentation

Project Sigma – Case Study Walkthrough

Project Background – Atul Bichkar / Smita / Partha / Subhalakshmi/ Kirti (12th March
2011)
• Client Overview
• Drivers for Implementing SAP – KPIs (Current Business / Software challenges /
Current data on 3 KPIs)
• Business Processes in Scope
• System Landscape
• Project Location & Schedule with phases (6 month)
• Project Organization
• Project Management Plan Overview
• Project Value
• Project preparatory Activities

Business Blueprint – Ashwin / Sujoy / Raja

• Requirement Gathering Methodologies – Workshops, Interviews, High level business
scenario, Schedules, Assignment of SMEs
• Business Blueprint Components: Organizational Structure, Master Data & General
settings, Business Scenarios
• To-be Processes in SAP
• Demonstration - Functional Specifications
• Demonstration - Business Blueprint with Gap Analysis & Baseline functional scope
• Demonstration - Business Blueprint Sign-off document

Realization
• Configuration Planning & dependencies (Shikha/Sumita/Rekha)
• Demonstration – Requirement Traceability Table (Umesh / Rajasekhar)
• Demonstration - Configuration document (Rekha/Shikha/Umesh/ Rajasekhar
/Sumita)

L&T Infotech - Confidential Page 709 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

• Demonstration - Technical Specifications Ashwini.

• Demonstration – All Configured Processes: Umesh / Rajasekhar
• Demonstration – Test Methodology (Unit Testing & Integration Testing) / Test
Cases: Harsha/Ravi/Kamili
• Demonstration – Authorization Matrix: Harsha/Ravi/Kamili

Final Preparation
• Set up of the Production Server - Harsha/Ravi/Kamili
• Data Migration – Master Data & Transactional Data - Harsha/Ravi/Kamili
• End User Training strategy - Harsha/Ravi/Kamili
• Demonstration - Creation of Training Material - Harsha/Ravi/Kamili
• Demonstration: LSMW Tool for customer Master - Umesh

Go-Live and Support – Gajanan/Deepak/Shelke/Manideep

• Support Organization Structure – Level 1 and 2 Support
• Service Level Agreements – Response time and resolution time
• Support Escalation Matrix
• Demonstration: Support Issue Log created

Project Controls - Atul Bichkar / Smita / Partha / Subhalakshmi/ Kirti

• Document Naming Conventions
• Development Standards
• Status Review - Steering Committee Meetings for Project Review - Monthly
• Status Review - L&T InfoTech Delivery Head / Delivery Manager Review / Global
Operations Head - Monthly
• Status Review – Weekly Project Team Meetings with Project Manager
• Demonstration - Risk Monitoring Log
• Demonstration - Decision Recording Log
• Demonstration - Project Status Report
• Demonstration - Resource Register
• Quality Processes Followed – Process Compliance Index (PCI)
• Customer Satisfaction Index (CSI)
• Time sheet Compliance / Dress Code / Uniform Code of Conduct

L&T Infotech - Confidential Page 710 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Lessons Learnt - Gajanan/Deepak/Shelke/Manideep

• Business Blueprint Phase
• Realization Phase
• Testing
• Scope Creep
• Unavailability of servers on time
• Cutover Planning – Master Data Standardization
• Customer took lot of time to finalize organization structure

Implementation benefits - Harsha/Ravi/Kamili

• KPI comparison before and after
• Soft benefits

L&T Infotech - Confidential Page 711 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Day 29: 09-Mar-11 – The End

89.0 Enhancements to the SAP System
System code changes / Creation of Tables etc. are done using Developer logins.
Developer logins has to be registered in the SAP Marketplace i.e. OSS (Online Service
System). All ABAP development is independent of the client in a server.

90.0 Determining a number range dynamically during saving a

sales order – My First User Exit ☺

SE38 – MV45AFZZ: This user exit determines the sales document number based on the
customer code. For customer CL1A111, number range 03 is required and for customer
CL1A112, number range 05 is required.

FORM USEREXIT_NUMBER_RANGE USING US_RANGE_INTERN.

IF VBAK-KUNNR = 'CL1A111'.
US_RANGE_INTERN = '03'.
ENDIF.

IF VBAK-KUNNR = 'CL1A112'.
US_RANGE_INTERN = '05'.
ENDIF.

ENDFORM.

Note: In the above example, we have hardcoded the customer as well as the number
range. In actual projects, hard coding should be avoided. Using the above example, what
we should be doing is creating a Z table with fields Customer and number range.
Logic:
Go to table ZNUMBER, check if the customer in the sales order has an entry in this table.
If it finds an entry, pick up the number range assigned in table ZNUMBER else continue
with normal numbering as defined in the sales document type.

L&T Infotech - Confidential Page 712 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Note: Every table has a compulsory field called MANDT. If you do not put this, the system
automatically hunts for data in client 000.

FORM USEREXIT_NUMBER_RANGE USING US_RANGE_INTERN.

TABLES: ZNUMBER.

SELECT SINGLE * FROM ZNUMBER WHERE ZKUNNR = VBAK-KUNNR.

IF SY-SUBRC = 0.
US_RANGE_INTERN = ZNUMBER-ZNUMBER.
ENDIF.

ENDFORM.

L&T Infotech - Confidential Page 713 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

91.0 Customer Master Checks using Exits – Tcode CMOD

L&T Infotech - Confidential Page 714 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

92.0 Appendix

92.1 Set Start Transaction

We set sales order as the start transaction. Whenever you log in, the system straight
away takes you to the sales order till you deactivate this.

92.2 Sales Order Tables

Sales Order data gets stored in tables VBAK and VBAP.

L&T Infotech - Confidential Page 715 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

92.3 Viewing Users in the System – SM04

92.4 Creating SD Number Range – Tcode SNRO

Select number ranges.

L&T Infotech - Confidential Page 716 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Status:

L&T Infotech - Confidential Page 717 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

92.5 Finding technical names of fields from master data /

transaction data

You want to find out the table and field name of PO Number in the sales order header.

Go to field and press F1.

L&T Infotech - Confidential Page 718 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Select . You see the table name and field name details. VBKD-BSTKD

Note: In many cases you see structure instead of table. To find out the table name, there
are other ways here.

L&T Infotech - Confidential Page 719 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

92.6 Personal Settings for F1 Help

When you select Modal Dialog box,

L&T Infotech - Confidential Page 720 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Now if you select F9, the technical information is seen directly.

When you select ‘Performance Assistant’.

L&T Infotech - Confidential Page 721 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

92.7 Setting standard customizing Request

L&T Infotech - Confidential Page 722 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

Select Set Standard Request. .

The white band denotes a standard request.

Set Validity Period of Standard Request

L&T Infotech - Confidential Page 723 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

92.8 Setting defaults using parameter IDs

When you a sales order or any transaction, you have to enter org structure, etc.

Example: We want to default Sales Organization. Do a F1-F9 on the field. The parameter
ID is VKO.

L&T Infotech - Confidential Page 724 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

92.9 Viewing Customer Master – Administrative Data

Tcode: VD02/XD02/FD02

L&T Infotech - Confidential Page 725 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

92.10 Viewing Sales order Document flow

92.10.1 Viewing Document Flow at Header Level

L&T Infotech - Confidential Page 726 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 727 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

92.10.2 Viewing document flow at item level

L&T Infotech - Confidential Page 728 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

L&T Infotech - Confidential Page 729 of 730

 FTR Boot Camp Training
Mar 09 2011
Author: Kaushik Sarkar

92.11 Settings overview of sales document type

Sales document customizing Setting Explanation

1. Sales Document Block
2. No. Range Internal Assignment
3. No. Range External Assignment
4. Item Number Increment
5. Item Division
6. Read Info Record
7. Check Purchase Order Number
8. Enter PO Number
9. Fcodes for Overview Screen
10. Document Pricing Procedure
11. Propose Delivery Date
12. Lead Time
13. Propose PO Date
14. Incomplete Messages

L&T Infotech - Confidential Page 730 of 730