Explore topic-wise InterviewSolutions in .

Price limits can be set by navigating the following menu PATH:

• CUSTOMIZING Implementation Guide (IMG Menu)->Sales and Distribution->BASIC FUNCTIONS-> PRICING->Pricing Control-> Define Condition Types-> Define Upper/Lower Limits for Conditions.

Price limits can be set by navigating the following menu path:

The following MENU PATH is navigated to define and assign account KEYS:

• Customizing Implementation Guide (IMG Menu)->Sales and Distribution->Basic Functions->Account Assignment/Costing-> REVENUE Account Determination->Define and Assign Account Keys.

The following menu path is navigated to define and assign account keys:

The data TRANSFER ROUTINES are categorized as:

•  Orders.
•  Deliveries.
•  Billing DOCUMENTS.
•  Sales activities.
•  Shipping units.
•  Texts.
•  TEXT names.
•  Shipments.

The data transfer routines are categorized as:

The general rule of AVAILABILITY of requirements and DATA TRANSFER routines are as follows:

•  Copying requirements are available to be assigned during transfer of data between documents and texts.
•  Data transfer routines are available during copying between documents and texts.
•  Requirements are available to be assigned to any access sequence as WELL prior to most FUNCTIONS.
•  Formulae are available to be assigned during pricing determination.

The general rule of availability of requirements and data transfer routines are as follows:

The following menu path is NAVIGATED to define dependencies of REVENUE ACCOUNT determination:

• Customizing Implementation GUIDE (IMG Menu)->Sales and Distribution->BASIC Functions->Account Assignment/Costing-> Revenue Account Determination->Define Dependencies of Revenue Account Determination.

The following menu path is navigated to define dependencies of revenue account determination:

The following menu PATH is NAVIGATED to define tax determination RULES in SD:

• CUSTOMIZING Implementation GUIDE (IMG Menu)->Sales and Distribution->Basic Functions->Taxes-> Define Tax Determination Rules.

The following menu path is navigated to define tax determination rules in SD:

The tax determination is performed automatically by system. The tax determination is based on the structure of the organization, country, region or city of the plant DELIVERING the PRODUCTS and the country of the receiving customer. It WORKS in coordination with the tax RELEVANCY indicators on the customer master record and material master record. CONDITION Technique is used for tax determination procedure.

The tax determination is performed automatically by system. The tax determination is based on the structure of the organization, country, region or city of the plant delivering the products and the country of the receiving customer. It works in coordination with the tax relevancy indicators on the customer master record and material master record. Condition Technique is used for tax determination procedure.

The condition supplement is a GROUP of conditions that is applied EVERY time a condition is matched condition supplements will COME for a condition if you have maintained pricing PROCEDURE under master data of the condition.

The condition supplement is a group of conditions that is applied every time a condition is matched condition supplements will come for a condition if you have maintained pricing procedure under master data of the condition.

The following menu PATH is NAVIGATED to MAINTAIN condition exclusion group:

• Customizing Implementation Guide (IMG Menu)-> SALES and Distribution-> Basic Functions-> Pricing-> Condition Exclusions-> Condition Exclusion for Groups of Conditions->Define Condition Exclusion Groups.

The following menu path is navigated to maintain condition exclusion group:

The condition exclusion GROUP is a technique to ensure that the customer does not receive all TYPES of discount; rather, the customer RECEIVES the BEST discount out of all GIVEN discount condition types. A best condition type is chosen from this "Condition Exclusion Group" based on your configuration.

The condition exclusion group is a technique to ensure that the customer does not receive all types of discount; rather, the customer receives the best discount out of all given discount condition types. A best condition type is chosen from this "Condition Exclusion Group" based on your configuration.

We can ACTIVATE pricing for ITEM CATEGORY by navigating the following menu path:

1. Customizing Implementation Guide (IMG Menu)->SALES and Distribution->Basic Functions-> Pricing->Pricing Control-> Define Pricing by Item Category->Activate Pricing for Item Categories.

We can activate pricing for item category by navigating the following menu path:

The following TOPICS in SD have impact on pricing procedure:

•  Credit MANAGEMENT.
•  PAYMENT terms.
•  COST of Sales.
•  Rebate.

The following topics in SD have impact on pricing procedure:

PERFORM the FOLLOWING steps (in sequence) to CUSTOMIZE Pricing Procedure:

1. Put the required fields into the field catalog.
2. CREATE the required condition tables.
3. Create the required access sequence.
4. Assign the condition tables to the access sequence.
5. Create the condition types.
6. Assign the access sequence to the condition types.
7. Create the determination procedure, if necessary, and assign the condition types to it.
8. Assign the determination procedure.
9. Lastly, create the condition RECORDS.

Perform the following steps (in sequence) to customize Pricing Procedure:

Navigate the FOLLOWING menu PATH to begin with defining and assigning pricing procedures:

• Implementation Guide (IMG Menu)->SALES and Distribution->Basic Functions->Pricing ->Pricing Control-> Define and ASSIGN Pricing Procedures->MAINTAIN Pricing Procedures.

Navigate the following menu path to begin with defining and assigning pricing procedures:

The following three rounding rules are AVAILABLE while maintaining condition TYPES:

•  Commercial rounding — In case of commercial rounding, a value less than 5 is rounded down to nearest value while the values greater than 5 is rounded up to the nearest value.
• Always ROUND up — In this case, regardless of the fact whether it is greater than or less than 5, the value is always rounded up to the nearest value.
•  Always round down — In this case, regardless of the fact whether it is greater than or less than 5, the value US always rounded down to the nearest value.

The following three rounding rules are available while maintaining condition types:

The condition technique is the most important technique used for configuration in the Sales and DISTRIBUTION module. It is used for different types of determinations in SD such as pricing, text DETERMINATION, output determination, account Determination and material determination. It is called condition technique, because it provides a technique to select one from alternative choices, BASED on conditions, access sequence and condition tables.

The condition technique is the most important technique used for configuration in the Sales and Distribution module. It is used for different types of determinations in SD such as pricing, text determination, output determination, account Determination and material determination. It is called condition technique, because it provides a technique to select one from alternative choices, based on conditions, access sequence and condition tables.

The FOLLOWING are the USER EXITS for PARTNER DETERMINATION:

•  EXIT_SYSTEMLV09A_001.
•  EXIT_SYSTEMLV09A_002.
•  EXIT_SYSTEMLV09A_003.
•  EXIT_SYSTEMLV09A_004.

The following are the user exits for partner determination:

The following menu PATH can be navigated to view all the enhancements in the system:

• SYSTEM Menu ->TOOLS ->ABAP WORKBENCH ->UTILITIES ->Enhancements -> Definition.

The following menu path can be navigated to view all the enhancements in the system:

The TRANSACTION code SMOD can be USED to view all the ENHANCEMENTS in the SYSTEM.

The transaction code SMOD can be used to view all the enhancements in the System.

The empty ABAP forms at particular points in the standard SYSTEM, where the system ALLOWS customers to make enhancements to the WAY the CODE functions are called user EXITS. These are helpful tools to meet the specific business requirements.

The empty ABAP forms at particular points in the standard system, where the system allows customers to make enhancements to the way the code functions are called user exits. These are helpful tools to meet the specific business requirements.

The purpose of CONDITION index is to search all records for a specific condition TYPE. For example, you can search all the condition records for the condition type PR00 condition type. You can activate the condition index in the customizing screen for the condition Type PR00 by navigating the following MENU path:

• SPRO->Sales & Distribution->Basic Functions->Pricing->Pricing Control->Deflne Condition TYPES-> Maintain Condition Types-> Enter PROO.

The purpose of condition index is to search all records for a specific condition type. For example, you can search all the condition records for the condition type PR00 condition type. You can activate the condition index in the customizing screen for the condition Type PR00 by navigating the following menu path:

The terms of payment that a company offers to a customer based UPON which a DISCOUNT may be given for PROMPT payment or penalties can be CHARGED in case of late payment made is known "Payment Terms".

The terms of payment that a company offers to a customer based upon which a discount may be given for prompt payment or penalties can be charged in case of late payment made is known "Payment Terms".

The FOLLOWING are the TRANSACTION codes in the CONTEXT of REBATE agreement processing:

•  VBOl—Create.
•  VB02 —Change.
• VB03 —Display.

The following are the transaction codes in the context of rebate agreement processing:

Yes, you can PERFORM availability CHECK in MM by excluding a STORAGE LOCATION.

Yes, you can perform availability check in MM by excluding a storage location.

Perform the following steps to set a Distribution Channel as default for the transaction field that requires distribution channel DATA:

1. Use the SU01 transaction CODE and enter the USER ID.
2. Go to the parameters tab page and add VTW parameter.
3. Enter the default Distribution Channel in the parameter VALUE.

Perform the following steps to set a Distribution Channel as default for the transaction field that requires distribution channel data:

Subtotals are generally used in PRICING PROCEDURES. Subtotals are not tied to condition types. However, you can control the value entered in the FIELDS by ASSIGNING subtotals within the pricing PROCEDURE.

Subtotals are generally used in pricing procedures. Subtotals are not tied to condition types. However, you can control the value entered in the fields by assigning subtotals within the pricing procedure.

In such a PROBLEM, you should generate the INFO STRUCTURE and update group again for the client in which your Error Message is DISPLAYED.

In such a problem, you should generate the Info structure and update group again for the client in which your Error Message is displayed.

REBATE refers to a specific DISCOUNT given to a specific customer for Sales within a specific period of time. For example, a customer GETS 2% discount on buying 500 kgs in a particular month and another customer gets 5% discount on buying 2000 kgs in the same month.

Rebate refers to a specific discount given to a specific customer for Sales within a specific period of time. For example, a customer gets 2% discount on buying 500 kgs in a particular month and another customer gets 5% discount on buying 2000 kgs in the same month.

USER Exits are used in case there are some specific needs which are not MET by the Standard System. The purpose of user exit is to ADD a particular business-related FUNCTIONALITY to standard SYSTEM.

User Exits are used in case there are some specific needs which are not met by the Standard System. The purpose of user exit is to add a particular business-related functionality to standard SYSTEM.

A user exit is IMPLEMENTED as a call to a function module. A customer's developer can access DATA objects and program components with the help of user exit. User Exits are USED in CASE there are some SPECIFIC needs which are not met by the Standard System.

A user exit is implemented as a call to a function module. A customer's developer can access data objects and program components with the help of user exit. User Exits are used in case there are some specific needs which are not met by the Standard System.

The following are the standard OUTPUT TYPES in the SD module:

•  SALES ORDER Confirmation —BAOO.
•  Outbound Delivery Note —LDOO.
•  Billing document —RDOO.
•  Inquiry —AFOO.
•  Quotation —ANOO.
•  Contract —KO00.

The following are the standard output types in the SD module:

The FOLLOWING are the Customer TABLES of the SYSTEM SD module:

•  KNA1 — general data.
•  KNB1 — customer master.
•  KNB4— customer payment history.
•  KNB5— customer master.
•  KNBK— bank data.
•  KNKA — credit management.
•  KNKK— credit control area data.
•  KNVI— SALES area data.
•  KNVP— Partner Function KEY.
•  KNVD__output type.
•  KNVS__customer master ship data.
•  KLPA__customer vendor link.

The following are the Customer tables of the SYSTEM SD module:

The existing problem is CALLED number range BUFFERING. You need to perform the following STEP:
Transaction code->SNUM->debitor-> CHANGE MODE and change the numbers.

The existing problem is called number range buffering. You need to perform the following step:
Transaction code->SNUM->debitor-> change mode and change the numbers.

The menu path to define the PRODUCT hierarchies is:

• IMPLEMENTATION Guide (IMG Menu) -> Logistics-General -> MATERIAL Master -> SETTINGS for Key Fields -> DATA Relevant to Sales and Distribution -> Define Product Hierarchies [OVSV].

The menu path to define the product hierarchies is:

The menu PATH to assign a Sales area to the CUSTOMER Hierarchy is:

• Implementation Guide (IMG Menu)->Customer Hierarchy-> Assign Sales AREAS.

The menu path to assign a Sales area to the Customer Hierarchy is:

The customer hierarchy can be DEFINED for the FOLLOWING:

•  Customer Master.
•  Sales Document Header.
•  Sales Document ITEM.
•  Delivery.
•  Shipment.
•  Billing Header.
•  Billing Item.
•  Sales ACTIVITIES (CAS).

The customer hierarchy can be defined for the following:

The menu PATH to set the partner determination for hierarchy categories is:

• Implementation Guide (IMG Menu)->Sales and Distribution->Master DATA->Business Partners-> CUSTOMERS -> Customer Hierarchy->Set Partner Determination for Hierarchy Categories.

The menu path to set the partner determination for hierarchy categories is:

The MENU PATH to DEFINE the customer hierarchy types is:

• Implementation GUIDE (IMG Menu)->Sales and Distribution->Master Data ->Business Partners -> Customers -> Customer Hierarchy -> Define Hierarchy Types.

The menu path to define the customer hierarchy types is:

A CUSTOMER can be blocked by NAVIGATING the following menu PATH:

• SYSTEM Menu->LOGISTICS->Sales and Distribution->Master Data->Business Partner->Customer-> Block [VD05].

A customer can be blocked by navigating the following menu path:

The customer master record in the shipping screen and in the Sales document type is USED to SPECIFY shipping conditions. The shipping conditions are used to DECIDE the shipping point by copying them into the Sales document during order CREATION.

The customer master record in the shipping screen and in the Sales document type is used to specify shipping conditions. The shipping conditions are used to decide the shipping point by copying them into the Sales document during order creation.

The MASTER RECORDS from which a SALES order receives the master data are as follows:

•  Customer Master RECORD.
•  Material Master Record.

The master records from which a Sales order receives the master data are as follows:

You can BLOCK the transaction for a MATERIAL FLAGGED for deletion by customizing the Sales STATUS feld in the Sales organization VIEW of the material master.

You can block the transaction for a material flagged for deletion by customizing the Sales status feld in the Sales organization view of the material master.

It means to transfer the legacy DATA to the newly installed & CONFIGURED System. The data such as customer and material maintained by an ORGANIZATION before the installation of ERP System is known as the legacy data. You can use various tools to transfer the legacy data to the System, such as Batch Data Communication (BDC) and Legacy System Migration Workbench (LSMW) PROGRAMS.

It means to transfer the legacy data to the newly installed & configured System. The data such as customer and material maintained by an organization before the installation of ERP System is known as the legacy data. You can use various tools to transfer the legacy data to the System, such as Batch Data Communication (BDC) and Legacy System Migration Workbench (LSMW) Programs.

The T.Code SE91 is USED to VIEW all MESSAGES in SYSTEM.

The T.Code SE91 is used to view all messages in SYSTEM.

The FOLLOWING are certain T-codes USED to create and manipulate Customer master:

•  XD01 — CREATES a customer.
•  XD02— Changes a customer.
•  XD03— Displays a customer.
•  XD04— Changes customer changes centrally.
•  XD05- Blocks a customer centrally.
•  XD06— Marks a customer for deletion.
•  XD07— Changes a customer Account Group.
•  XD99— Maintains customer maintenance.
•  XDN1 — Maintains number RANGES for a customer.

The following are certain T-codes used to create and manipulate Customer master:

The following MENU path is navigated to define regional tax codes:

• CUSTOMIZING Implementation Guide (IMG Menu) -> Sales and Distribution -> Basic FUNCTIONS -> Taxes -> Define Regional Codes -> Define COUNTY Code.

The following menu path is navigated to define regional tax codes:

The following menu PATH is navigated to define tax RELEVANCY of the master record:

• Customizing Implementation Guide (IMG Menu)->Sales and Distribution->Basic FUNCTIONS->Taxes->Define Tax Relevancy of Master Records->Material Taxes.

The following menu path is navigated to define tax relevancy of the master record:

The underlying System USES the following sequence of steps to DETERMINE tax number and tax classification:

1. If the PAYER has a VAT REGISTRATION number and is identical to the sold-to party, the tax number and tax classification are copied from the payer. The tax number is copied on the basis of the "country of DESTINATION relevant for taxes."
2. If step 1 does not apply and If the Ship-to Party has a VAT registration number and the Sold-to Party does not have the same, tax number and tax classification are copied from the Ship-to Party.
3. If step 2 does not apply, then tax number and tax classification are copied from the Sold-to Party.

The underlying System uses the following sequence of steps to determine tax number and tax classification:

We NEED to make SURE that for all the countries in the OVK1, we have defined a tax category. At the same time we also need to VERIFY whether the tax CLASSES are defined in OVK3 and OVK4.

We need to make sure that for all the countries in the OVK1, we have defined a tax category. At the same time we also need to verify whether the tax classes are defined in OVK3 and OVK4.

While working on INTER COMPANY SALES, the transaction CODE MM01 is used to CREATE material related to the plant and Sales organization. For the other company code, this material can be extended if the server being used is common.

While working on Inter Company Sales, the transaction code MM01 is used to create material related to the plant and Sales organization. For the other company code, this material can be extended if the server being used is common.