Sales Order Management Transactions

GENERAL ORDER MANAGEMENT
Reviewing Document Flow VA03
Searching for a Customer Sales Order by Serial Number ZV11
Order Inquiry ZV33

SALES ORDER PROCESSING
Creating Sales Order VA01
Maintaining a Sales Order VA02
Displaying a Sales Order VA03
Releasing an Order or Delivery from Credit Hold: Non-Flooring VKM1
Releasing an Order or Delivery from Flooring Hold ZKM1
Manually Pre-authorizing Blocked Credit Card Orders Z.14
Display List of RMAs by Customer VA05
Confirm RMA Goods Receipt VL02
Generate list of open return orders for deletion VA05
Display Customer returns eligibility MCSI
Removing a Billing Block (Approving Credit/Debit Requests) V.23

PRICING MASTER DATA
Create Pricing VK11
Creating a Sales Deal VB21
Maintaining a Sales Deal VB22
Displaying a Sales Deal VB23
Maintaining Prices VK12
Displaying Prices VK13

MATERIAL MASTER DATA
Creating Material Substitution Master Data VB11
Maintaining/Deleting Material Substitution Master Data VB12
Displaying Material Substitution Master Data VB13
Creating a Bundled Master MM01
Creating a Sales BOM CS01
Maintaining a Sales BOM CS02
Displaying a Sales BOM CS03

CUSTOMER MASTER DATA
Creating Partner Records XD01
Maintaining Customer Master Data XD02
Displaying Customer Master Data XD03
Deactivating a Partner VD06
CUSTOMER CREDIT INFO
Creating/Maintaining New Customer Credit Information FD32
Displaying Customer Credit Information FD33
Blocking or Unblocking a Customer VD05

SHIPPING
Creating a Delivery VL01
Displaying a Delivery VL03
Deleting a Delivery VL02
Shipment Inquiry / Display VT03
Adjusting Transfer Order - Confirmation Quantity LT12
Collectively Confirm Transfer Order LT25
Batch Shipment Confirmation VL19
Creating Service Provider/Carrier Master Data XK01
Maintaining Serive Provider/Carrier Master Data XK02
Displaying Service Provider/Carrier Master Data XK03
Maintaining Product Master/Serial # Profile/Unit of Measure/Shipping Unit MM02
IDoc Inquiry WE02 / WE05
Workflow Instructions

BILLING
Invoicing a Customer Shipment VF01
Reprinting an Invoice VF31
Releasing a Sales Order for Billing V.23
Creating an Invoice by Using the Billing Due List VF04
Checking Open Billing Documents VF05
Create Credit/Debit Memo FB01
A/R
Controlling Total Debit/Credit bkgs F.03
Generate FI Account balance F.08
Generate Month-to-date Inv. register F.02
Process payments FBZ1
Rqst Individual Customer Corresp. FB12
Generate Customer Correspondence F.61
Enter Batch totals under Control ttl FB07
Display G/L Acct. totals FBL3
Reverse Posted Amounts FB08
Customer Refunds FBL6
Customer Refund to other than Payer FB05
Clearing Debit/Credit on Cust. acct. FB1D
Customer Balance in Local Currency F.23
G/L Account Balance Report F.08
Create Invoice - legal entity adjust FB01
Generate Cust. Acct. statements F.27
Generate Dunning Letters F150
Generate Billing Due List VF04
Generate Blocked Billing Doc list VFX3
Inq. via Credit Release Screen VKM1
List orders by partner VA05
Past Due invoices by customer FD11
Check number info by G/L account FBL3
Display customer Line items FBL5
TREASURY - CASH APPLICATION:
Post Customer payments FF68
Verify if A/R is updated FB03


Some inportant transaction for Sales and Logistics are as follows:
VS00 - Master Data;
VC00 - Sales support;
VA00 - Sales;
VL00 - Shipping;
VF00 - Billing.
VD01 - Create customer master;
VD02 - Change customer master;
VD03 - Display customer master;
XD01 - Create customer master centrally;
XD02 - Change customer master centrally;
XD03 - Display customer master centrally;
VD04 - Customer account changes;
VD06 - Customer deletion flag;
VKM3/VKM4 - Sales documents list.
MM01 - Create material master;
MM02 - Change material;
MM03 - Display material.
MMBE - Stock Query
MB52 - Ware house Stock
VA01 - Create sales order;
VA02 - Change order;
VA03 - Display order;
VA05 - Sales order list.
ME21N - Purchase Order
ME51N - Puchase order from Purchase requisition
MIGO - Goods Movement



VL01 - Create delivery;
VL02N - Change delivery document;
VL04 - Delivery due list;
VKM5 - Deliveries list;
Vl09 - Goods issue cancel.
VL31n- Inbound delivery
VF02 - Billing document change;
VF04 - Billing due list;
VF11 - Billing document cancel.
CO09 - Material availability overview;
MMBE - Stock overview.
VOV4 - Assign Item categories;
VOV6 - Scheduling line categories;
VOV8 - Define Sales document.
VOK0 - Maintain Pricing;
V/06 - Pricing;
V/07 - Access sequence;
V/08 - Maintain pricing procedure;
OVKP - Pricing procedure determination.
VK11 - Maintain Condtion recoreds;
IW21 - Create notification
IW31 - Create work order
IE01 - Create Equipment master
FPE1- Create document
FPE2- Change document
FPE3- Display document
INSOCREATE - Create Insurance object
INSOCHANGE - Change Insurance object
INSODISP - Display Insurance object

ERP and Change Management

ERP calls for a lot of change. The changes can be categorised as follows:

Business Processes

The business processes are most likely to undergo some changes. These changes could even involve scrapping the process entirely or tasks in the process, if they are considered as a redundant tasks in the ERP environment.

Organisation Authority, Jobs and Roles

The organisation authority and role definition of an individual also changes. In the new environment, information is available on-line, and access to information makes it easier to take decisions quickly at any levels. This creates new jobs and role definitions and new authority definitions.

Performance Measures and Rewards System

The new system also calls for a revised set of performance measures and rewards system. This is necessary since ERP causes a change in the job definition and role definition of the organisation employees.

Technology and IT Infrastructure

ERP involves a change in the existing technology and IT infrastructure. The architecture of ERP system requires an upgradation of the existing hardware and implementing of new technology.

Implementing ERP – Business Process Re-engineering

An ERP implementation involves a number of steps. In effect these steps lead to a BPR. Business Process Re-engineering can be of two types – The Big ‘R’ or the small ‘r’. The big ‘R’ re-engineering is the complete re-engineering of all the process. The small ‘r’ re-engineering is a package enabled re-engineering. At L&T, we have adopted the small ‘r’ or the package enabled re-engineering. In a package enabled re-engineering, the changes are made in the business process to adapt to the package.

A typical ERP implementation involves the following steps:

AS-IS Analysis:

This involves an in-depth analysis and mapping of the existing business processes. In the AS-IS phase, there were many good but disjointed systems. All the systems were independent of each other and there was no integration between the various systems.

TO-BE and GAP Identification:

This stage reflects the business process re-engineering phase. Once the existing business processes are mapped, then the second step is to identify how the organisation would require the particular business process to be addressed after implementing ERP. The business process may be continued to be addressed as it is being done so or the organisation might go in for a different method of addressing the business process. Thus each and every process mapped at the AS-IS phase is re-visited with a view of objectively analysing the same and thus increasing the effectiveness of the business process. Each AS-IS process is mapped to a TO-BE process.

After the TO-BE maps are prepared, each TO-BE map is studied with respect to how the ERP package addresses these processes. In this way each and every TO-BE map is studied and the end of the exercise, a list of issues that are not addressed directly by the ERP system, is generated. This list is called as the GAP List. GAPS are those business processes, which are not directly addressed by the ERP system. It is then decided whether to use workarounds, or develop patches, which will address these missing links, or decide not to address the GAP – if the process is not affected by it.

Prototyping and Design

In the prototyping and design stage, a design or prototype of the new configuration is created. This involves creating a story situation wherein the whole cycle of the business process is simulated in the system.

Construction

In the construction phase, the configurations are done, new developments (forms, reports and BDCs) are made for the new requirements. These configurations are first done in the development environment and then tested thoroughly before transporting the same to the production environment.

User Acceptance Test (UAT)

The users are trained in the new system and set of users representing the user community, are selected for conducting the testing and confirm their acceptance after testing the system and satisfying themselves regarding the same.

Go-Live

After the users have tested the system and given the user acceptance, a cut-off date is decided for going live in the new system. The go-live could be done by two methods. The organisation can decide to use the new system as well as the old system for some time. This method is called as handholding and is usually adapted for accounting systems. The other method is to decide a date from which all new transactions will be entered and will be available in the new system.