SAP SD TCodes

COGI Automatic Goods Movements: Error Handling

This transaction is used to correct errors that have resulted from automatic goods movements. Automatic goods movement errors occur, for example, when a production order is being confirmed and components are backflushed from a storage location that does not have the required quantity in inventory. Selection criteria include plant, storage location, material, error date from/ to range, and other relevant inventory document data. The output is an aggregated list of goods movement errors. Once the error has been reviewed and resolved, the inventory movement will be processed.

DGP1 Create Dangerous Goods Master

This transaction is used to create a dangerous good master, which is an extension of the material master. The master record contains information required to carry out automatic checks in the sales and distribution and materials management processes and generate documents required by local regulators. Input an existing material master and the dangerous goods regulation code (in customizing the dangerous goods regulation code contains the mode of transport and validity area, for example, Germany). Enter the master data and save.

DGP2 Change Dangerous Goods Master

Use this transaction to change a dangerous good master previously created using transaction DGP1

DGP3 Display Dangerous Goods Master

Use this transaction to display a dangerous good master previously created using transacionDGP1.

DGR1 Dangerous Goods Master: Display with Descriptions

Use this transaction to display a list of dangerous goods master data from the dangerous goods master data table DGTMD. Input selection includes material, regulation key, and valid from/to date range. The output can be listed by material, mode of transport category, and validity area; all change statuses, which are identified by validity area or change number, can be read at the item level. Display layout can be changed and saved as a default, according to user requirements.

DP91 Resource-Related Billing Request

This transaction is used to create a resource related billing request, which is a special type of billing based on resources consumed by the organization. For example, a consulting company agrees to sell services based on time spent on a sales order. Time is recorded to the sales order and then the customer is billed based on the hours charged to the sales order. This transaction generates the resource-related billing request, which is followed up by an actual billing document. Input the sales order and line items, pricing date, posting date and posting period, and execute

DP93 Resource-Related Billing Request Between Company Codes Sales and Distribution

Use this transaction to create an intercompany billing document for the purposes of billing one company for using the resources of another company code in order to bill an end customer. In this scenario an intercompany sales order is generated for using the resources. Once time and/or expenses are charged to a project, the selling company code can bill the end customer. The next step is to use this transaction to create the intercompany billing request, which is then followed by an intercompany billing document. This in turn facilitates the payment from the selling company code to the company code providing the resources. Input the intercompany sale document, period, fiscal year, and posting to date, choose a sales price and click Enter. On the Sales screen, expand the items and chose the crosscompany line item and then chose Billing Request and click Yes to confirm the billing request creation

DP96 Collective Processing Resource-Related Billing Request

This transaction is used to create a resource related billing request for multiple resource usage postings across multiple sales orders.
Resource-related billing is a special type of billing based on resources consumed by an organization. For example, a consulting company agrees to sell services based on time spent on a sales order. Time is recorded to the sales order and then the customer is billed based on the hours charge to the sales order. This transaction generates a resource related billing request, which is followed by the actual billing document. Input the sales order and line items, pricing date, posting date and posting period and execute.

MCTA Customer Analysis: Selection

This transaction uses the sales information system application to report sales activities. This transaction specifically uses information structure S001 (Customer). An information structure contains characteristics (fields that are reported on) and key figures (results of the report). This transaction has the following standard delivered characteristics: sold-to, sales organization, division, distribution
channel and material. The standard delivered key figures include, for example, sales order values and quantity, open sales order values, sales order cost, returns order values, billing values and sales order subtotal values. Input customer, sales area and posting period from/to range, and execute. Multiple display functions are available, including the ability to switch the drill order, the characteristic
key and value display, and key figures related to top % values.

MCTC Material Analysis (SIS): Selection

This transaction is similar to transaction MCTA but focuses on the material characteristic and uses information structure S004 (Material). An information structure contains characteristics (fields that are reported on) and key figures (results of the report). This transaction has the following standard delivered characteristics: material, sales organization, division and distribution channel. The key figures include, for example, sales order values and quantity, open sales order values, sales order cost, returns order values, billing values and sales order subtotal values. Input customer, sales area, posting period
from/to range, and execute. Multiple display functions are available including the ability to switch drill-down order, the characteristic key and value display, and key figures related to top % values.

MCTE Sales Organization Analysis:Selection

This transaction is similar to transaction MCTA but focuses on the sales organization characteristic and uses information structure S003 (Sales Organization). An information structure contains characteristics (fields that are reported on) and key figures (results of the report). This transaction has the following standard delivered characteristics: sales organization, division, distribution channel and sales district. The key figures include, for example, sales order values and quantity, open sales order values, sales order cost, returns order values, billing values and sales order subtotal values. Input customer, sales area and posting period from/to range, and execute. Multiple display functions are available, including the ability to switch drill-down order, the characteristic key and value display, and key figures related to top % values.

TK11 Create Condition Records Shipment Costs

This transaction is used to maintain pricing condition records for shipment costs that access pricing information automatically when creating a shipment cost document via transaction VI01. Input a condition type, for example FB00, and click Enter. Next select the condition table to be maintained (each condition type will be customized with an access sequence and condition tables with the condition fields) and click Enter. In order to calculate freight costs based on scales, you also need to assign the scale to the freight condition type in customizing (transaction T_06). Maintain the condition record fields, rate, unit of measure and valid from/to fields, and save.

TK12 Change Condition Records Shipment Costs

Use this transaction to change pricing condition records for shipment costs, which may be required if you need to change the rate, extend the valid to date, or place a deletion indicator on the condition record. Input the
condition type, click Enter, select the condition table that contains the condition fields (note that in customizing you do have some flexibility as to changing some of the required fields for the purposes of maintenance, which can be useful if you want the change multiple condition records at the same time) and click Execute. Then maintain the condition record and click Save.

TK13 Display Condition Records Shipment Costs

Use this transaction to display a condition record previously created using transaction TK11.

V.1 Incomplete SD Documents

Use this transaction to list all sales documents that are incomplete according to the incomplete procedure assigned to the sales document header or line item. Check the box for the document type(s) selected, the status code, sales area information, and execute. The output will list the incomplete documents with the follow-on documents affected and provide the ability to select the document, complete the missing data, and save the document

V.2 Incomplete SD Documents (Incomplete Orders)

This transaction is used in the same way as transaction V.01 except the default field selection for the SD transaction group is “0,” which meansthat all incomplete sales orders will be selected.

V.3 Incomplete SD Documents (SalesInquiry)

This transaction is used in the same way as transaction V.01 except the default field selection for the SD transaction group is “1,” which meansthat all incomplete sales inquiries will be selected.

V.4 Incomplete SD Documents (Sales Quotation)

This transaction is used in the same way as transaction V.01 except the default field selection for the SD transaction group is “2,” which means that all incomplete sales quotations will be selected.

V.14 Sales Orders/Contracts Blocked for Delivery

Use this transaction to report all sales order/ contracts blocked for delivery according to the delivery block indicator. Note: The values are determined from the confirmed quantities of the order items. Also note, by selecting the new data selection indicator, the program reads the whole database and so if there is a large data set being processed it is recommended not to select this indicator. Therefore, it is recommended that you save the output. Selection criteria include delivery block indicator and sales area. The display variant can be changed, saved, and used as a default at run time.

V.15 Backorders

This transaction is used for backorder processing, where you can list the materialsthat are on backorder and confirm them manually using available to promise inventory quantities. Input your selection criteria (for example, the plant, sold-to party, purchase order number) and click Execute. The output displays your list of sales order line items and materials. Then you can branch to the sales order change function. To process the backorder from the list, select your line item and select Edit • Backorder, select the MRP element, and click Edit • Change Confirmation. Then in the Sales Requirementssection, you can distribute available to promise quantities or redistribute confirmed quantities.

V.21 Log of Collective Run

Use this transaction to review a log of the billing collective run, which is generated by collective run transactions such as billing run via transaction VF04 or delivery run via transaction VL10. Selection criteria include the number of the collective run, the type of collective run (e.g., billing, delivery, etc.) and the user ID that started the run. The output shows the documents created and/or any errors that occurred during the collective run.

V.23 Release Sales Orders for Billing

This transaction is used to release any blocked orders for billing document processing. Note that if you select the confirmation prompt parameter, a dialog box appears for each order, so when you confirm again, the document should be released. Selection criteria include customer, sales order number range, sales area information, user ID that created the document, and creation date range.

V_17 Create Condition Record Using Index

This transaction is used to create condition records using an index which is an aid to condition record updates. An index is set up by selecting fields that are relevant to the index and then flagging a condition type (in customizing) as relevant to condition index update. Once this has been set up, you can use this transaction to create new condition records via the index. For example, you create from/to, delivering plant,sales organization, distribution channel and customer.

V_NL Create Net Price List

Use this transaction to create a net price list based on the pricing conditions already maintained in the system. Selection criteria include sales area information, sold-to party, plant, material from/to range, order
type, billing type, item category, and pricing date (note that the only optional field is the material number). Input required fields and click Execute to display the list of materials net price calculation. The display format can be changed and saved to include subtotal amounts, unit quantity, customer groups, and many more fields commonly used in net pricing calculation.

V_R2 Rescheduling of Sales and Stock Transfer Documents: Evaluation

This transaction is used to evaluate the list of rescheduled sales and stock transfer documents generated via transaction V_V2. A list of changed documents and documents in which an error occurred during processing are displayed. If, in the subsequent evaluation, a restricted selection is carried out, a note appears at the end of the list saying that not all document line items are displayed. You can set the scope of the list under the menu option List in the list display. You can view improvements, deteriorations, and the entire list. Before the documents can be included in one or either of the restricted lists, the date or
quantity has to have changed so that the item can be contained in both the list of improved or deteriorated documents. Selection criteria include material from/to range, plant, sales orders and/or stock transport orders range from/to, delivering plant,sales organization, distribution channel and customer.

V_UC Selection of Incomplete SD Documents

Use this transaction to list all sales documents that are incomplete according to the incomplete procedure assigned to the sales document header or line item. Check the box for the document type(s) selected and other selection criteria, for example, status code, sales area information, overall document status code, sales document from/to, and execute. The output will list incomplete documents with the follow-on document affected and provide the ability to select the document, complete the missing data, and save the document

V_V2 Rescheduling of Sales and Stock Transfer Documents: by Material

This transaction is used to reschedule open sales and stock transfer documents. A checking rule is used as a basis for the check, for example, check delivery schedules. Line items are sorted into priorities, delivery priority, schedule line date, etc. The rescheduling can be run in simulation mode or in update mode, which means the program changes the confirmation/delivery date. Line items are read and quantities are transferred to availability to promise checking, and delivery dates can be rescheduled and saved in a log. Input material from/to range, plant, sales order and/or stock transport order and list sorting requirements and execute. Results showing old new delivery scheduled date are displayed and can be saved. Note: due to system performance concerns, you should narrow selection criteria as much as possible.

V/I5 Change Condition Record Using Index

This transaction is used to change condition records using an index. An index is set up by selecting fields that are relevant to the index and then flagging a condition type (in customizing) as relevant to condition index update. Once this has been set up, you can use this transaction to change c
ondition records via the index. For example, you can change price and discount conditions for all materials within a material group. Select the table that contains the index fields, input selection criteria, click Execute Change, input condition record values, and save.

V/I6 Display Condition Record Using Index

Use this transaction to display condition records via an index. An index is set up by selecting fields that are relevant to the index and then flagging a condition type (in customizing) as relevant to condition index update. For example, you can display all price and discount conditions for materials within a material group. Select the table that contains the index fields, input selection criteria, and click Execute to display the list of condition records.

V/LD Execute Pricing Report

This transaction is used to display a list of pricing records based on a pricing report table set up in customizing. In customizing, select the key fields and condition tables that contain the selected fields and save the report table under a two-character ID. In this transaction, input the two-character ID of the reporting table and click Execute. On the next screen, input the selection criteria from the selected fields and execute to display the pricing report.

VA01 Create Sales Order

This transaction is used to set up a contractual agreement between your sales organization (typically aligned with a company code) and a sold-to party (the customer/business partner you have the agreement with). A sales order can be sub divided into a distribution channel and/or division, which, together with the sales organization, combine to make up the sales area. The sales area will determine some of the master data that will be used on the sales order. Various sales order types come standard with the system, including a regular order, cash sale, return order, debit/credit memo requests, etc. The sales order
has functionality to determine pricing for materials being sold, as well as availability and shipping date. Furthermore, the sales order is integrated with manufacturing and purchasing in order to plan fulfillment of the sales order requirements. Furthermore, the sales order is integrated with the finance module and credit management, checking, for example, whether the customer’s sales order value is within their credit limit. The sales order is split into header information and line item information. Input the sales order type, sales area, click Enter and then select customer/business partners, materials/services to be sold, requested delivery date and pricing information, and save.

VA02 Change Sales Order

Use this transaction to change a sales order, such as adding or deleting items. Input the sales order number and click Enter. If you need to make changes to multiple items, the Fast Change function can be used via the menu path Edit • Fast Change of. The Fast Change function can change data such as the plant, delivery block indicator and the reason for rejection status change. Other functions, such as executing the available to promise check and updating pricing details, can also be performed.

VA03 Display Sales Order

This transaction is used to display a sales created using transaction VA01.

VA05 List of Sales Orders

Use this transaction to list sales orders using a material or business partner as one of the selection criteria. You can select just the sales orders that you created, all open sales orders, or all orders within a date created range. Various output display options are available, which can be saved and used as a default. Note that a special authorization parameter ID is required in your user profile in order to make and save changes to the display layout.

VA07 Selection: Comparison of Orders with Purchase Requisitions and Purchase Orders

This transaction is used to report on inconsistencies between the sales order quantity and the purchase order quantity in a third party order sales process. Selection includes sales order and deviation category. For example, if a sales order is created for 20 ea and the purchase requisition/purchase order that was subsequently created from the sales order was changed to 30 ea, this report would highlight the difference. It also offers the ability to drill down on the documents to facilitate changing the quantity. Other deviation categories are also available

VA08 Adjustment Sales Purchasing (Selection Using Organizational Data)

This transaction is used to report on inconsistencies between the sales order quantity and the purchase order quantity in a third party order sales process. Selection includes sales organization, sales office, sales group and deviation category. For example, if a sales order is created for 20 ea and the purchase requisition/purchase order that was subsequently created from the sales order was changed to 30 ea, this report would highlight the difference. It also offers the ability to drill down on the documents to facilitate changing the quantity. Other deviation categories are also available. It is recommended to use transaction VA08 in background mode for large amounts of data.

VA11 Create Inquiry

This transaction is used to record an inquiry as part of the pre sales process. Functionality similar to the Sales Order Create function is also available to the Inquiry Create function, such as pricing information and delivery date scheduling. A sales inquiry is entered by sales area, which includes the sales organization, distribution channel and division. Also input an inquiry type, such as an available stock inquiry or price list inquiry, and click Enter. Within the inquiry function, the customer can be informed of available stock on hand, the shipping date timeline, and the price of materials. By saving the inquiry, reports can
be created such as an analysis of the number of inquires that have been converted to sales orders or materials that customers are most interested in. Input the inquiry type, sales area, click Enter, and then select customer/business partners, materials/services to be sold, requested delivery date and pricing information, and save.

VA12 Change Inquiry

Use this transaction to change an inquiry previously created using transaction VA11.

VA13 Display Inquiry

Use this transaction to display an inquiry previously created using transaction VA11.

VA14L Sales Documents BlockedforDelivery

This transaction is used to review any sales documents that have been blocked for delivery. Sales documents may be blocked for delivery if they are on credit hold where a customer has exceeded their credit limit. Selection optionsinclude the customer, sales area (sales organization, distribution channel and division), all sales documents, or only sales documents that are open. The report output displays sales document number and category, sold-to and ship-to customer number, and the various blocks that can exist. There is an option to change the layout and drill-down capability into the sales document in order to facilitate delivery dates change, remove manual blocks, etc.

VA15 List of Inquiries

Use this transaction to list sales inquiries using a material or business partner as one of the selection criteria. You can select just the sales inquiries that you created, all open inquiries, or all inquiries within a date created range. Various output display options are available, which can be saved and used as a default. Note: a special authorization parameter ID is required in your user profile in order to make and save changes to the display layout.

VA21 Create Quotation

This transaction is used to create a document that is a legally binding offer for a material or provision of service according to some fixed terms. Functionality similar to the Sales Order Create function is also available to the Quotation Create function, such as pricing information and delivery date scheduling. A sales area (sales organization, distribution channel and division) is required and the quotation can be
created in reference to a customer inquiry. Typically, the quotation has a specified valid from/to date. Input the quotation type (e.g., in reference to an inquiry or marketing activity), sales area information, click Enter, then select the customer/ business partners, materials/services to be sold, requested delivery date(s) and pricing information, and save

VA22 Change Quotation

Use this transaction to change a quotation previously created using transaction VA21.

VA23 Display Quotation 

Use this transaction to display a quotation previously created using transaction VA21.

VA25 List of Quotations

Use this transaction to list quotations using a material or business partner as one of the selection criteria. You can selectjustthe quotations that you created, all open quotations, or all quotations within a date created range. Various output display options are available, which can be saved and used as a default. Note: a special authorization parameter ID is required in your user profile in order to make and save changes to the display layout

VA26 List of Quotations (Follow-up Actions)

This transaction is used to display a list of open quotations for a particular sold-to party up to a valid to date. Furthermore, a document date from/to can also be selected in order to narrow the output list. After the list is displayed, quotations can then be processed and converted into sales orders.

VA31 Create Scheduling Agreement

This transaction is used to create an agreement with a customer to deliver materials with specific delivery quantities and dates which are created in a delivery schedule. Scheduling agreements are integrated with production planning so that material components/production can be appropriately scheduled in order to fulfill agreed upon delivery dates. Input the agreement type, for example, a just-in-time scheduling agreement, sales area information, and click Enter. Input the business partner data, the materials to be delivered, and the forecast or fixed delivery dates, and save.

VA32 Change Scheduling Agreement

Use this transaction to change the scheduling agreement, perhaps as a result of the customer informing you that the delivery dates require changing. Scheduling agreements can be integrated with EDI functionality whereby the customer can send forecast delivery dates for production planning purposes and then send follow-up notices of firm delivery dates.

VA33 Display Scheduling Agreement

Use this transaction to display a scheduling agreement previously created using transaction VA31.

VA35 List of Scheduling Agreements

Use this transaction to display a list of scheduling agreements using a material or business partner as one of the selection criteria. You can select just the scheduling agreements that you created, all open scheduling agreements, or all scheduling agreements within a date created range. Various output display options are available, which can be saved and used as a default. Note: a special authorization parameter ID is required in your user profile in order to make and save changes to the display layout.

VA41 Create Contract

This transaction is used to create a contract with your business partner. There are various types of contract, namely a master contract or a value, quantity, and service contract. A master contract will contain general terms such as a master agreement number, perhaps special payment terms, and it offers a way to group follow-on contracts for reporting purposes. A value, quantity and service contract will contain information about the material/service quantities and pricing, and it will facilitate copying information into released sales orders where delivery dates and prices can be finalized. Contracts are valid for a specified time period. Input the contract type, sales area information and click Enter. Then input business partner information, valid from/to dates, material/service materials, quantities/values, and save.

VA42 Change Contract

Use this transaction to change a contract previously created using transaction VA41. Note that any changes to contracts, as with most other master data and transactional documents, are logged in a change document that can be viewed within the contract document via the menu path Environment/Changes.

VA42W Change Contract

This transaction is the same as transaction VA42 but is used in conjunction with workflow functionality for the completion and approval of a master contract setup.

VA43 Change Contract

Use this transaction to display a contract previously created using transaction VA41.

VA44 Actual Overhead: Calculation: Sales Order

This transaction is used to calculate overhead on sales order costs as part of cost object controlling functionality for sales orders. An overhead costing sheet can be assigned directly in the sales order, in the Account Assignment tab, or derived via customizing to facilitate the overhead calculation. Note: As with valuated sales orderstock, overhead is allocated to the cost element for the cost ofsales calculation. But with a non-valuated sales order stock, overhead is allocated when the consumption cost elements are posted or to the cost elements upon the inventory movement posting when the materials are consumed.

VA45 List of Contracts

Use this transaction to display a list of contracts using a material or business partner as one of the selection criteria. You can select just the contracts that you created, all open contracts, or all contracts within a date created range. Various output display options are available, which can be saved and used as a default. Note: A special authorization parameter ID is required in your user profile in order to make and save changes to the display layout.

VA46 List of Contracts (Follow-up Actions)

This transaction is used to display a list of open contracts for a particular sold-to party up to a valid to date. Furthermore, a subsequent process valid to date can also be selected in order to narrow the output list. After the list is displayed, contracts can be processed and converted into released sales orders.

VA51 Create Item Proposal

This transaction is used to create a proposed list of materials that can be stored and easily retrieved at sales order processing time. For example, if a customer typically orders the same list of materials, this list of materials can be stored in an item proposal document and then, at sales order processing time, the list of materials can be retrieved via the menu path Edit • Additional functions • Propose Items. Input the proposal list type, sales area information, description of the list, valid from/to date, materials to be proposed, and save the document

VA52 Change Item Proposal

Use this transaction to change an item proposal previously created using transaction VA51.

VA53 Display Item Proposal

Use this transaction to display an item proposal previously created using transaction VA51.

VA55 List of Item Proposals

Use this transaction to list item proposals using the material number as the selection criteria. You can select just the item proposals that you created or all item proposals within a date created range or valid from/ to range. Various output display options are available, which can be changed,saved, and used as a default. Note: A special authorization parameter ID is required in your user profile in order to make and save changes to the display layout.

VA88 Actual Settlement: Sales Orders

Use this transaction to settle actual primary and secondary costs and revenues (if applicable) to the receivers established in the sales order line item (which is a cost object) settlement rules. In cost object controlling for sales orders, the sales order is an interim cost collector that can be used to plan, record actual costs, and monitor costs until certain activities have been completed and costs moved to their final destination. This movement of the costs to their final des
tination is called settlement. The sales ordersettlement rules are dependent on the parameters established in the settlement structure, settlement
profile, and order type (all defined in customizing and in the master data itself).

VACF Fiscal Year Close: Carry Forward Commitment

This transaction is used to carry forward commitments values, in this case open sales orders posted in the current year but not reduced until the following year. The commitment carried forward updates the budget in the new fiscal year. Input the sale order number range, the carry forward from fiscal year, and execute in test or update mode.

VB01 Create Listing/Exclusion

This transaction is used to control the materials you sell to your customers. In other words, you create a material listing for a particular customer and only sell materials to that customer that are on the list. Furthermore, you can create a material exclusion that prevents a customer from buying particular materials. The listing/exclusion functionality utilizes the condition technique to accommodate this
process. Input the listing/exclusion type, make the table entries, such as the selected materials, and save.

VB02 Change Listing/Exclusion

Use this transaction to change a material listing/exclusion previously created using transaction VB01.

VB03 Display Listing/Exclusion

Use this transaction to display a material listing/exclusion previously created using transaction VB01.

VB11 Create Material Determination

This transaction is used to determine materials based on some predefined conditions. For example, a material that has been replaced by a new material can be automatically substituted, using material determination during sales order input. Another typical use for this functionality involves using the customer’s material number to automatically determine SAP’s system-generated material number. The
material determination functionality utilizes the condition technique to accommodate this process. Input the material determination type, valid from/to date range and the relevant condition entries, and save.

VB12 Change Material Determination

Use this transaction to change a material determination condition previously created using transaction VB11. This transaction is typically used when the valid from/to date range has expired and needs extending.

VB13 Display Material Determination

Use this transaction to display a material determination condition previously created using transactionVB11

VB21 Create Sales Deal

This transaction is used to create master data for a sales deal, which includes general data and associated pricing information,such as a flat rate discount or volume-related discount. A sales deal can be created in reference to a promotion (created using transactionVB31), in which case the payment terms can also be defaulted into the sales deal. Input the agreement type, click Enter, and enter general data such as the valid from/to date range and description of the deal. Complete the master data by clicking the Condition Record icon to input the pricing/discount information, for example, a discount on a product line or
individual materials. This condition will now be shown in the sales order if that product line or material is being sold.

VB22 Change Sales Deal

Use this transaction to change a sales deal previously created using transaction VB21. This transaction may be used, for example, if the sales deal needs to be discontinued prematurely, which can be accomplished by changing the valid to date.

VB23 Display Sales Deal

Use this transaction to display a sales deal previously created using transaction VB21.

VB25 List of Sales Deals

This transaction is used to display a list of sales deals using the following selection criteria:sales deal number, sales deal description, valid from/to date range, assigned promotion, and sales area information. The output display can be changed and used as a default to suit user requirements.

VB31 Create Promotion

This transaction is used to create a promotion, which can represent a broad marketing plan used to connect multiple sales deals (created using transaction VB21). Sales deals can be created in reference to a promotion, which facilitates the link to the promotion. Further more, the promotion contains payment terms and valid from/to dates which, by default, contain the information from the sales deal. Input the agreement type, click Enter, and input the description. Then enter the payment terms, valid from/to date range and internal comment, if required, and save.

VB32 Change Promotion

Use this transaction to change a promotion previously created using transaction VB31. This transaction may be used, for example, if the promotion needs to be discontinued prematurely, which can be accomplished by changing the valid to date.

VB33 Display Promotion

Use this transaction to display a promotion previously created using transaction VB31.

VB35 Promotions List

This transaction is used to display a list of promotions using the following selection criteria: promotion number, promotion description, validity from/to date range, and sales area information. The output display can be changed and used as a default to suit user requirements.

VB41 Create Cross-Selling

This transaction is used to create a master data link for materials that are frequently sold together. This information is commonly used in mail order sales scenarios wherein a customer calls to order a material and once the material is entered into the sales order, a dialog box appears enabling the order entry clerk to suggest an additional material the customer might consider buying. Input the material determination type, click Enter, select a condition type, click Enter, enter a valid from/to date range, and then enter the materials sold/to be suggested. Note: to get a sales analysis of materials that are frequently sold together, you can use report program SDCRSL01

VB42 Change Cross-Selling

Use this transaction to change the material determination master data previously created using transaction VB41.

VB43 Display Cross-Selling

Use this transaction to display the material determination master data previously created using transactionVB41.

VBN1 Create Free Goods Determination

This transaction is used to create master data to determine free goods during sales document processing. Free goods are those that the customer does not pay for and may be one of two types: inclusive (the free goods are within the same line on the sales order) or exclusive (a separate line on the sales document is created where the free material does not have to take the same material number as the original material ordered). The condition technique is used to facilitate this functionality. Input the condition type (which may be by material, customer/material etc.), click Enter, select the key combination, materials etc., the valid from/to date range of the condition, and save. The free goods will now be selected during sales document processing if the condition is fulfilled.

VBN2 Change Free Goods Determination

Use this transaction to change a free goods condition record previously created using transaction VBN1. This transaction may be used, for example, if the free good deal needs to be discontinued prematurely, which can be accomplished by changing the valid to date.

VBN3 Display Free Goods Determination

Use this transaction to display the free goods condition record previously created using transaction VBN1.

VBO1 Create Rebate Agreement

This transaction is used to create a special type of agreement/discount with the customer involving the settlement of a discount/rebate retroactively. An agreement for a rebate is entered into with the customer or another rebate recipient, and rebate volume/accrual amounts are recorded as sales document/ deliveries are processed. Then, on a one-time or periodic bas
is, the rebate amount is settled
by creating a rebate request and rebate settlement document. The rebate agreement has header data and uses the condition technique to accrue for the rebate amount and capture the rebate volume. Input the agreement type, click Enter, enter the valid from/to date range, rebate recipient, description, type of settlement, click the Condition icon and then enter the condition records that will be called during sales document processing and save.

VBO2 Change Rebate Agreement

Use this transaction to change a rebate agreement previously created using transaction VBO1. This transaction is also used to perform the following functions: change the rebate amount or validity date range, perform settlement and report on previous settlement amounts and rebate volume.

VBO3 Display Rebate Agreement

Use this transaction to display a rebate agreement previously created using transaction VBO1. This transaction can be used to report on previous settlement amounts and rebate volume.

VBOF Update Billing Documents

This transaction is used to update billing documents for rebate conditions that have been created with a valid date in the past or pricing condition changes that will affect billing documents already created. The program updates the billing document pricing procedure for changes to rebate conditions and then posts an accrual if required. Selection criteria include rebate agreement number, rebate recipient, validity end date before, sales area information and posting date. The program can be run in test or update mode

VC/2 Sales Summary

Use this report to prepare for sales activities. The report is split into a header and main section. The header contains a View Field icon, which allows you to group the information you require and an Information Block field, which enables you to go directly to the information block you require. The main body of the report contains blocks of information, such as the customer address, partner contacts, sales volume/key figures, credit information, promotional agreements, and any payment card information.

VC01N Create Sales Activity

Use this transaction to record sales activities you engage in with a customer. Record the sales activity type such as a phone call,sales letter, etc., date and time from/to the activity took place, company information, contact person and description of the activity. The screen can be customized by sales activity type to suit business requirements. Sales information can be displayed and you can branch to the address data of the customer. Follow-on activities can also be created,such as a sales letter to follow up on a phone call or sales order processing.

VCC1 Payment Cards: Worklist

This transaction lists all sales orders and deliveries with payment cards. The report selection criteria include sales area information, sales document and various status indicators, such as the sales document’s
overall status and credit hold status. The output display enables you to process a sales document, release documents and carry out authorizations.

VD01 Customer Create (Sales)

This transaction is used to create the customer master record sales and distribution views, which are stored at the sales area level. The customer master sales and distribution view contains data relevant to sales, shipping, billing and business partner determination functionality. Customer master data fields that are either optional or required fields, as determined by the account group, can be maintained. All business partners, such as sold-to, ship-to, payer and bill-to, can be created using this transaction code. Input the customer master sales area information and the customer master number if the General Data views have already been maintained; if not, leave blank and the General Data will need input also. Then click Enter. Input relevant customer master data and save. Note that there is a comparison report via transaction F.2D that displays customer master records that have not been created in finance or sales and distribution to ensure that all data have been set up in the relevant modules.

VD02 Customer Change (Sales)

This transaction is used to change any of the customer master record views in the General or Sales Area Data views. Customer master data fields that are either optional or required, as determined by the account group, are available to change. All business partners, such as sold-to, ship-to, payer and bill-to, can be changed using this transaction. Note that there is a change log on the customer master that can be accessed within the customer master via menu path Environment • Account Changes in order to review changes by user ID, date and old/ new values

VD03 Customer Display (Sales)

This transaction is used to display the customer master record views at the general and/ or sales area level. All business partners, such as sold-to, ship-to, payer and bill-to, can be displayed using this transaction.

VD04 Customer Account Changes

Use this transaction to report all changes to the customer master. The report is organized by customer and sales area. There is an option to select a specific date, time, and user ID of the individual making the change. The report output will display the fields changed, with the option to drill down and display the old/ new field value and date changed

VD05 Customer Block/Unblock

This transaction is used to block the customer master from various transactions, such as sales order processing, financial postings, etc.

VD06 Customer Flag for Deletion

Use this transaction to flag a customer master for deletion. The deletion flag can be set by sales area or all sales areas. Furthermore, the deletion flag can be set at the general area level and general area level including selected sales areas. The deletion flag will ensure that the customer cannot be used in transactional processing and can be included in the archiving process.

VD51 Create Customer Material Info Record

This transaction is used to stored customer specific material master data, such as the customer’s material number and description. Furthermore, customer-specific data on deliveries and delivery tolerances can also be stored. This data can be used during sales order entry whereby if you input the customer’s material number, your company’s material number will be pulled into the sales order. Also, during EDI incoming sales order processing, your company’s material number can be derived from this master data

VD52 Selection of Customer-Material Info Records (Change)

Use this transaction to change a customer’s material info record previously created using transaction VD51. This may be required if, for example, more materials need to be added.

VD53 Selection of Customer-Material Info Records (Display)

Use this transaction to display a customer’s material info record previously created using transaction VD51

VD59 List Customer-Material Info

Use this transaction to display a list of customer-material info records. Input selection criteria include sales organization, your company’s material number, the customer’s material number, and the customer number. Display variants can be created, saved, and used as a default.

VDH1N Edit Customer Hierarchy

This transaction is used to create and change levels on a customer hierarchy, which is used to reflect the structure of a customer organization. For example, a customer may have several buying companies that all receive the same pricing/discounts: you can maintain this hierarchical structure and maintain pricing records at that higher level. The same hierarchy can be used for rebate processing and profitability analysis. Input the hierarchy type (which controls how the hierarchy is used, for example, pricing, account groups and organizational data restrictions), the customer or customer number range, sales area
information and execute. On the next screen, highlight the customer and click the C
reate button or the Change button to maintain the hierarchy assignment in the right-hand window pane and save.

VDH2 Display Customer Hierarchy

Use this transaction to display a customer hierarchy previously created using transaction VDH1N.

VF01 Create Billing Document

This transaction is used to processthe billing document, which represents the final step in the sales and distribution ordering cycle. This transaction is used to process an individual billing document; however, transaction VF04 is used to process multiple billing documents. Billing document types, including invoices, credit memos, cancellations, rebate settlements and pro forma invoices, are typically defaulted from the previous document type/copy control settings in customizing. The billing document is fully integrated with the financial module and, upon posting, creates financial postings to the general ledger and
management reporting modules (if required). Input the billing type (if needed) and billing date (current date is defaulted) and then input the reference document, which could be a delivery document,sales order(if non-delivery relevant) or rebate settlement request, and click Enter. The billing information can be reviewed before saving.

VF02 Change Billing Document

Use this transaction to change a billing document, which may be required, for example, if the billing document had not been processed in the financial modules because perhaps the posting period had been incorrectly closed. In this case, you need to reopen the accounting period and, using this transaction, input the billing document number, click Enter, and save the document, which will ensure that the accounting documents have been created.

VF03 Display Billing Document

Use this transaction to display the billing document previously created using transaction VF01 or VF04. From the display function, you can click the Accounting Document icon in order to drill down into the general ledger or management financial postings.

VF04 Maintain Billing Due List

This transaction is used to process multiple billing documents at one time. Selection is by billing date, reference document or sales area. You can change the default data, proposed by copy control, by clicking the Default Settings tab and selecting a different billing type or billing date. Document selection enables the choice of sales process you want to bill, such as order-related or delivery-related billing. After executing the program and before you create the billing documents, you have the option to bill individually for each reference document or perform collective billing, where the system tries to combine billing
documents as much as possible, by sold-to, payment terms, etc.

VF05 List of Billing Documents

Use this transaction to list billing documents using a material or business partner, typically payer, as one of the selection criteria. You can select all open billing documents or all billing documents within a date created range. Various output display options are available, which can be saved and used as default. Note: A special authorization parameter ID is required in your user profile in order to make and save changes to the display layouts.

VF11 Cancel Billing Document

This transaction is used to cancel a billing document, which may be required if, for example, there was an error in posting to the incorrect customer account in finance. An additional cancellation billing document is created reversing the accounting entries, allowing the corrections to be made to the reference document and allowing for the recreation of the billing document. Input the billing document number and save. The cancellation will also be displayed in the document flow.

VF21 Create Invoice List

This transaction is used to create invoice lists, at specified time intervals or on specific dates, in order to send to a particular payer business partner. This may be required where a central payer collects and pays invoices for a group of companies. Typically, the group payer pays the invoices and in return for this service earns a factoring discount. Note that there are a number of prerequisites to enabling this functionality that must be set up in customizing, such as a special condition type for the factoring discount, use of special billing document type, customer calendar setting (in the customer master), etc. Input the billing documents individually or via a work list and save your selection.

VF22 Change Invoice List

Use this transaction to change an invoice list, for example, if one of the billing documents had been incorrectly input into the list. Input the invoice list number, remove the billing document, and save the list.

VF23 Display Invoice List

Use this transaction to display an invoice list previously created using transaction VF21.

VF25 List of Invoice Lists

Use this transaction to list invoice lists using the business partner payer. You can select all open invoice lists or all invoice lists within a date created range. Various output display options are available, which can be saved and used as a default.

VF26 Cancel Invoice List

Use this transaction to cancel invoice lists, which reverses financial postings and renders the billing documents available for posting again

VF31 Output from Billing

This transaction is used to process the billing output as a separate step from the billing document creation function. Input the output type (which is the billing document layout form), the transmission medium (e.g., printout or fax), the sort order in which the output is created and printed, and the processing mode (e.g., whether this is the first billing output or repeat output). In addition, the billing document range, billing date, reference type document and sales area information can be selected before you click Execute.

VF43 Posting Documents for Revenues

Use this transaction to report on revenue recognition postings for an individual sales order or accounting document, which is useful if document summarization is active since it is not possible to retrace the postings by sales order line item from the accounting document. The revenue posting document can also be found by looking at the document flow and also by drilling back to the original document from the accounting document. Selection criteria include sales documents or the Accounting Document radio buttons and the document number. The display offers the ability to navigate to postings at the line
item level and then to the revenue accounts with the revenue update status. Click the All Revenue Posting icon to display all postings for a collective run. Drill-down capability is available to view the sales order and followon documents

VF44 Edit Revenue List

This transaction is used to recognize revenue separately from the standard billing document, once the process is initialized (depending on the revenue recognition method). Revenue recognition functionality
is activated by item category in customizing. Sales order line items with an item category activated for revenue recognition will control when revenue is recognized as opposed to recognizing revenue when invoicing the customer (which is the standard SAP process). Input the company code, sales document number range (if required), the posting period/fiscal year, posting date, and execute. The output displays the revenue recognition relevant line items from which you can select the lines and process the financial posting documents individually or collectively

VF45 Revenue Report

Use this transaction to report on revenue recognition postings for multiple sales orders. The revenue posting document can also be found by looking at the document flow and by drilling back to the original document from the accounting document. Selection criteria include sales and distribution documents or the Accounting Document radio button and the document number. The display list offers the ability to navigate to postings at the line
item level and then to the revenue accounts with the revenue update status. Click the All Revenue Postings icon to display all postings for a collective run. Drill-down capability
is available to view the sales order and the follow-on documents.

VF46 Maintain Cancellation List

Use this transaction to cancel any revenue recognition postings incorrectly generated from transaction VF44. This transaction reverses the original financial postings, marks both the original line and the reversed line with a cancellation indicator in the revenue recognition tables, and creates new lines ready for use again with transaction VF44.

VF47 Revenue Recognition;

Inconsistency Check in Revenue Table Use this transaction as the main tool in the analysis of the revenue recognition data from a technical view of the revenue recognition tables. Sales orders may contain errors, which can cause inconsistencies in the revenue recognition tables (VBREVK, VBREVE and VBREVR). Selection criteria include company code,sales document range, number of lines to read (to improve performance) and types of checks (for example, checking control lines in the revenue recognition tables and whether the control lines have errors). The report can be executed in test mode (which is recommended until errors are analyzed) and update mode.

VF48 Compare Report

This transaction is used to compare finance and sales and distribution balances on the accrual accounts (i.e., deferred revenue and unbilled revenue). The program looks at the account balance in finance and compares this to the balance in the revenue recognition tables (VBREVE and VBREVR) for selected periods. This report simply compares balances; to determine the reasons for any issues, VF47 can be used. Selection criteria include the company code, an individual accrual account, posting period, and fiscal year from/to. The executed report provides a header part that shows the balances determined for the selected accrual account and a detail part that provides a work list with sales document line items used when the accrual account was posted via billing or revenue recognition.

VFRB Retro-billing

Use this transaction in a scenario where new pricing has been agreed upon with the customer and is valid for billing documents that have already been processed. You can run this transaction to list the billing documents affected by the new pricing conditions and to create new billing documents for the differences.Input the payer, sales organization, billing date range, execute transaction, and then process the additional invoices.

VFX3 Release Billing Documents for Accounting

This transaction enables the release of billing documents that, for whatever reason, have not been passed to finance for posting. For example, if the financial posting period had been incorrectly closed. Once the posting period has been reopened, you can use this transaction to release the billing document to accounting. Input the payer or payer range, sales organization,select various incomplete posting indicators, and then execute the program

VG01 Create Group

This transaction is used to group delivery documents for collective processing. Input the group type, which determines the type of document that can be processed in this collective manner, i.e., group deliveries that refer to sales order or returns only, and click Enter. On the next screen, enter the documents numbers that are to be grouped and save.

VG02 Change Group

Use this transaction to change a delivery group previously created using transaction VG01.

VG03 Display Group

Use this transaction to display a delivery group previously created using transaction VG01.

VI01 Create Shipment Costs

This transaction is used to create an individual shipment cost document for a shipment or shipment stage. Input the shipment document number, which must have a transportation status of “planned” (defined in customizing) and click Enter. The shipment cost document has header information, such as pricing/settlement date, which will be set to the default value (defined in customizing). The shipment cost document also has line item information, which includes a pricing procedure that calculates costs using the pricing condition technique and settlement data. The shipment cost document also has sub
items that represent the calculation basis for the cost. Upon saving the shipment cost document, costs are automatically calculated and settlement data is assigned and transferred to accounting.

VI02 Change Shipment Costs

Use this transaction to change an individual shipment cost document, which may be required, for example, if further calculation of shipment costs is needed or settlement data need to be assigned. Input the shipment document number, click Enter, make the necessary changes and save.

VI03 Display Shipment Costs

Use this transaction to display a shipment cost document previously created using transaction VI01.

VI04 Shipment List: Create Shipment Costs

Use this transaction to create multiple shipment cost documents at one time. Input selection criteria include service agent, route, shipment document range, status of the shipment document and many attributes of the shipment document. The shipment cost document header information includes pricing date and settlement date, which will default (defined in customizing). The shipment cost document line item information includes a pricing procedure calculating costs using the pricing condition technique and settlement data. The shipment cost document also has sub items that represent the calculation basis for the cost. Upon program execution and list generation, the saved shipment cost document can have the costs automatically calculated, settlement data assigned, and be transferred to accounting.

VI05 List Shipment Costs: Change Worklist

This transaction is used to change shipment cost documents via a worklist. Individual shipment cost documents may require changing, for example, if further calculation of shipment costs is needed or settlement data need to be assigned. Input the shipment document number, click Enter, make the necessary changes and save.

VI07 List Shipment Costs: Change Worklist in Background

This transaction is used to change shipment cost documents via a worklist with background processing. Shipment cost documents may require changing, for example, if further calculation of shipment costs needs updating, and the updates can be performed in background

VI12 List Shipment Costs: Settlement

Use this transaction to settle shipment cost documents that have not been fully calculated, for example, shipment cost documents created with line items with automatically calculated shipment costs. On a periodic basis, this program is executed, and line items are reviewed and batched together for settlement to accounting.

VI16 Logs in the Application Log

Use this transaction to review the log for shipment cost document changes via a worklist in background executed using transaction VI07. The log can be displayed with or without warnings and errors.

VK11 Create Condition Records

This transaction is used to maintain pricing condition records that access pricing information automatically in sales documents. Input a condition type, for example PR00 for price, and click Enter. Next, select the condition table to be maintained (each condition type will be customized with an access sequence and condition tables with the condition fields) and click Enter. Maintain the condition record fields, price, unit of measure and valid from/to fields and save

VK12 Change Condition Records

Use this transaction to change pricing condition records, which may be required if you need to change the price, extend the valid to date, or place a deletion indicator on the condition record. Input the condition type, click Enter, select the condition table that contains the condition fields. (Note: In customizing, you do have some flexibility
as to changing some of the required fields for the purposes of maintenance, which can be useful if you want to change multiple condition records at the same time.) Click Execute. Then maintain the condition record and click Save.

VK13 Display Condition Records

Use this transaction to display a condition record previously created using transaction VK11

VK14 Create Condition Records with Reference

This transaction is used to create pricing condition records with reference to existing pricing condition records. Input the pricing condition type, select the table used for the reference, input the reference pricing condition record, select the option to keep the reference valid from/to date, if required, and execute. On the next screen, enter the new entries at the line item level and save.

VKM1 Blocked SD Documents

This transaction is used to review sales documents, including sales orders and deliveries, that have been blocked via credit control. Customers can be set up with a credit master and with Dynamic Credit Checking turned on at the sale document level, sales documents can be checked for credit control purposes. For example, a sales order placed by customer who has exceeded his or her credit limit can be blocked. After the sales order has been blocked, the customer may settle his or her account receivable and/or the credit department may grant the customer more credit, which means that you can use
this transaction to release the blocked sales order(s). Input the credit control area and credit representative group, credit account (customer) and click Execute. On the next screen, select the blocked sales order, click the Release flag, and save the document.

VKM2 Released SD Documents

Use this transaction to display a list of sales documentsthat have been released via transaction VKM1.

VKM3 Sales Document

This transaction is used to review only sales orders that have been blocked via credit control, as opposed to transaction VKM1, which reviews both sales orders and deliveries. There is also a selection option for the sales order document number. Customers can be set up with a credit master and with Dynamic Credit Checking turned on at the sale document level, sales documents can be checked for credit control purposes. For example, a sales order placed by a customer who has exceeded his or her credit limit can be blocked. After the sales order has been blocked, the customer may settle his or her account receivable and/or the credit department may grant the customer more credit, which means you can use this transaction to release the blocked sales order(s). Input the sales order document number, if known, and
click Execute. On the next screen, select the blocked sales order, click the Release flag, and save the document

VKM4 SD Documents

Use this transaction to review both blocked and released sales documents: this transaction is a combination of transactions VKM1 and VKM2.

VKM5 Deliveries

This transaction is used to review only deliveries that have been blocked via credit control, as opposed to transaction VKM1, which reviews both sales orders and deliveries. There is also a selection option for the
delivery document number. Customers can be set up with a credit master with Dynamic Credit Checking functionality at the sale document level. For example, at delivery time a customer who has overdue accounts receivable and has exceeded his or her credit limit will have any future deliveries blocked for credit control purpose. Subsequently, the customer may settle his or her account receivable and/or the credit department may grant the customer more credit, which means that you can use this transaction to release the blocked deliveries. Input the delivery document, if known, and click Execute. On
the next screen, select the blocked delivery document, click the Release flag, and save the document

VL01N Create Outbound Delivery with OrderReference

This transaction is used to create a delivery document in reference to a single sales document. Delivery documents can serve as the basis for planning material requirements, picking, creating shipping units and billing. A delivery will be issued out of one shipping point. When you create the delivery document, some of the activities that will take place include checking for delivery blocks, calculating weight and volume, checking for any partial delivery requirements on the sales order, redetermining the shipping route, assigning pick locations, and updating the sales order status. Input the shipping point, selection date (this will select all material available on those dates and transportation scheduling up to this date) and click Enter. Review the delivery quantity and default information and click Save.

VL01NO Create Outbound Delivery without Order Reference

Use this transaction to create a delivery document without reference to a sales order, which may be required if sales orders are processed outside of SAP and you want to create a delivery document manually just for printing delivery output. In this scenario, there will be no default information flow from the sales order, so all information will need to be entered manually and there will be no system checks (for example, checking to see whether the data are complete with plant and material storage information). Input the shipping point, delivery document type, sales area information, click Enter, and manually enter materials, quantities, etc.

VL02N Change Outbound Delivery

Use this transaction to change an outbound delivery document, which can include inputting the pick quantity, changing the shipping route for the delivery, transportation scheduling dates, deleting or adding line items to the delivery, etc. Input the delivery document and click Enter. Make changes to the header or line item information and click Save. If the delivery document is complete and the goods have been shipped, you can also post the goods issue inventory movement from this transaction, which will relieve and update inventory balances and process the associated financial transactions. For the ability to process multiple documents via a worklist, you can use transaction VL06.

VL03N Display Outbound Delivery

Use this transaction to display the delivery document, which also includes drill-down capability to view any follow-on documents, such as inventory and financial postings. Input the delivery document number and click Enter.

VL06 Delivery Monitor

Use this transaction to access the delivery monitor, which is a central transaction for monitoring and subsequent collective processing of inbound and outbound delivery documents. This transaction lists completed and open deliveries. Delivery documents can be listed depending on their status, such as all deliveries ready for picking or goods issue. Deliveries can be selected for collective processing using multiple selection options, but some of the selection options are preset, such as those dependent on the status of the delivery document. Select the type of collective processing required, for example, click
the Transportation Planning icon and on the next screen input selection options, such as shipping point or shipping planning date range, and execute.

VL06C Outbound Deliveries for Confirmation

Use this transaction for the collective processing of delivery documents that require confirmation,such asthose requiring confirmation of transfer orders for picking or put away entries. As with creation of a transfer order, the color of the confirmation indicates its status. Input selection criteria, such as shipping point and planned goods movement date range, and execute. If you have set the processing of subsequent functions to background mode, you can specify whether the picking or put away quantity should be copied into the delivery quantity or whether you want to post goods issue/goods receipt immediately following confirmation

VL06D Outbound Deliveries for Distribution

This transaction is used when integr
ating SAP with a decentralized warehouse management system (WMS) where you can choose at which point the delivery document is ready for distribution to the WMS. In customizing, you set decentralized WHS to active for the warehouse number; for the delivery type, you set at what point the distribution occurs. Furthermore, if you set the distribution option to delayed for the delivery type, then you can use this transaction to execute the distribution of the delivery document to the decentralized WMS. Selection criteria include sales area, shipping point, delivery date range, delivery status(e.g. “D” for delayed), warehouse number, delivery number, material number range, and most of the common data referenced on a delivery document.

VL06F General Delivery List – Outbound Deliveries

Use this report for a general list of outbound delivery documents. Selection criteria include sales area, shipping point, delivery date range, delivery status (e.g. transportation planning, goods issue, etc.), warehouse number, delivery number, material number range, and most of the common data referenced on a delivery document.

VL06G Outbound Deliveries for Goods Issue

Use this transaction to process the outbound delivery post goodsissue function. Selection options include shipping point and the actual goods movement date. Execute the program. Ifthe goodsissue posting wassuccessful, the processed deliveries appear in green; if errors occurred, they appear in red. The delivery also appears in green if the goods issue was already posted for the delivery document in question (this may occur because the same delivery was accidentally selected twice, for example).

VL06I Inbound Delivery Monitor

Use this transaction to access the delivery monitor, which is a central transaction for monitoring and subsequent collective processing of inbound delivery documents. This transaction can list completed and open deliveries. Delivery documents can be listed depending on their status, such as all deliveries ready for put away or goods receipt. Deliveries can be selected for collective processing using multiple selection options, but some of the selection options are preset, such as those dependent on the status of the delivery document. Select the type of collective processing required, for example, click the Transportation Planning icon and, on the next screen, input selection options such as purchase order, delivery date range, and execute.

VL06IC Inbound Deliveries for Confirmation

Use this transaction for the collective processing of delivery documents that require confirmation, such as transfer orders for picking or put away entries. As with the creation of a transfer orders, the color of the confirmation indicates its status. Input selections include purchase order document number, inbound delivery document number, planned goods movement date range. Then you can execute. If you have set the processing of subsequent functions to background mode, you can specify whether the picking or put away quantity should be copied into the delivery quantity or whether you want to post goods issue/goods receipt immediately following confirmation.

VL06ID Inbound Deliveries for Distribution

This transaction is used when integrating SAP with a decentralized warehouse management system (WMS) where you can choose at which point the delivery document is ready for distribution to the WMS. In customizing, you set decentralized WHS to active for the warehouse number; in the delivery type, you set at what point the distribution occurs. Furthermore, if you set the distribution option to delayed for the delivery type, then you can use this transaction to execute the distribution of the delivery document to the decentralized WMS. Selection criteria include sales area, shipping point, delivery date range, delivery status(e.g. “D” for delayed), warehouse number, delivery number, material number range, and most of the common data referenced on a delivery document.

VL06IF List of Inbound Deliveries

Use this report for a general list of inbound delivery documents. Selection criteria include shipping point/receiving point, purchase order, document creation date range, vendor status, status of the inbound delivery document, delivery number, material, and most of the common data referenced on a delivery document.

VL06IG Inbound Deliveries for Goods Receipt

Use this transaction to process the inbound delivery goods receipt function. This transaction may be used, for instance, in the sales return process where a delivery document is processed with the relevant information for receiving the returned materials back into the plant. Selection options include the receiving shipping point and the actual goods return date. Execute the program. If the goods return posting was successful, the processed deliveries appear in green; if errors occurred, they appear in red. The delivery also appears in green if goods return was already posted for the delivery document in question (this may occur because the same delivery was accidentally selected twice, for example)

VL06IP Inbound Deliveries for Putaway

This transaction is used to process an inbound goods receipt and put the stock into the warehouse supported by the Warehouse Management system (WM). For example, a company issues a purchase order that is confirmed by the vendor using a shipping notification. When the shipping notification is received, the data are transferred to an inbound delivery document so that you can put the inventory away into the warehouse when it arrives. Input selection criteria include purchase order document number, inbound delivery document number, planned goods movement date range; then you can execute. If you have set the processing of subsequent functions to background mode, you can specify whether the picking or put away quantity should be copied into the delivery quantity or whether you want to post the goods receipt immediately following confirmation.

VL06L Outbound Deliveries for Loading

Use this transaction to generate a list of deliveries ready for loading into a truck or shipment container prior to goods issue. The vehicle or transport equipment sealing activity is also supported. Selection options include shipping point and the actual loading date. Execute the program and update the loading date as necessary and save. The processed deliveries appear in green; if errors occurred, they appear in red.

VL06O Outbound Delivery Monitor

Use this transaction to access the delivery monitor, which is a central transaction for monitoring and the collective processing of outbound delivery documents. This transaction lists completed and open deliveries. Delivery documents can be listed depending on their status, such as all deliveries ready for picking or goods issue. Deliveries can be selected for collective processing using multiple selection options, but some of the selection options are preset, such as those dependent on the status of the delivery document. Select the type of collective processing required, for example, click the Transportation Planning icon and, on the next screen, input selection options, such as shipping point and shipping planning date range, and execute.

VL06P Outbound Deliveries for Picking

Use this transaction to execute the picking process, which involves taking goods from a storage location and staging the materials in a picking area where the goods can be prepared for shipping. Picking can be set up to post automatically at delivery document creation time or processed manually using this transaction, according to the daily workload. There is a picking status in the delivery document that indicates what stage of picking the delivery is at, such as started or completed. Selection options include shipping point, picking delivery date range, and warehouse number. Execute to display a list of deliveries ready for picking. Then select the delivery documents, enter picking quantity, and save.

VL06T Outbound Deliveries for Transportation Planning

T
his transaction is used to display a worklist of deliveries ready for transportation planning, i.e., those deliveries that are ready to be assigned a route for the delivery and a forwarding agent for transportation. A
prerequisite for this functionality is that the delivery type is flagged in customizing as transportation-planning relevant and routes are set up. Input the shipping point and transportation planning date or organize the worklist by selecting the route and/or for warding agent and then click Execute. Once the worklist is displayed, you can then assign delivery documents to shipments manually or have them automatically assigned to shipment documents.

VL06U Unchecked Outbound Deliveries

Use this transaction to display a worklist of unchecked deliveries, which are deliveries with a reduced scope of check in relation to the main availability checking functionality. An unchecked delivery is only created in reference to a preceding document that has shipping requirement dates on it. Use this transaction to convert unchecked deliveries into checked deliveries by performing all necessary checks that were explicitly switched off when you created the unchecked delivery, especially the availability checking. Input the sales area, shipping point, planned goods movement date, and click Execute. The delivery now confirms the delivery quantities to the sales order and updates the status. You can now perform all the follow-on functions, such as picking, packing, and goods issue.

VL08 Report Results of Pick Order

This transaction is used to report picked quantities. Input the delivery number and the picking request number and click Enter. On the next screen, you can confirm amounts for individual items in the picking request. Items that are subject to confirmation are automatically confirmed.

VL09 Reverse Goods Movement

Use this transaction to reverse a goods movement such as a goods issue posted in reference to an outbound delivery document. This may be require dif the goods movement was posted in error. Enter the shipping point, goods movement date, inbound/outbound delivery document number, and click Execute. Then select the delivery document/ goods movements you want to reverse and click Save. Select Enter through the confirmation message to confirm the reversal and post the reversing goods movements.

VL10 Sales and Purchase Orders, Fast Display

This transaction is used to create multiple delivery documents in reference to a sale and/or purchase order. Sales and purchase orders are analyzed and delivery documents are created according to the planned delivery date.Collective processing of deliveries may be required if you want to combine deliveries for a ship-to party. Input the shipping point, the delivery creation date (which is the earliest of the material availability date or transportation planning date), the rule for determining the delivery date, and click Execute. You can then manually process the delivery document by selecting the line and clicking the Dialog or you can select the lines and click the Creating the Deliveries in Background icon

VL10A Sales Orders, Fast Display

This transaction is used to create multiple delivery documents in reference to a sales order only. Sales orders are analyzed and delivery documents are created according to the planned delivery date. Collective
processing of deliveries may be required if you want to combine deliveries for a ship-to party. Input the shipping point, the delivery creation date (which is the earliest of the material availability date or transportation planning date), the rule for determining the delivery date, and click Execute. You can then manually process the delivery document by selecting the line and clicking the Dialog icon or you can select the lines and click the Creating the Deliveries in Background icon

VL10B Purchase Orders, Fast Display

This transaction is used to create multiple delivery documents in reference to purchasing documents only. This may be required, for instance, when delivering interplant transfers using stock transport orders. Stock transport orders are analyzed and delivery documents are created according to the planned delivery date.Collective processing of deliveries may be required if you want to combine deliveries for a ship-to plant location. Input the shipping point, the delivery creation date (which is the earliest of the material availability date or transportation planning date), the rule for determining the delivery date, and click Execute. There are also further selection options for narrowing the list of stock transport orders on the Purchase Orders tab. On the next screen, you can manually process the delivery document by selecting the line and clicking the Dialog icon or you can select the lines and click the Creating the Deliveries in Background icon.

VL10H Sales OrderandPurchase Order Items

This transaction is used to create multiple delivery documents in reference to a sales/  purchase order at the line item level. The delivery list output gives you the option to select specific quantities, at the line item level, when combining and creating deliveries. Sales and purchase orders are analyzed and delivery documents are created according to the planned delivery date. Collective   processing of deliveries may be required if you want to combine deliveries for a ship-to party. Input the shipping point, the delivery creation date (which is the earliest of the material availability date or transportation planning date), the rule for determining the delivery date, and click Execute. You can then manually process the delivery document by selecting the line and clicking the Dialog icon or you can select the lines and click the Creating the Deliveries in Background icon

VL10I Sales and Purch. Order Item Sched. Lines 

Use this transaction to create multiple delivery documents in reference to a sales or purchasing schedule line agreement. Schedule line agreements contain details of a delivery schedule. Some scheduling agreements contain two sets of delivery date: one
is a forecast delivery date and the other is a firm delivery date that can be sent by the customer via EDI. Once the firm delivery dates are received, you can use this transaction for  the automatic creation of the delivery documents for subsequent shipment processing. Collective processing of deliveries can also facilitate combining deliveries for a ship-to party. Input the shipping point, the delivery creation date (which is the earliest of the material availability date or transportation planning date), the rule for determining the delivery date, and click Execute. You can then manually process the delivery document by selecting the line and clicking the Dialog icon or you can select the lines and click the Creating the Deliveries in Background icon

VL21 Create Background Jobs for Goods Issue Posting

This transaction can be used for collectively posting the goods issue for delivery documents and can be set up to run in background mode. Selection criteria include shipping point, route, goods issue date, delivery document number, grouped delivery document number and shipment number

VL22 Display Change Documents of Delivery

Use this transaction to display a list of delivery  document change documents that are posted when details of a delivery are changed. The system records changes to the header or line item data, partner roles, status, and to management data. You can also call up  is  report when processing the delivery document in change or display mode. Selection criteria include one delivery document number at a time. Selection criteria can also include item number, date and user ID of the individual making the change. The report  utput  will display the fields changed with the option  to drill down and display the old/new field value and date changed.

VL31N Create Inbound Delivery

This transaction is used to create an inbound delivery document, which may be required to document delivery confirmation f
rom the vendor. Input the vendor number, purchase order number, expected delivery date, expected delivery time, any external ID  umbers, means of transport and click Enter. The purchase order lines will be displayed; then select the line item, input the quantity confirmed, and save.

VL32N Change Inbound Delivery

Use this transaction to change an inbound delivery document, which may be required to input a change in the planned delivery date, change the confirmed vendor delivery quantity or process the goods receipt. Input the inbound delivery document number, click Enter, make changes to the delivery date or quantity received, for example, and save.

VL33N Display Inbound Delivery

Use this transaction to display an inbound delivery document previously created via transaction VL31N.

VL35 Create Picking Waves According to Delivery Compare Times

This transaction is used to assign deliveries to picking waves. The warehouse is divided into picking timeslots, and the assignment of a delivery to a timeslot is dependent on the time when the order is recorded. Input the warehouse number, reference date (used to compare with the delivery date), timeslot group, timeslot, and other selection related to delivery data and execute. The program can be executed with the wave groups saved automatically or wave groups displayed before saving.

VL35_ST Create Pick. Waves Acc. To Shipments

Use this transaction the create wave picks automatically according to time criteria, with reference to shipments. Input the warehouse number, reference date (used to compare with the delivery date), timeslot group, timeslot, shipment number from/to range and execute. The program can be executed with the wave groups saved automatically or wave groups displayed before saving.

VL36 Change Wave Picks

This transaction is used to make changes to wave picks. Input the warehouse number, reference date (used to compare with the delivery date), timeslot group, timeslot and the numbers of the wave picks in the group field. On the next screen, the wave picks appear. Waves and deliveries that were saved with capacity problems are marked in yellow.  You can move deliveries from one wave to another and deselect waves and deliveries and then save the changes.

VL37 Wave Pick Monitor

Use this transaction to monitor the status of wave picks. Input the warehouse number, reference date (used to compare with the delivery date), timeslot group, timeslot and the numbers of the wave picks in the group field and clickExecute. The display listgives you an overview of the processing status of wavepicks.

VL41 Create Rough Goods Receipt

This transaction is used to split the goods receiving process into two steps: one a rough goods receipt and the other an exact goods receipt. This allows for the matching of a shipping notification or purchase order with a delivery note while triggering the printing of documents to enable the physical receiving of the goods (counting). You can enter a rough goods receipt only if the purchasing information record has the confirmation category (confirmation control) turned on. Input the delivery number, vendor, purchase order number, and delivery date and then click the Inbound Delivery Document icon

VL64 Generation of Inbound Deliveries

 This transaction is used to search for a delivery schedule of a purchase order line item or schedule line of a scheduling agreement where the flag is set for Automatic inbound delivery creation. If the delivery date for the schedule line is older than or equal to the delivery date entered by the user, the system generates a new inbound delivery for each purchase order and/or scheduling agreement. Selection criteria include vendor, plant, purchasing document number and delivery to date. The program can be run in test or update mode.

VL65 Inbound Delivery Purge Report

This transaction is used to purge old inbound deliveries for which no more goods receipts are expected. For this program to work, the purge offset in days needs to be entered in customizing for the warehouse in question. The goods movement status of the inbound delivery at the header level and for each item is set to C (completely processed) if the offset days are reached for the purge scenario. Selection criteria include purge scenario (e.g., third part process or stock transport order), warehouse number and delivery  umber. The program can be executed in test or update mode.

VL66 Delete Inbound Delivery

Use this transaction to delete an inbound  delivery document. Note that the inbound delivery document must not have any goods receipts posted to it or any handling units assigned to it. Selection criteria include delivery document and the created on date. The program can be executed in test or update mode.

VLSP Subsequent Outbound Delivery Split

This transaction is used to subsequently split a delivery into multiple deliveries, which is required if you discover that one delivery has too many items or the quantity is too large for the means of transport. This functionality has to be activated in customizing. uring
the subsequent outbound-delivery split, the status of the delivery document is checked to ensure that subsequent functions, such as goods movements or billing documents, have not been created. Also, the system confirms characteristics (delivery groups and   orrelation), copies data (texts), calculates attributes (volume and weight), and carries out determinations (outputs). Selection criteria include  shipping point, outbound delivery document, handling unit, ship-to party, shipment data and split profile, which contains the control settings for how the split deliveries will be grouped.

VM01 Create Hazardous Material

This transaction is used to create hazardous material master records that contain special  handling instructions in the warehouse management system. Information in the master record can include storage class (how the material should be stored), hazardous  material storage warning (warnings that can be issued when handling the material in the  warehouse) and, if the material is liquid, what concentration of a hazardous substance (as a percentage) is in the material. Regulations governing hazardous material vary by national laws, so the master record data can be customized to include any extra data required. Input the hazardous material number and the region code that governs the hazardous material regulations and click Enter. Maintain the relevant data and save.

VM02 Change Hazardous Material

Use this transaction to change hazardous material master records that contain special handling instructions in the warehouse management system. This may be required if, for example, regulations governing the hazardous material were to change. Input the
hazardous material number and the region code that governs the hazardous material regulations and click Enter. Maintain the relevant data and save.

VM03 Display Hazardous Material

Use this transaction to display a hazardous material previously created using transaction VM01.

VRRE Create Returns Delivery for Repair Order

This transaction is used to create a returns delivery document in reference to a single returns request. This transaction is similar to transaction VL01N (Create Delivery Document) except that you can cannot process the post goods movement (instead, you have to use transaction VL02N the post the goods receipt). The delivery document can serve as the basis for planning the material return and for processing the credit memo. Input the shipping point, return request, delivery type, click Enter, review the delivery quantity  nd default information, and click Save.

VS01 Create Scale

This transaction is used to create a scale for calculating shipment costs, for example, a scale to calculate a freight rate depending on the combination of a distance scale (scale base type distance) and weight scale (scale base type weight). In order to calculate freight costs based on
scales, you also need to assign the scale to the freight condition type using transaction T_06. Input the scale basis, click Enter, and on the next screen enter a description for the scale, scale type (controls scale level, e.g., “scale basis” or “to scale”), enter scale levels, and save.

VS02 Change Scale

Use this transaction to change the scale rate for calculating shipment costs, for example, a scale to calculate a freight rate depending on the combination of a distance scale (scale base type distance) and weight scale (scale  base type weight). Input scale ID, click  enter, change rates and save

VS03 Display Scale

Use this transaction to display scales for calculating shipment costs,for example, a scale VS03 Display Scale Use this transaction to display scales for calculating shipment costs,for example, a scale 

VS04 Create Scale with Reference

 Use this transaction to create a scale with reference to an existing scale. Input the scale ID and click Enter. Then, on the next screen,  make changes for the new scale and save.

V T01N Create Shipment

This transaction is used to create an individual shipment document, which controls the transportation planning process, including acquiring the services of a forwarding agent, organizing the means of transportation, specifying the route of the shipment, and  defining the stages covering the route in the most efficient way. In customizing, the delivery type must be relevant for transportation planning and, for outbound deliveries, the routes have to be defined. Input the transportation point, shipment type (what type of  transportation is to be processed, for example, shipment by road), selection variant (can default values for transportation planning) and click Enter. On the next screen, assign deliveries to the shipment, select a forwarding agent, plan the transportation times/dates, and save the document. 

V T02N Change Shipment

Use this transaction to change an individual shipment document, which controls the transportation planning process, including acquiring the services of a forwarding agent, organizing the means of transportation, specifying the route for the shipment, and  defining the stages covering the route in the most efficient way. Input the shipment document, click Enter, make the necessary  changes,such as assign additional deliveries documents, adjust transportation times/date, etc. and save.

V T03N Display Shipment

Use this transaction to display a shipment document previously created using transaction VT01N.

V T04 Create Shipments in Collective Proc.

This transaction is used to create multiple shipment documents automatically at one time depending on grouping rules that you define. The shipment document controls the transportation planning process, including acquiring services of a forwarding agent, organizing the means of transportation, specifying the route for the shipment, and defining stages covering the route in the most efficient way. In customizing, the delivery type must be relevant for transportation planning and, for outbound deliveries, routes have to be defined. Select whether inbound or outbound shipment documents are to be created and then define which deliveries will be considered by maintaining a selection variant. Then you can define the grouping criteria for the shipment documents, such as grouping by shipping point, ship-to party and route with minimum and maximum values for weight, volume and number of  deliveries. You can also define some default values for shipment dates and times. There  is also an option to process transportation chains when shipments consist of multiple shipment documents. Execute the program with an option to log the results, which can be viewed via transaction VT05.

V T05 Logs in the Application Log

Use this transaction to display the log resulting from the collective shipment create program executed via transaction VT04. The amount of detail in the log depends on your selection when executing transaction VT04; for example, you can save the log with a normal amount of detail or with very detailed information, including messages of a technical nature

V T06 Shipment List: Collective Change Shipment

This transaction is used for mass changes to shipment documents, for example, if you need to change the forwarding agent on muliple shipments. Instead of changing each document individually, you can make a mass change in multiple shipment documents in  one step. This change function allows you to enter changes in a sample line and then carry those changes over multiple shipment documents. Selection criteria include forwarding agent, route, shipping conditions, container ID, overall transport status and various
transportation planning dates. Execute the program and, on the next screen, enter your changes in the default line and choose reference document. New value(s) will update the selected shipment documents and then you can save your changes.

V T11 Shipment List: Planning

Use this transaction for reporting on shipments to be planned or scheduled. For example, a shipment planner can select, as selection criteria, the overall transport status 0 (Planned), transportation planning point,  planned check-in date, and the shipment
type. Input selection criteria and execute to display the list. On the next screen, the planner can select a shipment and branch to the shipment document for processing and save the document. This report is displayed in advanced list viewer(ALV)format, which
means there are advanced view options that can be customized by the user and saved for future reporting.

V T12 Shipment List: Shipment Completion

This transaction is similar to transaction VT11 but has an extra option related to status reporting of the shipment document, in particular, transportation status and dates for planned and actual shipment completion. 

V T16 Shipment List: Check-in

Use this transaction to report on shipments that you want to check in. You can report on all shipments that are expected to arrive on that day, for instance, so that you can check in the shipments as the trucks arrive. Selection criteria important for check-in  include planned deadlines and service agents. Input  selection criteria and execute the report. From  the displayed list, you can set the check-in status for all selected documents. Provided that the relevant setting was made in the activity profile, a dialog box will appear in which the truck’s license plate number and driver’s name can be entered. Once you have made changes to a shipment document in the list and then returned to the list, you can use the Refresh function to update the list.

V T20 Overall Shipment Status Monitor

This transaction gives a good overview of the transportation execution process, displaying shipments grouped by status, time, and date and how much workload exists. For example, the transportation planner can review a particular shift in terms of workload and  react to a busy schedule. In this way, the work can be distributed more evenly. Selection criteria  include transportation planning point, shipment type, shipping point, forwarding agent, transportation planning date and time range, status groups, and an option to select the critical number of shipments per hour.

V T22 Selection Screen: Change Document Shipment

Use this transaction to report a list of shipment document changes. Selection criteria include user ID of the individual making the change, date and time of change, shipment number, shipment document table/field, and an option to display the changes per shipment or by field grouping. The report output will list the fields changed grouped by shipment document or table field and the old/new field values and date changed.

V T32 Selection Criteria for Forwarding Agent

This transaction is used to report on the tendering status of shipment order where one or more potential transportation service  providers submit a quote for the t
ransportation service. Selection criteria include tender status, such as accepted or rejected
by forwarding agent, date of tender status, forwarding agent, shipment type, and overall status of the shipment document. Once the quote is accepted, the shipment order is updated with the terms and conditions of the transportation service and the service is
carried out.

V T70 Messages for Shipments

Use this transaction to print output from shipment documents. The types of documents that can be output include general shipping documents, labels to attach to the side of containers, shipment notifications and pro forma billing documents to accompany export shipments across country borders. Input the shipment document number, planned shipment completion date, transportation planning point, business partners (including ship-to party and forwarding agent), output type (documents), the transmission medium (such as printout and email), output device (such as a printer), and execute. The next screen will show the status of the output

VV21 Create Output – Condition Records:Shipping

This transaction is used to create conditions for the automatic generation of output (such as printed documents/sending emails) for shipping documents. Input the output type and click Enter to select the condition table. Then choose the condition table that will
store the condition records and click Enter. The condition record will be those conditions that, if fulfilled, will automatically generate the output. On the next screen, input the conditions, the valid from/to date range and save.

VV22 Change Output – Condition Records:Shipping

Use this transaction to change conditions for the automatic generation of output (such as printed documents/sending emails) for shipping documents, which may be required to extend the validity period for the condition record. Input the output type and click Enter to select the condition table. Then choose the condition table that will store the condition records and click Enter. Make changes to the condition record and save 

VV31 Create Output – Condition Records: Billing

 This transaction is used to create conditions for the automatic generation of output (such as printed documents/sending emails) for billing documents. Input the output type and click Enter to select the condition table. Then  choose the condition table that will store the condition records and click Enter. The condition record will be those conditions  that, if fulfilled, will automatically generate the output. On the next screen, input the conditions and the valid from/to date range and save

VV32 Change Output – Condition Records: Billing

Use this transaction to change conditions for the automatic generation of output (such as printed documents/sending emails) for billing documents, which may be required to extend the validity period for the condition record. Input the output type and click  Enter to select the condition table. Then choose the condition table that will store the condition records and click Enter. Make changes to the condition record and save

Veja também:

• SAP SD 
• SAP S/4 HANA SD Configuration
• Configuração SAP SD

Faça a inscrição para a prova de certificação. Estude com os simulados Bynem