SAP SD FREE MATERIAL

STRANGE BEHAVIOR IN SAP : From sdn forum : Ideally if Delivery document type is with sales order requirement system should not allow to created delivry without sales order BUT there is one possibility to manipulate this check. You can check following scenario yourself in Ides or test system Create one sales order using VA01 Create delivery with reference to sales order before saving delete all items from delivery and enter same items again. and save the delivery. Now go to VL02n and check the document flow of that delivery. you will find sales order reference missing. It looks like delivery type LF is created without reference to sales order. And if you check the document flow of sales order it show no reference delivery is created. Actually once you delete items form delivery all the references also gets deleted and then you can enter not only same material but can enter any material, any quantity and you can do PGI and billing also, system will not stop you anywhere but

Material Master Tables General Material Data – MARA Material Descriptions – MAKT Plant Data for Material – MARC Material Valuation – MBEW Storage Location Data for Material – MARD Units of Measure for Material – MARM Sales Data for Material – MVKE Forecast Parameters – MPOP Planning Data – MPGD_MASS Tax Classification for Material – MLAN Material Data for Each Warehouse Number – MLGN Material Data for Each Storage Type – MLGT Vendor Master Tables: Description – Table Vendor Master (General Section) – LFA1 Vendor Master (Company Code) – LFB1 Vendor master (VAT registration numbers general section) – LFAS Vendor master (dunning data) – LFB5 Vendor Master (Bank Details) – LFBK Vendor master record (withholding tax types) X – LFBW Vendor master record purchasing organization data – LFM1 Vendor Master Record: Purchasing Data – LFM2 Vendor Subrange – WYT1 Vendor Sub-Range Description – WYT1T Partner Functions - WYT3 Related to Materials: MARA - Material Master

The most frequently used transaction codes are as follows: 1. VS00 - Master data 2. VC00 - Sales Support 3. VA00 - Sales 4. VL00 - Shipping 5. VT00 - Transportation 6. VF00 - Billing Others as follows: At Configuration: 1. VOV8 - Define Sales documents type (header) 2. OVAZ - Assigning Sales area to sales documents type 3. OVAU - Order reasons 4. VOV4 - Assign Item categoreies(Item cat determination) 5. VOV6 - Scedule line categories 6. OVAL - To assign blocks to relevant sales documents type 7. OVLK - Define delivery types 8. V/06 - Pricing 9. V/08 - Maintain pricing procedure 10.OVKP - Pricing proc determination 11.V/07 - Access sequence Enduser: 1. Customer Master Creation-VD01 and XD01 (for full inclu company code) VD02 - Change Customer VD03 - Display Customer VD04 - Customer Account Changes VD06 - Flag for Deletion Customer XD01 - Create Customer XD02 - Modify Customer XD03 - Display Customer 2. Create Other material ----

Customers KNA1 General Data KNB1 Customer Master–CCode Data (payment method, recon. acct) KNB4 Customer Payment History KNB5 Customer Master – Dunning info KNBK Customer Master Bank Data KNKA Customer Master Credit Mgmt. KNKK Customer Master CCA Data (credit limits) KNVV Sales Area Data (terms, order probability) KNVI Customer Master Tax Indicator KNVP Customer master partner Function KNVD Output type KNVS Customer Master Ship Data KLPA Customer/Vendor Link V_THIT Customer Hierarchy Types KNVH Customer Hierarchies KNVK Customer master Contact partner Sales Documents VBAKUK VBAK + VBUK VBUK Header Status and Administrative Data VBAK Sales Document – General Header Data VBKA Sales Activities VBKD Sales Document - Business Header/Item Data VBPA Sales Document - Partners Header Data VBUP Item Status VBPA Sales Document – Partner Item Data VBAP Sales Document – General Item Data FPLA sales Document – Items Conditions data VBFA Document Flow VBEP Sales Documen

1) You carry out config. changes in "Tata Group" client , (say100) in DEV server. 2) When you save, system prompts a Transport request dialogue, which is generally, saved by input of a description that identifies the Kind of Config carried out. User name appears by default with the Config request description when saved. 3) This is required to be tested in (Unit) Test Client say 120, by Client Copy of the Request using Tcode - SCC1. 4) On successful test results, we need to release the request (Tcode = SE01 or SE10). Here Collapse the request line once. Then click on Sub-task and press Transport button.. Then, Click on Main task and again press Transport button System gives success message. 5) Subsequently the BASIS Guy can transport the request to QUALITY and PRODUCTION Clients

1. Name two ways to start a transaction. Dynamic Menu Command Field 2. Why do you create user-specific parameters? They supply defaults to R/3 fields. If a field is indicated, the system automatically fills in default value. Depending on the field definition, the entry can also be replaced with a value entered by the user. (Concept of PARAMETER ID) 3. Name the three different kinds of messages in the R/3 system. What is the difference between them? A message can have five different types. These message types have the following effects during list processing: A (=Abend): The system displays a message of this message type in a dialog window. After the user confirms the message using ENTER, the system terminates the entire transaction (for example SE38). E (=Error) or W (=Warning): The system displays a message of this message type in the status line. After the user chooses ENTER, the system acts as follows: While creating the basic list, the system terminates the report