I have a fixed amount discount condition type, which I need to establish a constant discount for all possible values. For a value of $100, a discount of $3. For a value of $200, a discount of $6. For a value of $300, a discount of $9, and so on. The problem is that I cannot maintain this scale at VK11 for all possible high values. I need to determine that for each $100 there is a $3 discount. How do I configure this?
A: Follow these steps:
(1) new routine in VOFM -> Formulas -> Condition value. There you divide the quantity by 100 and multiply the integer part of the result by 3.
(2) new condition - calculate type - G-formula.
(3)Input condition in your pricing procedure and input AltCTy (Condition formula for alternative calculation type) - new formula.
I have two condition types for cost. One is customized and the other is VPRS. Their values are determined Correctly in the sales order. A problem arises when I create the d/o and billing document. The condition type VPRS is incorrect with value '0,' while the customized one is correct. What is the cause of this? A: The VPRS is a valuation condition, normally the cost of goods sold. If it comes from the material master record, it is a standard valuation price. However, if it comes from the information record, it is the very cost of goods sold. You may have a difference from the price you valued your material at and the real cost of purchase. Check if you have a standard value in your master record or if you have a relevant info record. Another possibility is your customized condition is Undoing The VPRS.
If you want to enrich your career and become a professional in SAP SD, then visit Tekslate - a global online training platform: "SAP SD Training" This course will help you to achieve excellence in this domain
Case: We create an order for a sales BOM with three sub-items. Since the sub item components must not be delivered without the main product we declared the main item category as a delivery group. The problem arises when there is zero availability for the main item and no schedule line can be confirmed. The main item is defined as a delivery group but the delivery is created without the main and only the component sub-items. The delivery group becomes broken up. This occurs only in VL01N and VL10 dialogue mode. In the VL10 background, it works ok, so no delivery item is created at all for those unconfirmed items. How do we fix this? A: The message is not configurable; at least in releases <= 4.6. But you can change the 'W' to an 'E' with a modification.
Case: I can press actual PGI successfully even without stock, but I know that is the wrong way to do so. The correct scenario should have enough stock then press actual PGI. How can I configure this? A: You must make sure you do not allow negative inventory in MM.
Stock Transfer
How do we transfer stocks under one company code From plant to plant? A: Plant to plant is handled using MB1B. If stock Transfer orders with deliveries are configured, use ME27.
Pop up in Order Creation
When I create a sales order using VA01, a pop up appears saying, "for this customer, there are open quotations". I would like to disable that pop-up. How would I do that? A: You can change this by checking order header configuration (VOV8), and field quotation messages.
VPRS Not Copied to Billing Document
I have two condition types for cost. One is customized and the other is VPRS. Their values are determined correctly in the sales order. A problem arises when I create The d/o and billing document. The condition type VPRS is incorrect with value '0,' while the customized one is correct. What is the cause of this? A: The VPRS is a valuation condition, normally the cost of goods sold. If it comes from the material master record, it is a standard valuation price. However, if it comes from the information record, it is the very cost of goods sold. You may have a difference from the price you valued your material at and the real cost of purchase. Check if you have a standard value in your master record or if you have a relevant info record. Another possibility is your customized condition is Undoing the VPRS.
Ans: Posting Keys are defined at Client Level. Posting keys determine whether a line item is a debit or credit as well as the possible field status for the transaction. In this context, it is essential to understand the factors that determine the field status of a transaction. The field status within a FI document is controlled by Account Type, field status of Posting Key and the field status of the G/L account.
Ans: Cumulative Condition Record is a field that Condition Update during configuration for a condition type that has anything to do with the cumulative condition records.
Ans: The Enterprise organization chart shows the organizational structure of an enterprise, its organization units, and how they are related. A combined structure can be created from the point of view of accounting, MM, SD. This structure forms a framework in which all business transactions can be processed.
Ans: Text determination: For transferring information from material or customer to order/delivery or invoice (and anything in between)
Account determination: For transferring financial and costing information to proper financial docs
Partner determination: For determining who is legally responsible for who the goods are going to and whatever else you want to drive through this functionality.
Output determination: What kind of output does a sales/delivery/billing document create and who gets it.
Ans: The agenda of the quick-off meeting was
Serial Numbers in a Delivery Document Which report will show the serial number assigned in a delivery document? A: Take a look at function modules with SERIAL_*. For example, SERIAL_LS_PRINT.
Ans: There are 16 fields in the pricing procedure In
SAP SD Pricing
Ans: Enterprise organization diagram. Chart showing the organizational structure of an enterprise, its organization units and how they are related. A combined structure can be created from the point of view of accounting, MM, SD. This structure forms a framework in which all business transactions can be processed.
Ans: Sales organization: An organizational unit that sells and distributes products, negotiates terms of sale and is responsible for these transactions.
Distribution channel: Channel through which salable materials or services reach customers. Typical distribution channels include wholesale, retail, and direct sales. You can assign a distribution channel to one or more sales organizations.
Division: Product groups can be defined as a wide-ranging spectrum of products. For every division, you can make customer-specific agreements on, for example, partial deliveries, pricing, and terms of payment. Within a division, you can carry out statistical analyses or set up separate marketing.
Ans: Sales Office: Geographical aspects of the organization in business development and sales are defined using the term sales office. A sales office can be considered as a subsidiary. Sales offices are assigned to sales areas. If you enter a sales order for a sales office within a certain sales area, the sales office must be assigned to that area.
Sales Group: The staff of a sales office may be subdivided into sales groups. For example, sales groups can be defined for individual divisions.
Salespersons: Individual personnel master records are used to manage data about salespersons. You can assign a salesperson to a sales group in the personnel master record.
Ans: Business Area. The system posts costs and revenue according to the business area.
The business area can be equivalent to the:
Sales area (if the accounts are to be posted according to sales) plant/division (if the accounts are to be posted according to products) The business area is defined in Customizing for Sales.
Business area. A unit in an enterprise, grouping product and market combinations as homogeneously as possible for the purpose of developing unified business policy.
Financial Accounting (FI). A business area is an organizational unit within financial accounting which represents a separate area of operations or responsibilities within an organization. Financial accounting transactions can be allocated to a specific business area.
Ans: Many to One.
Ans: Purchasing Organization.
Ans: Many to Many.
Ans: Many to Many to One.
Ans: Yes in CO.
Ans: Credit control area: Organizational unit in an organization that specifies and checks credit limits for customers. A credit control area can include one or more company codes. It is not possible to assign a company code to more than one credit control areas.
Ans: Shipping Point: Organizational unit at a fixed location that carries out shipping activities. A shipping point could, for example, be a company's mail department or a plant's rail depot. Each delivery is processed by only one shipping point.
Ans: Organizational unit within Logistics, serving to subdivide an enterprise according to production, procurement, maintenance, and materials planning aspects.
A plant is a place where either materials are produced or goods and services provided.
Classification: Business object
Structure: A plant can assume a variety of roles: As a maintenance plant, it includes the maintenance objects that are spatially located within this plant. The maintenance tasks that are to be performed are specified within a maintenance planning plant. As a retail or wholesale site, it makes merchandise available for distribution and sale. As a rule, the plant is the organizational unit for material valuation.
The preferred shipping point for a plant is defined as the default shipping point, which depends on the shipping condition and the loading condition. For the placement of materials in storage (stock put-away), a storage location is assigned to a plant. The storage location depends on the storage condition and the stock placement situation.
The business area that is responsible for a valuation area is determined as a function of the division. As a rule, a valuation area corresponds to a plant.
Ans: Yes.
Ans: Sales Organizations.
Ans: SD: Sales Organizations. M: Plant PP: Plant FI: Company Code CO: Controlling Area
Ans: A plant can be subdivided into storage locations, allowing stocks of materials to be broken down according to predefined criteria (e.g., location and materials planning aspects).
A plant can be subdivided into locations and operational areas. Subdivision into locations takes geographical criteria into account, whereas subdivision into operational areas reflects responsibilities for production.
Ans: Yes.
Ans: Many.
Ans: None.
Ans: Plant & Storage Location. Sales and Distribution - Transfer of Requirements The MRP department is informed about the quantities and deadlines by which incoming orders should be delivered. The system checks the availability of the goods based on the requested delivery date of the customer and creates MRP records which contain all necessary information for passing on to planning. It ensures that the goods are available in time for the delivery. Materials planning transfers the reporting requirements and creates orders or purchase requisitions from them etc. For controlling transfer of requirements, you have to carry out the following steps: 1. Each requirement type has to be allocated to one requirement class only.2. The transfer of requirements must be switched on at requirements class level, the sales documents at schedule line level.3. You must define a check group. It is possible to have this check group proposed for the initial creation of a material master record.4. Note that a plant must exist for the transfer of requirements to be carried out at the document item level. OVZG - Requirement class It specifies the following points: - whether an availability check and a transfer of requirements are carried out for a transaction (for sales documents, fine-tuning using the schedule line category is possible),- whether the requirements are relevant for MRP,- the allocation indicator from the sales view which controls the settlement of customer requirements with requirements - whether an item is to be settled to an auxiliary account assignment,- the settlement profile,- the results analysis key. (Use transaction SM30 for V_* configuration)OVZH - Requirements typeV_TVEPZ_V - Assignment of requirement type to TransactionV_TVEP_V - Schedule line category OVZ2 - Define Checking GroupV_TMVFU - Define the checking group that the system proposes when you create a new material master record. You can overwrite the default value for the checking group in the material master record.
Ans: Sales Status field in the sales organization view of the material master may be used to block any transaction for the material.
Ans: Exchange rate gets copied from the customer master record. Exchange rate types are to be maintained for the customer in the sales screen of the customer master record.
Shipping
Ans: In order to use the Packing list PL00 (packing slip in delivery) you must do 'Packing' in the delivery note (edit->packing).
Ans: When you are releasing a sales order, choose Sales document -> Subsequent functions-> Create delivery, then the shipping point will be brought in from the sales order. In all other scenarios you have to key in the shipping point. The above-described scenario will only work if all items on the sales order are to be shipped from the same shipping point.
Billing
Ans: Make the non-stock material deliverable, but not pickable. Both items will carry into the delivery, and therefore appear on the same invoice.
Change the copy rule for orders->invoices and deliveries->invoices to specify that invoice combination is permitted. However note that for system to create combined invoices, PO number, payment terms, sales organization, and distribution channel must be identical. Else undesirable combinations may be created by the system.
Pricing Conditions
Ans: The field used to look up at the price is defined in the Access sequence. You may find a step with PMATN as a material number. If you insert a step with MATNR then the system will first look for the material, if not found (use the exclusion tick box) it will look for the pref.
Customizing
Ans: Assign output determination procedure to the header of the document and the output type.
Ans: IMG->Fin. Acct.>AR and AP ->Customer acct>Master Record -> Prepare to Create Customer-> Define Acct. Group.
Ans: Use an item category that is configured for bills of material for having a sales BOM to explode automatically.
Standard SAP item categories are :
TAQ - Pricing and inventory control take place at the BOM header level TAP - Pricing and inventory control take place at the BOM item level These can be automatically derived using the item category groups ERLA and LUMF, respectively.
Ans: Logistic General-> Logistics Basic Dat Business Partners -> Customers -> Control -> Define account groups and field selection for customer
Choose Customer Acct. GR. (double-click). -> Field Status: Sales data (double click) -> sales (double click) .Check the radio button against Customer Gr as REQ. ENTRY. Save the settings to make customer GR entry mandatory.
Ans: Use user exit MCP20001 and include ZXSOPU01.
Ans: These are the condition type that will display the results of the unit costing for a certain type of sales documents.
EK01 : If you use this condition type, the result of unit costing is issued to the first position on the conditions screen for the item. The value can be used as a basis for price determination.
EK02: If you use this condition type, the result of unit costing is simply a statistical value which you can compare with the price.
Please note the following points :
1) The condition type must have condition category 'Q' (costing).
2) The condition type must agree with the condition type defined for unit costing in the pricing procedure.
Ans: Need to change the validity of the condition record for the condition type K007 defining it not valid for that particular 2 months. And also the settings of the Requirements as it is correct that it overrules the exclusion.
Accumulate the number of condition types in accounting document
To accumulate the number of condition types in accounting documents without affecting the pricing display in the billing document.
As an illustration:-
ZPXX 3500 ZDXX 1000- ZWXX 500-
(all condition types are shown separately in the pricing view)
Journal: Dr. Vendor 2000 Cr Sales 2000 (ZPXX - ZDXX - ZWXX)
One way to do it is:-
Mark the condition types you want to group as statistical and remove the account assignment key.
Create a subtotal in your pricing procedure that will add them together and put in the account assignment key for it. This way the individual components will still display on your pricing screen but FI will only get one posting.
For In-depth knowledge on SAP SD click on:
You liked the article?
Like: 0
Vote for difficulty
Current difficulty (Avg): Medium
TekSlate is the best online training provider in delivering world-class IT skills to individuals and corporates from all parts of the globe. We are proven experts in accumulating every need of an IT skills upgrade aspirant and have delivered excellent services. We aim to bring you all the essentials to learn and master new technologies in the market with our articles, blogs, and videos. Build your career success with us, enhancing most in-demand skills in the market.
