Posts

Showing posts from 2011

TAX determination in SD

Define Tax Determination Rules You specify the valid tax types in transaction OVK1. More than one tax type can be defined for a country by defining the sequence. The SAP System determines the taxes automatically within pricing. In the standard SAP R/3 System, the elements of tax calculation are predefined (for example, tax condition type "MWST" for taxes on sales and purchases). Assign the plant for Tax Determination in OX10, using the country key, the SAP System recognizes which tax type is valid for a plant and thus which taxes are relevant when creating an SD document. Define the Customer Taxes in OVK3, you will maintain the tax code in Customer Master. Define the Material Taxes in OVK4, which will then be maintain in Material Master. For example :- MWST GST 0 Tax Exempt MWST GST 1 Liable for Taxes Now, you define the Tax Determination in VK12. VK12 - Domestic Taxes/Export Taxes Condition Type MWST Customer Ta

How to create t-code from SQVI query?

How to create t-code from SQVI query? If you have created a query report from sqvi t-code, you can generate a new t-code for that report, so you can share it to other users (since sqvi query cannot be accessed by other users). You can do it as follow steps: Select your query on the SQVI screen and accessing the menu: "QuickView - Additional functions - Generate program" Display the program name by accessing menu: "QuickView - Additional functions - Display report name". Copy that program name. Open t-code: SE93. Input your new t-code name (begin with "Z" letter) in the "transaction code" field. Click "Create" button. Input the new t-code description and choose "program and selection screen (report transaction). Press "enter". Paste the program name of your sqvi query into the "program" field. Click "save" to create your new t-code that execute your sqvi query. You can give the authorization

Variant Configuration

Steps for SD Variant Configuration (Basic Steps) 1.) Create a Material - KMAT type with Item category Group(002) 2.)Create Charateristics in CT04 - Zbike, where in values mention the Color of the bile like Red, Blue etc 3.) Create another characteristics in CT04 - ZPrice, where directly go the additional data tab and maintain the table SDCOM and field VKOND (ABAP Dictionary it will ask for) 4.) Assign these two characteristics to a Class in CL01 - ZBikeclass ( Type 300) in characteristics tab page. 5.) Then go to CU41 Configuration profile select the material and enter the description click on the class assignment ie assign Zbikclass. 6.) Now go back to CT04 - enter Zbike -go to values- select Red- go to extras - Other Dependencies - Select Procedure enter in front 10 write - $self.ZPrice='Red' and save Now go back go to extras - Other Dependencies - assignments and assign relationship ( by default it will come just save) Now select Blue- go to extras - Other

SAP SD INTERVIEW QUESTIONS

A Collection From Internet Resource : What is transfer order? What are the fields in pricing procedure? What are the Standard output types in SD? What is Condition type? What is difference between delivery document & scheduling? How is item category determined? What is Extract used in condition tech. in pricing? What is the difference between plant and storage location? What is the difference between item proposal What are the statuses? What is Lean Warehouse Management? What is the purpose of sales document type? What is an integration point between SD AND MM? What are MRP types? What is use of customer group? What is the difference between incomplete order and backorder processing? Why does the customer master have different views? What is t-code for listing the blocked documents? What is batch split? What is Product attributes? What is difference between SD account key and FI account key?What is a variant and its use? How is credit control determined? Wha

CREDIT MANAGEMENT

CREDIT MANAGEMENT A credit limit may be a customer's credit limit, which is the permitted limit of value of open items, such as invoices not yet paid, plus the value of open sales orders. - The credit limit is the total combined value of the following documents: - Net value of sales order - Open Sales order: order created, but not delivered - Open deliveries: delivered, but not invoiced - Open billing doc: value of billing doc, which has not yet been forwarded to accounting - Open items: forwarded to accounting, but not settled. Types of Credit Check - Simple Credit Check - Automatic Credit Check o Static o Dynamic Simple Credit Check: SPRO- IMG- SD- Basic Functions- Credit Mgmt/ Risk Mgmt- Simple Credit Check- Assign Credit Check to Doc Types. - Based on sales doc types - It will check all the above-mentioned docs & if the credit limit exceeds, the syst

Copy Control Settings Screenshots

Image
BELOW ARE THE SCREENSHOTS OF THE COPY CONTROL SETTINGS AT HEADER LEVEL, ITEM LEVEL, AND SCHEDULE LINE LEVEL CLICK ON SCREENS TO VIEW A LARGER SCALE

Master Data Tables

General settings Countries T005 Countries Currency TCURC Currency codes TCURR Wisselkoersen TCURT Currency name TCURX Decimal places for currencies. Unit of measure T006 Units of measure Calendar functions T247 Month names TFACD Factory calendar definition T015M Month names TTZZ Time zones TTZD Summer time rules TTZDF Summer time rules (fixed annual dates) TTZDV Summer time rules (variable dates) TTZDT Summer time rules texts TTZ5 Assign Time Tones to Countries TTZ5S Assign time zones to regions Enterprise structure Definition FI T880 Company T001 Company code CO TKA01 Controlling area LO T001W Plant / sales organisation T499S Locations TSPA Division SD TVKO Sales organisation / company code TVTW Distribution channel TVBUR Sales office TVKBT Sales office text TVKGR Sales group TVGRT Sales group text T171T Sales district text MM T001L Storage locations T024E Purchasing organi

Simplify......SAP_SD: Make-to-Order__Process Flow

Simplify......SAP_SD: Make-to-Order__Process Flow : "Materials in SAP ECC system is usually either procured or produced and kept in stock or it is custom made as per the customer’s specificatio..."

SAP Note 11162 - Invoice split criteria in billing document .

Symptom From a number of deliveries or sales orders more than one billing document is created. Cause and prerequisites The invoice split may have been carried out for the following reasons: a) Explicit setting in Customizing b) Different header partners c) Different header fields d) The billing date of all documents is equated in a data transfer routine (for example, by VBRK-FKDAT = SY-DATUM). This works when you are billing using VF01; a single billing document is generated. However, if you use VF04 or in case of a batch, several billing documents might be generated. Solution Please check the causes mentioned above: 1. Explicit setting in Customizing: On the detail screen of the document flow table (TVCPF) in the entry field 'DATEN VBRK/VBRP' (as of Rel.2.2..: 'Data transfer') the routine '003' (single invoice) was entered and thus an invoice split was created. 2. Different header partners The header partners in the billing documents created

LF Delivery without Sales Order !!

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

SAP MM : A Few tables for reference

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

SD Key TRANSACTION CODES

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 ----

Important Tables : SAP SD

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

Steps to transport a Configuration Request

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

SAP SD Interview Questions - BASIC KNOWLEDGE AND SYSTEM NAVIGATION

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