SD Flow Inquiry Quotation Sales order Shipping Delivery Invoice Return goods.

MM Process Flow
The typical procurement cycle for a service or material consists of the following phases: 1. Determination of Requirements Materials requirements are identified either in the user departments or via materials planning and control. (This can cover both MRP proper and the demand-based approach to inventory control. The regular checking of stock levels of materials defined by master records, use of the orderpoint method, and forecasting on the basis of past usage are important aspects of the latter.) You can enter purchase requisitions yourself, or they can be generated automatically by the materials planning and control system. 2. Source Determination The Purchasing component helps you identify potential sources of supply based on past orders and existing longer-term purchase agreements. This speeds the process of creating requests for quotation (RFQs), which can be sent to vendors electronically via SAP EDI, if desired. 3. Vendor Selection and Comparison of Quotations The system is capable of simulating pricing scenarios, allowing you to compare a number of different quotations. Rejection letters can be sent automatically. 4. Purchase Order Processing The Purchasing system adopts information from the requisition and the quotation to help you create a purchase order. As with purchase requisitions, you can generate Pos yourself or have the system generate them automatically. Vendor scheduling agreements and contracts (in the SAP System, types of longer-term purchase agreement) are also supported. 5. Purchase Order Follow-Up The system checks the reminder periods you have specified and - if necessary - automatically prints reminders or expediters at the predefined intervals. It also provides you with an up-to-date status of all purchase requisitions, quotations, and purchase orders. 6. Goods Receiving and Inventory Management Goods Receiving personnel can confirm the receipt of goods simply by entering the Po number. By specifying permissible tolerances, buyers can limit over- and under deliveries of ordered goods. 7. Invoice Verification The system supports the checking and matching of invoices. The accounts payable clerk is

notified of quantity and price variances because the system has access to PO and goods receipt data. This speeds the process of auditing and clearing invoices for payment

Important Tables for SAP SD

Sales and Distribution: Table Customers KNA1 KNB1 reconciliation acct) KNB4 KNB5 KNBK KNKA KNKK limits) KNVV KNVI KNVP KNVD KNVS KLPA Sales Documents VBAKUK VBUK VBAK VBKD VBUP VBAP VBPA VBFA VBEP VBBE Description General Data Customer Master Co. Code Data (payment method, Customer Customer Customer Customer Customer Payment History Master Dunning info Master Bank Data Master Credit Mgmt. Master Credit Control Area Data (credit

Sales Area Data (terms, order probability) Customer Master Tax Indicator Partner Function key Output type Customer Master Ship Data Customer/Vendor Link VBAK + VBUK Header Status and Administrative Data Sales Document - Header Data Sales Document - Business Data Item Status Sales Document - Item Data Partners Document Flow Sales Document Schedule Line Sales Requirements: Individual Records Delivery Document item data, includes referencing PO Delivery Document Header data Billing Document Header Billing Document Item Shipping Unit Item (Content) Shipping Unit Header

SD Delivery DocumeLIPS LIKP Billing Document VBRK VBRP VEKP VEPO

SD Shipping Unit

MM Process Flow
The typical procurement cycle for a service or material consists of the following phases: 1. Determination of Requirements Materials requirements are identified either in the user departments or via materials planning and control. (This can cover both MRP proper and the demand-based approach to inventory control. The regular checking of stock levels of materials defined by master records, use of the orderpoint method, and forecasting on the basis of past usage are important aspects of the latter.) You can enter purchase requisitions yourself, or they can be generated automatically by the materials planning and control system. 2. Source Determination The Purchasing component helps you identify potential sources of supply based on past orders and existing longer-term purchase agreements. This speeds the process of creating requests for quotation (RFQs), which can be sent to vendors electronically via SAP EDI, if desired. 3. Vendor Selection and Comparison of Quotations The system is capable of simulating pricing scenarios, allowing you to compare a number of different quotations. Rejection letters can be sent automatically. 4. Purchase Order Processing The Purchasing system adopts information from the requisition and the quotation to help you create a purchase order. As with purchase requisitions, you can generate Pos yourself or have the system generate them automatically. Vendor scheduling agreements and contracts (in the SAP System, types of longer-term purchase agreement) are also supported. 5. Purchase Order Follow-Up The system checks the reminder periods you have specified and if necessary automatically prints reminders or expediters at the predefined intervals. It also provides you with an up-to-date status of all purchase requisitions, quotations, and purchase orders. 6. Goods Receiving and Inventory Management Goods Receiving personnel can confirm the receipt of goods simply by entering the Po number. By specifying permissible tolerances, buyers can limit over- and under deliveries of ordered goods. 7. Invoice Verification The system supports the checking and matching of invoices. The accounts payable clerk is notified of quantity and price variances because the system has access to PO and goods receipt

data. This speeds the process of auditing and clearing invoices for payment.

Extraction SD Sales: Order Delivery

Technical Name: 2LIS_11_V_SSL

Technical Data
Type of DataSource Application Component Available from OLTP Release Available from Plug-In Release RemoteCube Compatibility Transaction data SD Sales (BW-BCT-SD) 4.0 2002.1 No

Use
Use the structure Extraction SD Sales: Order Delivery to extract essential information about the delivery of order schedule lines to an SAP BW system.

Delta Update

A Delta update is supported.

Fields of Origin in the Extract Structure

Field in Extract Structure VBELN POSNR ETENR VBELN_VL POSNR_VL ROCANCEL WMENG Description of Field in Table of Origin the Extract Structure Sales document number Item number of sales document Schedule line number Delivery Delivery item Cancellation of data record Requested quantity of order schedule line in Sales ME
Definition Rquested order quantity of a single schedule line in the extract structure MC11V_0SSL. Use Because a schedule line in the extract structure MC11V_0SSL can be assigned to several delivery items, you only fill in the requested quantity once for the first data record in the schedule line during an extraction process.

Field in Table of Origin

VBAP VBAP VBEP LIPS LIPS

VBEP

BMENG

Confirmed quantity of an order schedule line in Sales ME

Definition Confirmed quantity of an order schedule line in the extract structure MC11V_0SSL. Use Because a schedule line in the extract structure MC11V_0SSL can be assigned to several delivery items, you only fill in the requested quantity once for the first data record in the schedule line during an extraction process.

VBEP

VSMNG

Delivered quantity in Sales ME of order

WVBEP Dynamic part of the

schedule line
Definition Share of the delivery quantity of a delivery item assigned to a confirmed schedule line in the extract structure MC11V_0SSL. Use In this field, the quantities delivered for an order item are assigned to the confirmed quantities of the schedule line for the order item. This assignment is basically dynamic and is determined anew with each extraction process. There is no fixed assignment between order schedule lines and order items. The quantity shipped is therefore basically displayed in the sales unit of the order schedule line. For individual conversion, the conversion factors in the base unit of measure from the order schedule line are available in the extract structure as well. An order schedule line with delivery block is only assigned a quantity when you are dealing with the last schedule line for an item and the entire quantity of available delivery items could not yet be assigned.

schedule lines

VRKME LFGSA LFSTA WBSTA MCEX_WBSTA_LOW

Sales unit Overall delivery status of item Delivery status Goods movement status Smallest goods movement status of an order item
Definition This field contains the smallest goods movement status of all delivery items of an order item. Use The field is only used and filled in the extract structure MC11V_0SSL (DataSource 2LIS_11_V_SSL).

VBEP VBUP VBUP VBUP Field is determined dynamically

There, this status is determined for one order item at a time, and is assigned to all data records for the order item. This status is basically empty for items not yet completely delivered. If an order item is controlled so that the item is already completed with the first partial delivery, then the lowest goods issue status for the order item is not empty, even if a delivery item cannot be assigned to all schedule lines.

MCEX_W_LFDAT

Requested delivery date of an order schedule line

Definition This field contains the requested delivery date of an order schedule line. Use The field is only used and filled in the extract structure MC11V_0SSL (DataSource 2LIS_11_V_SSL). For schedule lines with a positive requested quantity, the requested delivery date is the schedule line date. For schedule lines without a requested quantity, the requested delivery date is taken from the last available schedule line with a positive requested quantity.

Field is determined dynamically

MCEX_W_LFUHR

Requested delivery time of an order schedule line

Definition This field contains the requested delivery time of an order schedule line. Use The field is only used and filled in the extract structure MC11V_0SSL (DataSource 2LIS_11_V_SSL). For schedule lines with a positive requested quantity, the requested delivery time is the arrival time of the schedule line.

Field is determined dynamically

For schedule lines without a requested quantity, the requested delivery time is taken from the arrival time of the last available schedule line with positive requested quantity.

MCEX_B_LFDAT

Confirmed delivery date Field is determined dynamically

Definition This field contains the confirmed delivery date of an order schedule line. Use The field is only used and filled in the extract structure MC11V_0SSL (DataSource 2LIS_11_V_SSL). For schedule lines with a positive confirmed quantity, the confirmed delivery date is the schedule line date. This date is basically not filled for schedule lines without a confirmed quantity.

MCEX_B_LFUHR

Confirmed delivery time Field is determined dynamically

Definition This field contains the confirmed delivery time of an order schedule line. Use The field is only used and filled in the extract structure MC11V_0SSL (DataSource 2LIS_11_V_SSL). For schedule lines with a positive confirmed quantity, the confirmed delivery time is the arrival time of the schedule line. This field is basically not filled for schedule lines without a confirmed quantity.

MCEX_B_WADAT

Planned goods issue date of a confirmed schedule line

Definition This field contains the planned goods issue date of an order schedule line with a confirmed quantity. Use The field is only used and filled in the extract structure MC11V_0SSL (DataSource

Field is determined dynamically

2LIS_11_V_SSL). For schedule lines with a positive confirmed quantity, the confirmed planned goods issue date is the goods issue date of the schedule line. This date is basically not filled for schedule lines without a confirmed quantity.

MCEX_I_WADAT

Actual goods movement date of a delivery

Definition This field contains the actual goods movement date of a delivery of an item order. Use The field is only used in the extract structure MC11V_0SSL (DataSource 2LIS_11_V_SSL). There, this date is determined for one delivery at a time, and is assigned to all data records for this delivery. In these data records, you are dealing with confirmed quantities of order schedule lines, which are assigned a corresponding delivery item as delivery. The date is only assigned if it was entered in the associated delivery.

Field is determined dynamically

MCEX_I_WADATLATE

Last actual goods movement date of an order item

Definition This field contains the last actual goods movement date of all delivery items of an order item. Use The field is only used in the extract structure MC11V_0SSL (DataSource 2LIS_11_V_SSL). There, this date is determined for one order item at a time, and is assigned to all data records for the order item. This date is basically empty for items not yet completely

Field is determined dynamically

delivered. If an order item is completed delivered but goods issue has not yet been posted for all deliveries, then the field contains the last goods movement date of all deliveries already posted. If an order item is controlled so that the item is already completed with the first partial delivery, then the last actual goods movement date for the order item is filled even if an delivery item cannot be assigned to all schedule lines.

MCEX_I_LFDAT

Actual delivery date of a Field is determined dynamically delivery

Definition This field contains the actual delivery date of a delivery of an item order. Together with the actual delivery time, the actual delivery date forms the point in time when the delivered goods arrive at the customer. Use The field is only used in the extract structure MC11V_0SSL (DataSource 2LIS_11_V_SSL). There, the time is calculated for one delivery at a time from the actual goods movement date, and is assigned to all data records for this delivery. In these data records, you are dealing with confirmed quantities of order schedule lines, which are assigned a corresponding delivery item as delivery. The date is calculated via the following rules: For every schedule line receiving the delivery concerned, the deviation between the confirmed goods movement date and the actual goods movement date is added to the confirmed delivery date The actual delivery date is thereby equated with the actual goods movement date, if the calculated value were to get smaller. The actual delivery time is taken from the confirmed

delivery time of the schedule line. The latest actual delivery timespot calculated in this way is assigned to all delivered schedule line quantities. This time-spot is used if the actual delivery date and actual delivery time are created as of R/3-Release 4.6 via the acknowledgement of receipt of goods.

MCEX_I_LFUHR

Actual delivery time of a Field is determined dynamically delivery

Definition This field contains the actual delivery time of a delivery of an item order. Together with the actual delivery date, the time forms the point in time when the delivered goods arrive at the customer. Use The field is only used in the extract structure MC11V_0SSL (DataSource 2LIS_11_V_SSL). There, the delivery time-spot is determined for one delivery at a time, and is assigned to all data records for this delivery. In these data records, you are dealing with confirmed quantities of order schedule lines, which are assigned a corresponding delivery item as delivery. For more information on determining actual delivery time-spots, see Actual Delivery Date.

MCEX_I_LFDATLATE

Last actual delivery date of an order item

Definition This field contains the last actual delivery date of all delivery items of an order item. Together with the actual delivery time, this field forms the point in time when the last delivery for an order item arrives at the customer. Use The field is only used in the extract structure MC11V_0SSL

Field is determined dynamically

(DataSource 2LIS_11_V_SSL). There, this date is determined for one order item at a time, and is assigned to all data records for the order item. This field is basically empty for items not yet completely delivered. If an order item is completed delivered but the goods issue has not yet been posted for all deliveries, then the field contains the last actual delivery date of all deliveries already posted. If an order item is controlled so that the item is already completed with the first partial delivery, then the last actual delivery time-spot for the order item is determined even if an delivery item cannot be assigned to all schedule lines.

MCEX_I_LFUHRLATE

Last actual delivery time of an order item

Definition This field contains the last actual delivery time of all delivery items of an order item. Together with the actual delivery date, this field forms the point in time when the last delivery for an order item arrives at the customer. Use The field is only used in the extract structure MC11V_0SSL (DataSource 2LIS_11_V_SSL). There, this date is determined for one order item at a time, and is assigned to all data records for the order item. This field is basically empty for items not yet completely delivered. If an order item is completed delivered but the goods issue has not yet been posted for all deliveries, then the field contains the last actual delivery time-spot of all deliveries already posted. If an order item is controlled so that the item is already completed with the first partial delivery, then the last actual

Field is determined dynamically

delivery time-spot for the order item is determined even if an delivery item cannot be assigned to all schedule lines.

LIFSP MEINS UMVKN

Delivery block item Base unit of measure Denominator for conversion of sales unit into SKU. Numerator for conversion of sales unit into SKU. Sales document category Schedule line deleted
Definition This indicator for DataSource 2LIS_11_V_SSL signals that the respective schedule line for the current document change was deleted. Use The field is only used and filled in the extract structure MC11V_0SSL (DataSource 2LIS_11_V_SSL). There, this indicator is determined for one order schedule line item at a time, and is assigned to all data records for the order schedule line. Because the DataSource 2LIS_11_V_SSL basically does not transfer any deletion information to the SAP BW system, this indicator can be used to delete the schedule line within the start routine when you update an ODS with Order Number, Item Number and Schedule Line Number as key fields. In such an update, the schedule line usually remains in the SAP BW system with blank indicators.

VBAP VBEP VBEP

UMVKZ

VBEP

VBTYP VBEP_DELETED

Field is determined dynamically

RECORD_DELETED

Order schedule line delivery deleted

Definition This indicator for DataSource 2LIS_11_V_SSL signals that a

Field is determined dynamically

unique data record of the DataSource was deleted during the current document change. A data record is uniquely determined via the five key fields Order Number, Item Number, Schedule Line Number, Delivery Number and Delivery Item Number. Use The field is only used and filled in the extract structure MC11V_0SSL (DataSource 2LIS_11_V_SSL). There, this indicator is determined for each combination of order schedule line and delivery item, and is assigned to the corresponding data record. Order schedule lines not yet assigned a delivery item are flagged with blank delivery number and delivery item number. Because the DataSource 2LIS_11_V_SSL basically does not transfer any deletion information to the SAP BW system, this indicator can be used to delete the corresponding data record within the start routine when you update an ODS with Order Number, Item Number, Schedule Line Number, Delivery Number and Delivery Item Number as key fields. In such an update, the corresponding data record usually remains in the SAP BW system with blank indicators.

Features of Extractor
y y y y A data record is uniquely determined via the five key fields Order Number, Item Number, Schedule Line Number, Delivery Number and Delivery Item Number. The transfer of Deltas from this extract structure occurs during document changes as well as delivery changes. In reconstruction, this structure is set up under the order data (application 11) in the table MC11V_0SSLSETUP. The data records for the extract structure contain requested schedule lines as well as confirmed schedule lines of the order items. If there are delivery items for the order items, then the delivery quantities are assigned to the confirmed schedule lines. If there are no deliveries available for a schedule line, then a data record is transferred to the schedule line in which the delivery number, delivery item number and all further delivery-related data record is unfilled.

If several delivery items can be assigned to the schedule line, then several data records containing different delivery numbers, delivery item numbers and the associated delivered quantity, are transferred to the schedule line. On the other hand, if a delivery item delivers to more than one confirmed schedule line at the same time, then this results in several data records for the same delivery item with different schedule line numbers. The delivery quantity is distributed across the schedule lines as shipped quantity.