How Sales Documents are Structured

All sales documents have basically the same structure. They are made up of a document header and any number of items. The items can in turn be divided into any number of schedule lines. The following graphic shows the structure of a sales document:

Header data
The general data that is valid for the entire document is recorded in the document header. For example, Number of the sold-to party Number of the ship-to party and the payer Document currency and exchange rate Pricing elements for the entire document Delivery date and shipping point

Item data
Whereas data in the document header applies to all items in the document, some data applies only to specific items. This data is stored at item level and includes the: Material number Target quantity for outline agreements Number of the ship-to party and the payer (an alternative ship-to party or payer can be defined for a particular item) Plant and storage location specifications

Pricing elements for the individual items

Schedule line data

An item consists of one or more schedule lines. The schedule line contains all the data that is needed for a delivery. For example, a customer orders 20 units of a particular material which you enter as one item in the sales order. However, you can only deliver 10 pieces now and the remaining 10 pieces next month so you need to schedule two deliveries. The data for these deliveries (dates, confirmed quantities) are stored in two separate schedule lines. In sales documents where delivery data is not relevant, for example, contracts, credit and debit memo requests, the system does not create any schedule lines. Data recorded in the schedule lines includes the: Schedule line quantity Delivery date Confirmed quantity

Sales Order
Implementation Considerations
The sales order is a contractual agreement between a sales organization and a sold-to party about delivering products or providing a service for defined prices, quantities and times. In sales order processing, the system implements various functions: In the sales order, functions such as pricing and printouts are available. The system checks whether the material is available for the requested delivery date and if necessary, transfers the requirements to materials planning. Shipping deadlines and shipping points are determined in delivery scheduling. Another part of this component are the special sales order types - rush orders and cash sales. (For more information, see Special Sales Orders.) In cash sales the goods are paid for in cash. In a rush order transaction, the customer picks up the goods or you deliver the goods on the same day as the order is placed. However, the invoice is created later.

Features
You can process sales orders in the SAP R/3 System differently, depending on your specific needs. In the most simple case, you can enter a sales order with several items in a single screen. The system automatically proposes data from the relevant master records: From the customer master record of the sold-to party, the system proposes sales, shipping, pricing, and billing data. In addition, the system copies customer-specific master data about texts, partners, and contact people at the customer site. For each material in the sales order, the system automatically proposes data from the relevant material master records, such as data for pricing, delivery scheduling, availability check, tax determination, and weight and volume determination.

The data proposed by the system can be used as a basis for your order. If your sales order processing requires it, you can modify this data manually or add new data. For example, your pricing policy may allow you to manually change the value of certain discounts within a permitted range. In addition, you can branch in the sales order to a number of different screens where you can display and modify data, such as terms of payment and delivery data.

Using Existing Documents as a Reference

It is also easy to create a new sales order with reference to an existing document. For example, if a customer accepts a quotation you sent, the system can copy all the relevant master data from the quotation when you create the sales order (see Creating a Sales Order With Reference).

Standard Functions During Order Processing

When you process a sales order using the standard version of the SAP R/3 System, the system can automatically carry out basic functions, such as the following: Pricing Availability check (if this function is defined in the material master record) Transferring requirements to materials planning (MRP) Delivery scheduling Shipping point and route determination

Checking credit limits

Sales and Distribution (SD)

The Sales and Distribution (SD) Benchmark covers a sell-from-stock scenario, which includes the creation of a customer order with five line items and the corresponding delivery with subsequent goods movement and invoicing. It consists of the following transactions:

Create an order with five line items. (VA01) Create a delivery for this order. (VL01N) Display the customer order. (VA03) Change the delivery (VL02N) and post goods issue. List 40 orders for one sold-to party. (VA05) Create an invoice. (VF01)

Each benchmark user has his or her own master data, such as material, vendor, or customer master data to avoid data-locking situations.

Dialog Steps
0. Logon 1. Main screen 2. Call /nVA01 (Create customer order) 3. First screen 4. Second screen (with five items) 5. Choose Save 6. Call /nVL01N (Create a delivery) 7. First screen 8. Choose Save 9. Call /nVA03 (Display customer order) 10. Choose Enter 11. Call /nVL02n (Change delivery) 12. Choose [F20] (Posts goods issue) 13. Call /nVA05 (List orders) 14. Choose Enter 15. Call /nVF01 (Create invoice) 16. Choose Save 17. Call /nend 18. Confirm log off

User interaction steps 2 - 16 are repeated n times (15 user interaction steps --> min. 150 sec. duration). Business aspect: One run (user interaction steps 2 - 16) corresponds to the selling of five items.

T Codes:
SPRO MM01 MM02 MM03 MMS1 MMS2 MMS3 MB1C MMPI MMBE MM60 XD01 XD02 XD03 VA01 VA02 VA03 VA11 VA12 VA13 VA21 VA22 VA23 VD02 VD03 VD04 VD06 VK11 VK0A VOK0 VOR1 VOR2 VOV6 VOV8 VOFA V129 V149 CA01 CA02 CA03 CS01 CS02 CS03 OVK1 OVK3 OVK4 OVR6 DEFINE ITEM CATEGORY CREATE MATERIAL MODIFY MATERIAL DISPLAY MATERIAL CREATE MATERIAL MASTER CHANGE MATERIAL MASTER DISPLAY MATERIAL MASTER MAINTAIN STOCK INITIALISE PERIOD FOR MASTER MATERIAL RECORDFROM CO CODE CREATE STOCK MATERIAL LIST CREATE CUSTOMER MODIFY CUSTOMER DISPLAY CUSTOMER CREATE ORDER CHANGE ORDER DISPLAY ORDER CREATE INQUIRY CHANGE INQUIRY DISPLAY INQUIRY CREATE QUOTATION CHANGE QUOTATION DISPLAY QUOTATION CHANGE SALES PROSPECT DISPLAY SALES PROSPECT DISPLAY CHANGES FLAG FOR DELETION MAINTAINING PRICING ASSIGN G/L ACCOUNT GENERAL PRICING DEF COMMON DIST CHANEL DEF COMMON DIV DEFINE SCHEDULE LINES DEFINE SALES DOC TYPE CREATE/OR CHANGE BILLING TYPES CONFIGURATION DEFINE INCOMPLETENESS SCHEMAS FOR FOREIGN TRADE ASSIGN INCOMPLETENESS SCHEMAS FOR COUNTRY CODE CREATE ROUTING EDIT ROUTING DISPLAY ROUTING CREATE BOM CHANGE BOM DISPLAY BOM DEFINE TAX DET RULES DEF TAX REL OF MASTER RECORDS CUSTOMER TAXES DEF TAX REL OF MASTER RECORDS MATERIAL TAXES DEF LEGAL STATUSES

OVS9 OVRA OVRF OVXC OVX6 OVLK OVSG OVLH OVXM OVXJ OMS2 OVLP OX10 O/S2 O/S1 OBB8 OKKP VB01 VB02 VB03 VB31 VB32 VB33 VB21 VB22 VB23 VB25 VB35 VKA4 VKA5 VKA6 VC/1 VC/2 VDH2 VF01 VF02 VF03 VF07 VF11 VFX3 VFRB VF04 VF06 VF21 VF22 VF23 VF44 VF45 VF46 VF31 VFP1 VARR VL01N VL02N VL03N V/08 V/30 FD32 /NSM12 SM30 ND59

DEF CUSTOMER GRP MAINT STATISTICS GRPS FOR CUSTOMERS MAINT STATISTICS GRPS FOR MATERIAL ASSIGN SHIIPING POINT TO PLANT ASSIGN PLANT TO S.O AND DIST CHANEL DEFINE DELIVERY TYPE DEFINE INCOTERMS DEFINE ROUTES ASSIGN SALES OFF TO SALES AREA ASSIGN SALES GRP TO SALES OFFICE MATERAIL UPDATE DEFINE ITEM CATEGORY FOR DELIVERY ASSIGN DEL PLANTS FOR TAX DET DEFINE SERIAL NO PROFILE DEFINE CENTRAL CONTROL PARAMETERS FOR SR NO DEFINE TERMS OF PAYMENT ACTIVATION OF COMPONENETS CREATE REBATE AGGREMENTS CHANGE REBATE AGREMENT DISPLAY REBATE AGGREMENT CREATE PROMOTION CHANGE PROMOTION DISPLAY PROMOTION CREATE SALES DEAL CHANGE SALES DEAL DISPLAY SALES DEAL LIST OF SALES DEAL PROMOTION LIST CREATE ARCHIVE ADMINISTRATION DEL ARCHIVE ADMINISTRATION RELOAD ARCHIVE ADMINISTRATION CUSTOMER LIST CREATE SALES SUMMARY DISPLAY CUSTOMER HIERARCHY CREATE PROFORMA INVOICE CHANGE PROFORMAINVOICE DISPLAYPROFORMA INVOICE DISPLAY FROM ARCHIVE CANCEL BILL BLOCKED BILLING DOC RETRO BILLING MAINTAIN BILL DUE LIST BACKGROUND PROCESSING CREATE INVOICE LIST CHANGE INVOICE LIST DISPLAY INVOICE LIST MAINT REVENUE LIST REVENUE REPORTS MAINT CANCELLATION LIST ISSUE BILLING DOC SET BILLING DATE ARCHIVE DOCUMENTS CREATE DELIVERY TO CHANGE DELIVERY WHICH IS ALREADY CREATED DISPLAY DELIVERY TO CHANGE CONDITION (PR PROCEDURE) DEFINE PRINT PARAMETERS SETTING CREDIT LIMIT FOR CUSTOMER TO REMOVE LOCK ENTRY LIST CUSTOMER MATERIAL INFO

VB0F

UPDATE BILL DOC

How to access transactions for which you do not have access to execute and View ABAP Codes? Tip for use with CALCULATED caution BY EXPERTS ONLY. You do not have access to run most of the transactions in PRD, even to Z reports which do not update any data. Pre-req: You should have access to SE93 - Execute SE93 - Enter your t.Code you want to execute - Hit Display - Then double click on the program field that will take you to the program code for view. - If you click on 6th Icon from you left, which is execute, you will be able to execute this program CAUTION USE THIS TIP WITH CAUTION

Search for SAP Basis Transaciton codes

You can access all the transaction codes by using the transaction code 'SDMO'. This is the transaction code for the Dynamic Menu. Based on your search string, you can get all related transaction codes for all the SAP application modules. For e.g. the Search text for ADMIN returns the following results:
---------------------------------------------------------|Tcode|Transaktionstext | ---------------------------------------------------------|ADOK |AM: System Administration Guide | |BALE |Area Menu for Administration | |BDMO |ALE CCMS Group Administration | |CATSX|Time Sheet Admin.: Initial Screen | |CICY |CTI Administration | |CJV6 |Maintenance: Version administration | |CN84 |PS: Archiving project - admin. | |COA4 |PP: Archiving order - administration | |CSADM|Content Server Administration | |FC_BW|Administrator Workbench | |FDTA |TemSe/REGUT Data Administration | |FDTT |Treasury Data Medium Administration | |FO86 |Change active admin.contract fees | |FO8E |Create admin.contract event | |FO8F |Change admin.contract event | |FO8G |Display admin.contract event | |FO8H |Admin.costs acct sttlmnt simulation | |FOART|REsearch: Administration Web-User |

|HRCMP|Compensation Administration |HRCMP|Budget Administration: Display |HRCMP|Budget Administration: Change |IM_AR|Admin. of App. Request Archives |KA18 |Archive admin: assess., distr., ... |KE72 |Archive Administration: Line Items |KE73 |Archive Administration: Totals Recs |KPRO |KPRO Administration |OAAD |ArchiveLink Administration Documents |OG00 |Personnel Administration Customizing |OG01 |Personnel Administration Customizing |OMSM |CS MM Set Up Administrative Data |OOCM_|Compensation Administration Settings |OOML |Room Administration Mail Connection |OOPC |Administration: Personnel No. Check |OY22 |Create subadministrator Customizing |OYEA |IDoc administration |PA97 |Compensation administration - matrix |PA98 |Compensation Administration |PA99 |Compensation Admin. - Release Report |PACA |PF administration |PAT1 |Personnel Administration infosystem |PC00_|CBS survey salary administrations |PC00_|Tax Certificates - Administration 16 |PP26 |Plan Scenario Administration |PP2D |Administer Payroll Results |PSO5 |PD: Administration Tools |PUCA |PC administration for PF |PVSEA|Administer Search Engine |QD25 |Archiving Notifications: Admin. |S002 |Menu Administration |SA02 |Academic title (cent. addr. admin.) |SA04 |Name prefixes (centr. addr. admin.) |SA05 |Name suffix (centr. addr. admin.) |SA07 |Address groups (centr. addr. admin.) |SA08 |Person groups (centr. addr. admin.) |SA09 |Internat. versions address admin. |SA10 |Address admin. communication type |SARA |Archive Administration |SBPT |Administration Process Technology |SCC4 |Client Administration |SCON |SAPconnect - Administration |SCOT |SAPconnect - Administration |SCUA |Central User Administration |SCUM |Central User Administration |SE78 |SAPscript: Graphics administration |SECST|Administration of Secure Memory |SENG |Administration of External Indexes |SENGE|Explorer Index Administration |SIAC1|Web Object Administration |SLICE|Administer SAP Licenses |SLWA |Translation Environment Administratn |SM14 |Update Program Administration |SP12 |TemSe Administration |SPAD |Spool Administration |SPAT |Spool Administration (Test) |SPHA |Telephony administration |SPHB |SAPphone: System Administration |SSAA |System Administration Assistant |SSCA |Appointment Calendar: Administration |SSCA1|Appointment calendar: Administration

| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |

|SSO2 |Workplace Single Sign-On Admin. | |SSO2_|Workplace Administration SSO2 Ticket | |STMA |Proposal Pool Administration | |SURAD|Survey Administration | |SURL_|Personalization for URL Gen. Admin. | |SUUMD|Display User Administration | |SWDC |Workflow Definition: Administration | |SWEAD|Event Queue Administration | |SWEQA|Event Queue Administration | |SWEQA|Queue Administrator Maintenance | |SWIA |Selection rep. for work items(admin) | |SWRK |Administrtation using work areas | |SWUF |Administration of Runtime System | |SWUL |Customizing: Process Administrator | |SWUX |SAPforms Administration | |SYSAD|System Administration: Task List | |S_ALR|IMG Activity: CIC_V_CCMCTIADMIN | |S_ALR|IMG Activity: SIMG_EURO_ADMINUSER | |S_BCE|IMG-Aktivitt: BCDIGSI_ADMIN | |S_PH0|InfoSet Query: Administration | |S_PH0|InfoSet Query: Administration | |S_PH0|InfoSet Query: Administration | |S_PH0|InfoSet Query: Administration | |S_PH0|InfoSet Query: Administration | |TBD0 |Datafeed: Adminster Archives | |TBD3 |Datafeed: Market data administration | |TBD6 |Datafeed: Log file administration | |WE46 |IDoc administration | |WORKI|Administrtation using work areas | ----------------------------------------------------------

What the difference between tcode SE09 & SE10? SE09 transaction is for workbench transport request wherein the developers can track their changes or modifications to the workbench objects . Whereas SE10 is a customising transport request transaction.this is used for displaying customising requests. Sometimes this may be restricted to business analysts.