Transaction Code Doubts

[Former Member]

Hi,

What is the purpose of creating sales order and where we use.Like this i want to know for ME11,ME21N,MM01,VF01,VT01.

Can any of u give me a clear idea abt this.

Regards,

Divya

[Former Member · Accepted solution]

Hi Divya,

A sales order is created when the vendor wants to sell some goods produced by him to the customer. He shall server the customer according to his request based on this sales order. He shall have all the items that are required by the client on this sales order.

ME21: For Creation of Purchase Order. Purchase Order is created by the company for purchasing some goods like raw material, inorder to produce the goods that is required by the customer. Based on this purchase order the company gets the goods. Inturn these goods are used in making the final good that is required by the customer.

VF01: For creation of Invoice/Bill. This would be based on the goods that are delivered. Once the customer is delivered with goods, the company would want to get the required amount for the goods. So the company prepares a bill for him to pay. this is created in this transaction.

VT01: For Creation of shipment. Company would require customer shipment details inorder to deliver the goods to the customer. So shipment is created in this transaction.

Reward points if this helps,

Kiran

[Former Member · Accepted solution]

Hi kiran,

Can u plz explain the purpose of changing the above tcodes.

Thanks in Advance,

Divya

[Former Member]

ME11is ues to create info records.

The info record allows buyers to quickly determine:

Which materials have been previously offered or supplied by a specific vendor

Which vendors have offered or supplied a specific material

Content of an Info Record

The info record contains:

Data such as prices and conditions that you can store for the relevant purchasing organization or plant.

Number of the last purchase order

Tolerance limits for overdeliveries and underdeliveries

Planned delivery time (lead time required by the vendor to deliver the material)

Vendor evaluation data

Indicator showing whether the vendor counts as the regular vendor for the material

Vendor sub-range to which the material belongs

Availability period during which the vendor can supply the material

The info record contains quotation and ordering data. The data in the info record (prices for example) is also used as default data for purchase orders.

For instance, you can store the current and future quotation conditions (discounts, fixed costs etc.) in the info record, in order to be able to copy them into Pos. You can also maintain the vendor’s conditions directly in the info record.

Organizational Levels

An info record can apply to the following organizational levels:

Purchasing organization

Plant

Procurement Types in Info Records

Standard

A standard info record contains information for standard purchase orders. The info records can be created for materials and services with and without master records.

Subcontracting

A subcontractor info record contains ordering information for subcontract orders. For example, if you subcontract the assembly of a component, the subcontractor info record would include the vendor's (subcontractor’s) price for assembling the component.

Pipeline

A pipeline info record contains information on a vendor’s commodity that is supplied through a pipeline or pipes (for example, oil or water) or by similar means (for example, electricity through the mains). The info record contains the vendor’s price for the consumption of such commodities by the buyer ("pipeline withdrawals"). You can store withdrawal/usage prices for different validity periods.

Consignment

A consignment info record contains information on a material that vendors keep available at their own cost on the orderer’s premises. The info record contains the vendor’s price for withdrawals by the orderer from consignment stock. As in the case of the pipeline info record, you can store prices for different validity periods.

ME21N: is used to create purchase order

A purchasing document is an instrument used by Purchasing to procure materials or services.

The following list shows the various external purchasing documents available in the standard SAP System. (Note: purchase requisitions are not included on this list because they are usually regarded as internal documents used within Purchasing and are therefore treated separately.)

Request for quotation (RFQ)

Transmits a requirement defined in a requisition for a material or service to potential vendors .

Quotation

Contains a vendor's prices and conditions and is the basis for vendor selection.

Purchase order (PO)

The buying entity’s request or instruction to a vendor (external supplier) to supply certain materials or render/perform certain services/works, formalizing a purchase transaction .

Contract

In the SAP Purchasing component, a type of "outline agreement", or longer-term buying arrangement . The contract is a binding commitment to procure a certain material or service from a vendor over a certain period of time.

Scheduling agreement

Another type of "outline agreement", or longer-term buying arrangement. Scheduling agreements provide for the creation of delivery schedules specifying purchase quantities, delivery dates, and possibly also precise times of delivery over a predefined period

Requirements of materials or services can be reported to Purchasing by means of purchase requisitions.

Each purchasing document is subdivided into two main areas: the header and individual items . Each document will contain a header and can contain several items.

The header contains information relevant to the whole document . The items specify the materials or services to be procured . For example, information about the vendor and the document number is contained in the document header, and the material description and the order quantity are specified in each item.

The additional data provides extra information about the item, and has no direct connection with the item procurement data. Additional data includes, for example, account assignment data (such as cost center and G/L account) and the PO history for an item, which contains information on already recorded goods and invoice receipts relating to the item

Each item in a purchasing document represents a unit of procurement . Purchasing operations (involving requisitioning, ordering and follow-up processes) occur on an item-specific basis.

MM01 is used to create material.

Material master records are created when the MM module is first installed. Thereafter, the departments using the material master database are responsible for keeping the information it contains up to date.

Material master records may be created and changed either centrally or by individual departments. In the latter case, for example, the Purchasing Department will be responsible for continually updating purchasing data and, in the same way, Sales will be responsible for maintaining sales and distribution data.

What is a Material Type?

The material type identifies the characteristics of a material that are important with regard to Accounting and Inventory Management. A material is assigned a type when you create the material master record.

"Raw materials" and "finished products" are examples of material types. In the standard MM module, the material type for the former (ROH) denotes an externally procured (bought-in) material, whereas the material type for the latter (FERT) indicates that the relevant material is produced in-house.

The material type determines the accounts to be debited or credited when a material enters or leaves the stores/warehouse, or is used or consumed by a user department. It also determines whether numbers for materials are assigned by the system (internally) or by the user (externally).

When Do You Create or Maintain a Material Master Record?

You have to create or maintain a material master record if the material to be procured:

Is not defined in the material master database (that is, the material does not have a master record)

Has already been defined for a different plant, but not for the plant for which the PO is to be issued

Has been defined for the correct plant, but the purchasing data for the material has not been entered. This may be the case if a user from another department (Accounting for instance) created a material master record but was not authorized to add the data relevant to Purchasing.

To determine whether or not a material has a master record, try to display the material using the Possible entries facility. In doing so, proceed as described under Displaying a Material Master Record.

Prerequisites

Before creating a material master record, you need the following information:

The material type and industry sector

The units of measure, such as the base unit (stockkeeping unit), and the order unit

The purchasing group (buyer group) responsible for the material

Accounting data, such as the valuation class, price control, and standard or moving average price

VF01: create invoice or billing document.

Umbrella term for invoices, credit memos, debit memos, pro forma invoices and cancellation documents.

Use

The billing document is created with reference to a preceding document, in order to create an invoice or a credit memo, for example.

The billing document contains the following data:

Structure

All billing documents have the same structure. They are made up of a document header and any number of items. The following figure shows how billing documents are structured.

Header

In the header, you find general data valid for the entire billing document. For example,

Identification number of the payer

Billing date

Net value of the entire billing document

Document currency

Terms of payment and Incoterms

Partner numbers, such as the identification number of the sold-to party

Pricing elements

Items

In the items, you find data that applies to one particular item. For example,

Material number

Billing quantity

Net value of the individual items

Weight and volume

Number of the reference document for the billing document (for example, the number of the delivery on which the billing document is based)

Pricing elements relevant for the individual items

The billing document is controlled via the billing type.

Integration

When you create a billing document, the billing data is forwarded to Financial Accounting.

VT01 is used to create shipment

Implementation Options

Shipping is an important part of the logistics chain in which guaranteed customer service and distribution planning support play major roles.

In shipping processing, all delivery procedure decisions can be made at the start of the process by

Taking into account general business agreements with your customer

Recording special material requests

Defining shipping conditions in the sales order

The result is an efficient and largely automatic shipping process in which manual changes are only necessary under certain circumstances.

Integration

The Shipping component is integrated under the Logistics Execution component. Shipping is a subsequent activity of the Sales component.

Range of Functions

The shipping module supports the following functions, which include but are not limited to:

Deadline monitoring for reference documents due for delivery (sales orders and purchase orders, for instance)

Creating and processing outbound deliveries

Planning and monitoring of worklists for shipping activities

Monitoring material availability and processing outstanding orders

Monitoring the warehouse's capacity situation

Picking (with optional link to the Warehouse Management system)

Packing deliveries

Information support for transportation planning

Support of foreign trade requirements

Printing and transmitting shipping documents

Processing goods issue

Controlling using overviews of

Deliveries currently in process

Activities that still are to be carried out

Possible bottlenecks

A list of deliveries posted as goods issue in the shipping department could be used to form a worklist for the billing department.

[Former Member]

Hi,

just go through this document,

Note: Mostly, VT01 MM01 VA01 all these will be with respect to creating a shippment doc or material management or sales order etc..

ie, '01' series --> for creation,

'02' series --> for change,

'03' series --> for display.

EDI Specific Transactions

VOE1 Translation between EDI categories and SD item categories

VOE2 Table EDSC view. Customer link to sales area detail

VOE3 Table view EDPVW. Add partner types that will be transferred to the IDoc

VOE4 Table view EDPAR. Link external partner number with our internal number

WEDI EDI Administrator Menu

BALE Idoc Administration

Scheduling agreements

OVA9 Create entries for each sold-to customer for which you will receive EDI schedule releases. At implementation, the only field that needs to be maintained is "Check PO number," which causes SAP to make sure that the PO number sent on the release matches the PO number on the schedule agreement. This transaction updates table T663A. SAP will not post an EDI schedule release, if this record is missing.

OVAI Create entries for each Vendor / Partner description combination. (Vendors must match sold-to Acct. at Cust., and Partner descriptions must match ship-to Partner descriptions.) This transaction updates table T661W. SAP uses this table to determine the schedule agreement sold-to partner.

OVAJ If you would like SAP to post schedule requirements using discrete dates only, instead of weekly and/or monthly buckets, you can indicate the days of the week that you deliver to this customer. SAP will divide the customer's quantity for a week or month evenly into the days of the week specified by the distribution function code. This code must be sent in the DELINS IDoc in field E1EDP16-ETVTF.

IDoc Transactions

WE09 / WE02 IDoc lists according to content. View IDocs via specific IDoc number or business application detail contained within the contents of a segment.

WE05 View IDocs

WE19 EDI test tool. Use to test inbound Function module changes.

WE20 Partner profile configuration. Add partner detail together with inbound and outbound relationships. We also incorporate message control on the outbound IDocs. Utilize the organizational units to trap functional errors for further processing

WE30 Create IDoc extension type

WE31 Segment create

WE57 Assign function module to logical message and IDoc type

WE60 IDoc type documentation tool

WE82 Link Release detail to Extension IDoc Type

BD55 Conversion rule user exit. Link conversion rule user exit to the different system \ partner combinations

BD87 Reprocess IDocs in error or waiting for action. (Both inbound and outbound in 4.6. Use BD88 in prior versions)

BALA ALE Application Distribution

BALM ALE Master Data Distribution

Output determination

856 - ASN

V/36 Maintain output determination for deliveries (Output determination procedures). V10000 (Header output) has condition type LAVA (usually with requirement 1 NB: Use V/84 – V7ALLE – SHAD for grouped ASNs. I.e. Group deliveries into shipments

VV21,VV22,VV23 Create output condition records for shipping. LAVA – WE (Partner function) - We must add each new partner with VV21

VL71 Reissue output for deliveries

810 - Invoice

V/54 Maintain access sequence for billing documents

VV31,VV32,VV33 Create condition records for billing documents. (RD00 – RE Billing party)

VF31 Reissue output for billing documents

855 – Order Response

V/30 Sales document output types (BA00)

V/48, V/32, V/43 Maintain access sequence for sales documents

VV11,VV12,VV13 Create condition records for sales documents. (BA00 – SP Sold to party)

Requirements coding

V/27 Create code to check requirements for output control. Used to check ZBA0 against BA00 output.

Sales & Distribution

Sales order / Quote / Sched Agreement / Contract

VA02 Sales order change

VA05 List of sales orders

VA22 Quotation change

VA32 Scheduling agreement change

VA42 Contract change

Billing

VF02 Change billing document

VF11 Cancel Billing document

VF04 Billing due list

FBL5N Display Customer invoices by line

FBL1N Display Vendor invoices by line

Delivery

VL02N Change delivery document

VL04 Delivery due list

VKM5 List of deliveries

VL06G List of outbound deliveries for goods issue

VL06P List of outbound deliveries for picking

VL09 Cancel goods issue

VT02N Change shipment

VT70 Output for shipments

General

VKM3, VKM4 List of sales documents

VKM1 List of blocked SD documents

VD52 Material Determination

Workflow

SWEAD Event queue administration

SWE2 Event type linkages

SWE3 Event linkages

PPOME Organizational Unit Maintenance

SWE5 Consistency Checks for Event Linkages

SWUD Workflow Diagnostic Tool

General

The following section provides detail on other useful SAP areas.

Create delivery via transfer orders

Once the order is saved proceed through the following steps. The process assumes the item has values in the warehouse bin.

VL04 Delivery due list. Run the delivery due with your order number to create the delivery

LT03 Create Transfer Order. EG. Warehouse: 101 and enter. Picking background. Save

The Transfer order should now be saved. It now needs to be confirmed.

In LT03 go to menu option Transfer Order -> Confirm – Transfer Order

Enter

Save

The transfer order is now confirmed.

VL02N Delivery change. EG: Edit the delivery to do the following Pack – External customer material number = COO. External delivery number – Waybill number. BOL – Transport tag. Carrier – Header partner – SP (E.G. FXP). Tracking number = Packing Unit

Purchase Orders

ME22N PO Change

ME57 Create PO from purchase requisition

ATP

CO09 Availability overview

Goods Movement

MIGO Post goods receipt

MB51 Material document list

MB01 Goods Movement

Other

MD04 Material Requirements. Shows material requirements and releases against materials

SE38 ABAP Editor. Used to modify ABAP programs

SM01 Transaction list. Lock transactions in the system. Also a good tool to see what transactions are available

SHDB Transaction recorder (BDC)

CMOD User exit \ project tool. Coordinates your changes into projects for the purpose of activating all user exits for a particular project. A user exit needs to be modified before it will work

SE16 Table contents display

SOST View mails sent externally from SAP

SU53 Check authorization object

SQVI Table Quickviewer – Used to created quick client dependent reports

ST22 ABAP Dump Analysis

ST01 System trace

ST11 Display developer trace

ST05 SQL Trace

SM21 System log

ST22 Display short dumps

SM12 Display locked entries

Programs

List of ABAP Reports

Idoc

RBDAPP01 Post inbound Idocs to application documents

RBDAGAI2 Re-processing of IDocs after ALE input error

RBDAGAIE Reprocessing of edited IDocs

RBDMANIN Start error handling for non-posted Idocs

RSEINB00 Idoc inbound processing by file

RSEOUT00 Process outbound IDocs

General

RV80HGEN Report 'RV80HGEN' for including customer-specific routines in the SAP standard source code is not included automatically as an XPRA in the object list of the transport request. See OSS note 0385067. This report needs to be run in target clients once you have implemented a custom requirements definition.

RSWUWFML Report that interrogates the Workflow inbox, based on certain selections, and then forwards a notification to the respective users that they have email waiting in the SAP system. The auto-forwarding assignment of an email address to a user can be accomplished by the administrator and tx: SO36 or by the user themselves using tx: SO13. Use tx: SOST to view email status’ sent from SAP.

RHSOBJCH Corrects the following error in workflow customizing:

Transport object PDST

Information Table SOBJ is consistent as regards key tables

**Error** Table HRP1600 Not an entry in table SOBJ

Information Table SOBJ is consistent as regards PAD tables

See note 134311 (point 2). Note 60801 also recommends the same steps regarding RHSOBJCH.

RSPO0075 Run report RSPO0075 to activate access method M for device types.

ME21 - create purchase order

ME22 - change purchase order

ME51N - Create a Purchase Requisition

ME51N - Copy a Purchase Requisition

ME52N - Change a Purchase Requisition

ME52N - Delete a Purchase Requisition

ME54 - Individual Release of a Purchase Requisition

ME55 - Collective Release of a Purchase Requisition

MIGO - Receive Goods/Services

USMM Pressing F8 will display all hotpacks applied.

SEARCH_SAP_MENU Show the menu path to use to execute a

given tcode. You can search by transaction code or menu text.

DI02 ABAP/4 Repository Information System: Tables.

LSMW Legacy System Migration Workbench. An addon available

from SAP that can make data converstion a lot easier. Thanks to

Serge Desland for this one.

OSS1 SAP Online Service System

OY19 Compare Tables

SM13 Update monitor. Will show update tasks status. Very useful

to determine why an update failed.

S001 ABAP Development Workbench

S001 ABAP/4 Development Weorkbench.

S002 System Administration.

SA38 Execute a program.

SCAT Computer Aided Test Tool

SCU0 Compare Tables

SE01 Old Transport & Corrections screen

SE03 Groups together most of the tools that you need for doing

transports. In total, more than 20 tools can be reached from this

one transaction.

SE09 Workbench Organizer

SE10 New Transport & Correction screen

SE11 ABAP/4 Dictionary Maintenance SE12 ABAP/4 Dictionary

Display SE13 Maintain Technical Settings (Tables)

SE12 Dictionary: Initial Screen - enter object name.

SE13 Access tables in ABAP/4 Dictionary.

SE14 Utilities for Dictionary Tables

SE15 ABAP/4 Repository Information System

SE16 Data Browser: Initial Screen.

SE16N Table Browser (the N stands for New, it replaces SE16).

SE17 General Table Display

SE24 Class Builder

SE30 ABAP/4 Runtime Analysis

SE32 ABAP/4 Text Element Maintenance

SE35 ABAP/4 Dialog Modules

SE36 ABAP/4: Logical Databases

SE37 ABAP/4 Function Modules

SE38 ABAP Editor

SE39 Splitscreen Editor: Program Compare

SE41 Menu Painter

SE43 Maintain Area Menu

SE48 Show program call hierarchy. Very useful to see the overall

structure of a program. Thanks to Isabelle Arickx for this tcode.

SE49 Table manipulation. Show what tables are behind a

transaction code. Thanks to Isabelle Arickx for this tcode.

SE51 Screen Painter: Initial Screen.

SE54 Generate View Maintenance Module

SE61 R/3 Documentation

SE62 Industry utilities

SE63 Translation

SE64 Terminology

SE65 R/3 document. short text statistics SE66 R/3 Documentation

Statistics (Test!)

SE68 Translation Administration

SE71 SAPscript layout set

SE71 SAPScript Layouts Create/Change

SE72 SAPscript styles

SE73 SAPscript font maintenance (revised)

SE74 SAPscript format conversion

SE75 SAPscript Settings

SE76 SAPscript Translation Layout Sets

SE77 SAPscript Translation Styles

SE80 ABAP/4 Development Workbench

SE81 SAP Application Hierarchy

SE82 Customer Application Hierarchy

SE83 Reuse Library. Provided by Smiho Mathew.

SE84 ABAP/4 Repository Information System

SE85 ABAP/4 Dictionary Information System

SE86 ABAP/4 Repository Information System

SE87 Data Modeler Information System

SE88 Development Coordination Info System

SE91 Maintain Messages

SE92 Maintain system log messages

SE93 Maintain Transaction.

SEARCH_SAP_MENU From the SAP Easy Access screen, type it in

the command field and you will be able to search the standard SAP

menu for transaction codes / keywords. It will return the nodes to

follow for you.

SEU Object Browser

SHD0 Transaction variant maintenance

SM04 Overview of Users (cancel/delete sessions)

SM12 Lock table entries (unlock locked tables)

SM21 View the system log, very useful when you get a short

dump. Provides much more info than short dump

SM30 Maintain Table Views.

SM31 Table Maintenance

SM32 Table maintenance

SM35 View Batch Input Sessions

SM37 View background jobs

SM50 Process Overview.

SM51 Delete jobs from system (BDC)

SM62 Display/Maintain events in SAP, also use function

BP_EVENT_RAISE

SMEN Display the menu path to get to a transaction

SMOD/CMOD Transactions for processing/editing/activating new

customer enhancements.

SNRO Object browser for number range maintenance.

SPRO Start SAP IMG (Implementation Guide).

SQ00 ABAP/4 Query: Start Queries

SQ01 ABAP/4 Query: Maintain Queries

SQ02 ABAP/4 Query: Maintain Funct. Areas

SQ03 ABAP/4 Query: Maintain User Groups

SQ07 ABAP/4 Query: Language Comparison

ST05 Trace SQL Database Requests.

ST22 ABAP Dump analysis

SU53 Display Authorization Values for User.

WEDI EDI Menu. IDOC and EDI base.

WE02 Display an IDOC

WE07 IDOC Statistics

Hope this helps.

[Former Member]

here is list of all sap transaction codes

SPRO DEFINE ITEM CATEGORY

MM01 CREATE MATERIAL

MM02 MODIFY MATERIAL

MM03 DISPLAY MATERIAL

MMS1 CREATE MATERIAL MASTER

MMS2 CHANGE MATERIAL MASTER

MMS3 DISPLAY MATERIAL MASTER

MB1C MAINTAIN STOCK

MMPI INITIALISE PERIOD FOR MASTER MATERIAL RECORDFROM CO CODE

MMBE CREATE STOCK

MM60 MATERIAL LIST

XD01 CREATE CUSTOMER

XD02 MODIFY CUSTOMER

XD03 DISPLAY CUSTOMER

VA01 CREATE ORDER

VA02 CHANGE ORDER

VA03 DISPLAY ORDER

VA11 CREATE INQUIRY

VA12 CHANGE INQUIRY

VA13 DISPLAY INQUIRY

VA21 CREATE QUOTATION

VA22 CHANGE QUOTATION

VA23 DISPLAY QUOTATION

VD02 CHANGE SALES PROSPECT

VD03 DISPLAY SALES PROSPECT

VD04 DISPLAY CHANGES

VD06 FLAG FOR DELETION

VK11 MAINTAINING PRICING

VK0A ASSIGN G/L ACCOUNT GENERAL

VOK0 PRICING

VOR1 DEF COMMON DIST CHANEL

VOR2 DEF COMMON DIV

VOV6 DEFINE SCHEDULE LINES

VOV8 DEFINE SALES DOC TYPE

VOFA CREATE/OR CHANGE BILLING TYPES CONFIGURATION

V129 DEFINE INCOMPLETENESS SCHEMAS FOR FOREIGN TRADE

V149 ASSIGN INCOMPLETENESS SCHEMAS FOR COUNTRY CODE

CA01 CREATE ROUTING

CA02 EDIT ROUTING

CA03 DISPLAY ROUTING

CS01 CREATE BOM

CS02 CHANGE BOM

CS03 DISPLAY BOM

OVK1 DEFINE TAX DET RULES

OVK3 DEF TAX REL OF MASTER RECORDS CUSTOMER TAXES

OVK4 DEF TAX REL OF MASTER RECORDS MATERIAL TAXES

OVR6 DEF LEGAL STATUSES

OVS9 DEF CUSTOMER GRP

OVRA MAINT STATISTICS GRPS FOR CUSTOMERS

OVRF MAINT STATISTICS GRPS FOR MATERIAL

OVXC ASSIGN SHIIPING POINT TO PLANT

OVX6 ASSIGN PLANT TO S.O AND DIST CHANEL

OVLK DEFINE DELIVERY TYPE

OVSG DEFINE INCOTERMS

OVLH DEFINE ROUTES

OVXM ASSIGN SALES OFF TO SALES AREA

OVXJ ASSIGN SALES GRP TO SALES OFFICE

OMS2 MATERAIL UPDATE

OVLP DEFINE ITEM CATEGORY FOR DELIVERY

OX10 ASSIGN DEL PLANTS FOR TAX DET

O/S2 DEFINE SERIAL NO PROFILE

O/S1 DEFINE CENTRAL CONTROL PARAMETERS FOR SR NO

OBB8 DEFINE TERMS OF PAYMENT

OKKP ACTIVATION OF COMPONENETS

VB01 CREATE REBATE AGGREMENTS

VB02 CHANGE REBATE AGREMENT

VB03 DISPLAY REBATE AGGREMENT

VB31 CREATE PROMOTION

VB32 CHANGE PROMOTION

VB33 DISPLAY PROMOTION

VB21 CREATE SALES DEAL

VB22 CHANGE SALES DEAL

VB23 DISPLAY SALES DEAL

VB25 LIST OF SALES DEAL

VB35 PROMOTION LIST

VKA4 CREATE ARCHIVE ADMINISTRATION

VKA5 DEL ARCHIVE ADMINISTRATION

VKA6 RELOAD ARCHIVE ADMINISTRATION

VC/1 CUSTOMER LIST

VC/2 CREATE SALES SUMMARY

VDH2 DISPLAY CUSTOMER HIERARCHY

VF01 CREATE PROFORMA INVOICE

VF02 CHANGE PROFORMAINVOICE

VF03 DISPLAYPROFORMA INVOICE

VF07 DISPLAY FROM ARCHIVE

VF11 CANCEL BILL

VFX3 BLOCKED BILLING DOC

VFRB RETRO BILLING

VF04 MAINTAIN BILL DUE LIST

VF06 BACKGROUND PROCESSING

VF21 CREATE INVOICE LIST

VF22 CHANGE INVOICE LIST

VF23 DISPLAY INVOICE LIST

VF44 MAINT REVENUE LIST

VF45 REVENUE REPORTS

VF46 MAINT CANCELLATION LIST

VF31 ISSUE BILLING DOC

VFP1 SET BILLING DATE

VARR ARCHIVE DOCUMENTS

VL01N CREATE DELIVERY

VL02N TO CHANGE DELIVERY WHICH IS ALREADY CREATED

VL03N DISPLAY DELIVERY

V/08 TO CHANGE CONDITION (PR PROCEDURE)

V/30 DEFINE PRINT PARAMETERS

FD32 SETTING CREDIT LIMIT FOR CUSTOMER

/NSM12 TO REMOVE LOCK ENTRY

SM30

ND59 LIST CUSTOMER MATERIAL INFO

VB0F UPDATE BILL DOC

please reward if useful

keep rockin

vivek

[Former Member]

hello Divya,

ME11 creating the info record of a particular vendor

eg: no of matrail recd no transcation is dome .

ME21N creating purcahse order tcode before we want to purchase we need create a purchase order .

MM01 Material creation when new ,matrail is getting into the creating the details of the material.

VF01 its billing documnet we get some mateials

we need create the billing for those materails.

VT01 its a shipping means delivery document.

Thanks Regards

Santhosh