Cash less discount

Hello Everbody!
Required is to not grant "cash less discount" for SD Sales Orders
for amounts less than 100 Euro. How can this requirement being
implemented ?
Thx
Ilhan Ertas

Hi Ilhan,
Pls write a requirement routine and assign it to the condition type.
In the reqmt routine, you can mention the minimum criteria for the condition type to have a value. i.e. the net value of the sales order to be morethan 100Euro.
In such case, the condition records will be read only if the total value ofthe sales order is morethan 100euros.
Pricing routines are created in transaction code VOFM. If you create a routine, dont forget to execute the program RV80HGEN in everyclient after the routine is transported to the new client.
Reward if the solution helps.

Similar Messages

FF7B Discount issue

Hi,
When running FF7B, Liquidity Forecast report, Vendor Invoices are showing the discounted amount even after the expiry of the cash discount period.
The early discount is an option that company have, they can either take the discount or elect to pay the full amount of the invoice at the later due date.
When the invoice is booked, the Liquidity Forecast Report "plans" the discount will be taken and forecasts the net amount (gross less discount). However when the discount date is passed, the report should show the gross amount.
Appreciate any help with this
Thanks
Kind regards

I think u have not understand the question.
I have assigned my DISCOUNT PAID a/c in OBXI (SKT), DISCOUNT RECIEVED a/c in OBXU (SKE), DISCOUNT CLEARING a/c in OBXV (VSK) & OBXA (SKV). Am using net procedure to calculate discount. For disc recieved and disc paid g/l's, i have given post automatically option. Assigned my payment terms to my vendor and customer. While we make a vendor invoice, the disc amt posts to disc clearing a/c as open item and once we make payment, the open item in disc clearing g/l is cleared by another posting. My Question is why the disc what we recieved is not getting posted to the disc recieved a/c likewise in the case of customer invoice, the paid disc only getting posted to disc clearing a/c and not to disc paid a/c. Then what is the use of assigning disc recieved and disc paid g/l's to OBXI and OBXU. Am asking this coz i have already tried the same few weeks ago, it got posted and now its not working. So suggest me some config steps.
Thanks & Regards
Manoj

Cash Discout Lost

Hello All,
I am facing an issue related to cash discount lost during payment run.
1.The document date on the Invoice is 04/29/2010.
2.The posting of the document happens on 05/07/2010 (mmddyyyy).
3. The total amount of the Invoice is 57000
4.The payment term is defined as 10 days 2%, Due net 15 days.
5. The Payment run is done 05/07/2010 (mmddyyyy).
Issue: The system is calculating the Cash Discount of 1140, despite the fact that the Cash Discount is available till 05/09/2010. Please help in understanding Why has system considered That the Cash discount is lost on the Invoice despite the fact it is available till 05/09/2010.
Thanks
Nitin

Thanks raghu.
Yes we are posting document net of cash and discounts.
Actually we have not done the payment yet.
We have just genereated the Payment proposal and the system is showing us the Lost cash discount of 1144. I hope it may give you some lead on the issue.
Regards
Nitin

DIscount condition types mapping to value field (+/-)

Hi,
1)While mapping SD condition types to Copa value fields, do we need to check the transfer +/- symbol for all discount condition types...
or when do we need to check it..
2) In our case we have some 4 to 5 discount condition types mapped to copa... If we check that symbol, as discount will always be negative system is posting discount values in negative in copa. At the time of report execution, since we give formula as Sales Less discount and discount is already negative in system it is getting added... so we are planning to change formula as sales + discounts... is that approach is right?
Reg
Karthik

Hi Ajay,
Thanks for your quick reply... generally for which condition types do we need to check this indicator in ke4i... for all discount condition types and rounding off condition types... is that right? Because as I told we have some 4 to 5 discount condition types and we have ticked for only one discount condition type which is mostly used...
Reg
Karthik

Price Comparision not for RFQ

Hi,
My client requirement is to compare the price with following pricing elements before creating the PO
we are not creating RFQ's here ,when we enter below values for each vendor, it should dispay the report as it shows in ME49
Basic Value
Less discount
Add excise duty
Add cst/vat
Add frieght
less monthly discount
if you have functional spec for the above report pls share with me
Thanks,
Zeeshu

Hi,
In standard system ME49 considers net price, delivery cost and
cash discount only.
So it is not possible to have tax amount included in price comparison.
In order to have payment terms included in price comparison please
kindly ensure that the flag 'Include discounts' is ticked ON in ME49.
The help message on the 'Include discounts' flag in ME49 will help to
understand the usage of the flag. When this flag is enabled, the value
set under the condition type SKTO (Cash Discount) is taken into
account. This discount can be availed based on the terms of payment
with the vendor, which can be set in header data screen of the
quotation maintenance.
To summarise, the 'Include discounts' flag is for including Cash
discounts realised by prompt payment.
Regards,
Edit

Help me on tthese issues

Hai Friends,
<b>1)
Kindly help me toughest tickets in SD with clear explanation....
i lost many interviews because of this ....
2)
kindly through customization on pricing
3)
what is significance of account assignment grp in SD?
4)can we have credit mangement only at order level or only at delivery level?
5)toughest GAP analysis u faced in implementaion
6) generally how many types of pricing scenarios will be there in normal implamentaion?
Mail me at [email protected]
</b>
i reward suitably***
Thanks a lot in Advance
Venkat

Hi Venkat,
PRICING SD:
PRICING:
Pricing is the combination of creating correct pricing procedure that map the business needs & processes, such as correct pricing & discounting, & keeping to the legal requirements placed on the business, such as adhering to the tax laws of the country.
SPRO- IMG- SD- Basic Functions- Pricing- Pricing Control
Create Condition Table: V/03, V/04, V/05
Define Access Sequence: V/07
Define Condition Types: V/06
Define & Assign Pricing Procedure
Maintain Pricing Procedure: V/08
Define CuPP: OVKP
Define DoPP: OVKI. The DoPP indicator is used to determine pricing in conjunction with the sales area & CuPP.
Assign DoPP to Order Types & Billing Types: OVKJ & OVTP
Define Pricing Procedure Determination: OVKK
Create Condition Table: V/03, 04, 05
Put the most general field for e.g., Sales Orgn in the highest position & the most specific field in the lowest. After organizational fields, place fields from doc header before those that come from item level (customer comes before material).
Sales Orgn, Distbn Channel, Div, Cust, Mat: Customer Specific Price
Sales Orgn, Distbn Channel, Div, Price List Type, Mat: Price List
Sales Orgn, Distbn Channel, Div, Mat: Material Price.
Maintain Access Sequence: V/07
Go to new entries, define 4-digit acc seq. Select acc seq, go to Accesses and place the cond tables and check exclusive indicator (which determines that if a cond record is successfully found, the system will stop searching further). Select each cond table and go to Fields.
There are some cond types for which you do not create cond records (header discounts that you can only enter manually). These cond types do not require an access sequence.
Define Condition Type: V/06
They are used in the pricing procedure to define how the cond is going to perform, such as either a %tage or a fixed amount. The cond type can be automatic or it can allow manual changes. Copy the required cond type and rename. Then assign acc seq to cond type.
If you use different calculation types for what are otherwise the same conditions (for e.g., %tage, as fixed amt, qty dependent), you do not have to define different cond types in customizing. You can set different calculation type when maintaining cond records.
Functionality of Condition Types:
Access Sequence
Condition Class: surcharge & discounts or prices
Plus/Minus: -ve, +ve or both
Calculation Type: fixed amt, %tage, qty, wt, voln
Rounding rule: commercial, round up and round down
Group Cond
Manual Entry: whether manual or automatic entry has priority
Header Cond: after entering the header cond type click on the button activate. The cond amt of the header conditon is copied as it is to all the line items in the doc.
Item Cond
Amount/ Percent: check & u can change the amount or % for the cond type during data processing
Delete: check & the cond record may be deleted from the doc.
Value: check & the value of the cond type can be changed during data processing
Calculation Type: check & the cal type can be changed during doc processing
Valid from & to
Scale Basis: determines how the system interprets a pricing scale in a cond, for e.g., the scale can be based on qty, wt, voln
Check Value: indicates whether the scale rates must be entered in ascending or descending order.
Define and Assign Pricing Procedure: V/08
A pricing proc consists of a lists of cond types in a defined order, such as price less discount plus tax. Go to new entries, define 6-digit pricing proc with descp. Select the 6-digit pricing proc and go to Control Data, you will be faced with an empty structure.
Step: the no that determines the sequence no of a cond type with in a procedure
Counter: second mini step with in an actual step
Conditon type: specify the cond type
From & To: if you specify the ref steps in these fields, the cond values of the 2 steps specified and steps in between are totaled
Manual:
Mandatory: whether a cond type is mandatory when system carries out pricing
Statistical: the value represented in this step will not alter the overall value
Print: which cond types should be printed on a doc (order confirmation, invoices)
Subtotal: controls whether & in which fields the cond amts or subtotals are stored
Requirement: for a cond type to be executed in the sales doc the requirement specified here must be satisfied. (It is a gateway)
Alternative Calculation Type: alternative formula to the formula in the std system that determines the cond. In the std SAP system for the cust expected price EDI1, the alt cal type is 9, which means it contains a routine with a logic which states that the difference between the customer expected price & the net value is zero.
Alternative Cond Base Value: alternative formula for determining the cond basis (amt to which the discount or surcharge in a scale refers)
Account Key: this field enables the system to post the sales value to different G/L accounts. ERL: sales revenues, ERS: sales deductions, ERF: freight revenue.
Accruals: this is exclusively for rebate cond types BO01 & BO02. Key, which identifies various types of G/L accounts for accrual postings.
TAX: MWST
Tax is calculated on the following parameters:
Plant
Ship to party region
Customer tax classification
Material tax classification
Pricing Procedure Determination: OVKK: Determination Rule
Before one can proceed with the determination rule, one needs to maintain the CuPP & DoPP. One needs to assign a single character alphanumeric key with a short descp. Then assign the DoPP to the sales doc types. This will ensure that for e.g., all sales orders created using order type OR, which has been assigned a DoPP of 1, will all use the same pricing proc if created in the same sales area & with the same CuPP. In some instances, you may not want to have the same pricing proc for a sales doc, as you may want in a billing doc. For this reason, you may allocate a different DoPP to a billing doc.
Do not forget to assign the CuPP indicator to your CMD in the Sales Screen
Sales Orgn + Distbn + Division + CuPP indicator + DoPP indicator = Pricing Procedure
To Create own Sales Doc Types:
SPRO- IMG- Sales Doc- Sales Doc Header-
Define sales doc types: VOV8. Copy std order type& rename
Assign Sales area to Sales Doc Types:
Combine sales orgn
Combine Distbn channel
Combine division
Assign sales order types to permitted sales area
To create Price List Types:
SPRO- IMG- SD- Basic Functions- Pricing- Maintain Price Relevant Master Data:
Define price list category for customers: OVSI: assign to CMD sales area screen in price list type field, in sales tab page in pricing and statistics section.
Define pricing group for customers: OVSL: assign to CMD sales area screen in price group field, in sales tab page in pricing and statistics section.
Define material group: OVSJ: assign to sales orgn 2 view of MMR in Mat Pricing Group Field.
2 digits character key with description
Cond Type Description Cond Class Calculation Type
BO01 Group rebate Exp reimbursement Percentage
BO02 Mat rebate Exp reimbursement Qty (fixed)
BO03 Cust rebate Exp reimbursement Percentage
BO04 Hierarchy rebate Exp reimbursement Percentage
BO05 Hierarchy rebate / Mat Exp reimbursement Percentage
BO06 Sales Independent Rebate Exp reimbursement Fixed amount
EDI1 Cust Expected Price Prices Quantity
HB00 Discount (value) Discount / Surcharge Fixed amount
HD00 Freight Discount / Surcharge Gross weight
K004 Material Discount / Surcharge Qty / absolute
K005 Customer / Material Discount / Surcharge Qty / absolute
K007 Customer discount Discount / Surcharge Percentage
K020 Price group Discount / Surcharge Percentage
K029 Material Pricing Group Discount / Surcharge Absolute discount by wt
K030 Customer/ Mat Group Discount / Surcharge Percentage
K031 Price Grp/ Mat Pr Group Discount / Surcharge Percentage
K032 Price Grp/ Material Discount / Surcharge Quantity / absolute
KF00 Freight Discount / Surcharge Gross weight
NRAB Free Goods Discount / Surcharge Quantity
PI01 Inter company price Prices Quantity (fixed)
PI02 Inter company % Prices Percentage
RB00 Discount / value Discount / Surcharge Fixed amount
PR00 Price Prices Quantity
VPRS Cost Prices Quantity
RL00 Factoring Discount Discount / Surcharge Percentage
MW15 Factoring Discount Tax Taxes Percentage
SKT0 Cash discount
Customer Specific Price: sales orgn, distbn, division, customer & material
Price List Price: sales orgn, distbn, division, price list type & material
Material Price: sales orgn, distbn, division & material
Customer discount: sales orgn, distbn, division & customer
Customer material discount: sales orgn, distbn, division, customer & material or sales orgn, distbn, customer & material.
Material discount: sales orgn, distbn, division & material or sales orgn, distbn & mat.
Condition Records:
Condition records allow you to store & retrieve pricing data in the system. Pricing elements are generally managed at the sales orgn & distbn channel level. There fore you always have to specify organizational level when creating cond records. In the case of cond records for price groups, freight charges, & cust specific prices & discounts you must also enter the division. As a result, you can create conditions according to product groups with these price elements.
Pricing Elements in Sales Order:
Price: the basis of pricing during sales order processing is the gross price of the mat. The system selects the most specific record- the cust specific price. If it does not exist, the system looks for price list type. If it also does not exist then system takes the basic material price. You can define price list types by customer groups (wholesale or retail) or by currency (price lists for each foreign country dealt with)
Surcharge & Discounts:
Freight Costs: you can create cond record either based on: the first part of the inco term (for e.g. FOB) or on the combination of part 1 & 2 (for e.g. FOB & Boston). There are 2 predefined freight conditions
o KF00: applies to each item in a sales doc.
o HD00: applies to entire document.
Sales Taxes:
Prerequisites for Automatic Pricing:
Necessary data must be maintained in MMR & CMD:
Material Master Data: the price related fields can be found in sales orgn 1 & 2.
Tax Classification
Price Material: you can specify another material as ref for pricing info
Material Group: defines a group of materials for which you want to apply the same cond record.
Cash Discount: whether or not mat qualifies for cash discount
Customer Master Data: the price related fields appear on sales data screen.
CuPP: specify the pricing proc for a customer
Price List: Allow you to apply a mat price in a particular currency to a group of customers e.g. wholesale customers.
Price Group: price group lets you apply a discount to a particular group of customers.
Tax Classification: billing tab page.
HEADER & ITEM CONDITIONS:
The standard system includes cond types that you can apply at only the header level, the header conditions. Cond types that you can only use for items are called item conditions. There are some cond types that can be used at both header & item level:
RA01: percent from gross
RB00: absolute discount
RD00: weight discount
Header Conditions: you cannot create cond records for it; it is entered manually in order processing. Automatic pricing does not take place for them.
HA00: percent discount
HB00: absolute discount
HD00: freight
HM00: order value
Item Conditions: in the std SAP most cond types are defined as item conditions:
K004: mat discount
K005: cust/ mat discount
K007: cust discount
PR01: mat price
KF00: freight
Distribution between Header & Item:
Header conditions apply to all items in the doc & are automatically distributed to all the items. It can be either percentage or an absolute amount.
If you enter a header cond that is based on a percentage (e.g., a dis of 2% ) the system automatically applies this percentage to all the items in the doc.
If the header cond is an absolute amount, there are 2 ways in which the system can distribute the amount among the items in the doc:
Distributed proportionally among the items
Amount entered at header level is duplicated for each item.
You control the distribution of absolute header condition in the Group Price Field per cond type.
HB00: header discount distributed as percentage because it is marked as a header cond & group condition. The system distributes the amt proportionally among the various items, in this case according to the value of the items. The distribution of an absolute header cond need not be based on value. For e.g. you can specify in customizing for sales that the distribution is based on weight & volume of the different items. You can specify the basis of distribution in the Alternative Cond Base Value field in the pricing screen.
RB00: assigns the header discount to each item identically, because it is only marked as header condition.
Pricing Procedure:
In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
In SD, the steps to configure Pricing procedure are as under:
Step 1:
Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
5. Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.
Condition Table:
Condition records are always created using a specific key.
Use tables for help in defining the structure of condition record keys.
The most important fields used in pricing at header and item level are available in the standard system.
 The key fields of a condition table must appear at the start of the table, in other words, non-key fields must not appear between any two key fields.
Condition table: The definition of the key of the condition record.
Access Sequence:
The access sequence determines the sequence in which the condition records for a condition type are found and read.
 An access sequence (search strategy) is defined for each condition type (with the exception of header and manual only condition types) in the pricing procedure.
This search strategy defines the sequence in which the system reads the condition records for a condition type.
Each access performed during the access sequence is made using a condition table.
A condition table is a combination of fields, which form the key for a condition record.
You can make an access dependent on certain requirements.
You can define prices, discounts, and surcharges at various levels.
Each level is defined by a combination of fields or by a field in a condition table.
Using the access sequence, you can define the sequence of the different levels.
The system attempts to determine the condition records in the sequence specified.
 Within each access of an access sequence, you can specify the specific document field (source field) with which an access is carried out.
Examples:
> Material or pricing material?
> Document currency or local currency?
> Sold-to party or ship-to party?
Make accesses dependent on requirements to avoid unnecessary accesses. This reduces the system load.
Access sequence: A search strategy to locate the proper condition record.
Condition Types:
The condition type determines the category of a condition and how it is used.
The calculation type and the scale base type can be controlled for each condition type.
For Example: Scale for Condition Type PROO
1 pieces 800 uni
10 pieces 750 uni
100 pieces 700 uni
Possible scale base types Possible calculation types
Value Percentage from an initial value Fixed amount
Quantity Amount per unit of measure
Weight Amount per unit of weight
Volumes Amount per unit of volume
Time period Quantity per unit of time
Each condition type can be set as an automatic surcharge, discount or either.
Condition Type in Pricing Procedure can be set as Manual, Mandatory or Statistical, as per requirement.
Condition types: A calculation or formula used for a component of pricing.
A condition type is a representation in the system of some aspect of your daily pricing activities. For example, you can define a different condition type for each kind of price, discount or surcharge that occurs in your business transactions.
Example of a Condition Type price pr00, discountk007,frieght kf00
A condition table defines the combination of fields (the key) that identifies an individual condition record. A condition record is how the system stores the specific condition data that you enter in the system as condition records. For example, when you enter the price for a product or a special discount for a good customer, you create individual condition records.
An access sequence is a search strategy that the system uses to find valid data for a particular condition type. It determines the sequence in which the system searches for data. The access sequence consists of one or more accesses. The sequence of the accesses establishes which condition records have priority over others. The accesses tell the system where to look first, second, and so on, until it finds a valid condition record. You specify an access sequence for each condition type for which you create condition records.
The primary job of a pricing procedure is to define a group of condition types in a particular sequence. The pricing procedure also determines:
Which sub-totals appear during pricing
To what extent pricing can be processed manually
Which method the system uses to calculate percentage discounts and surcharges
Which requirements for a particular condition type must be fulfilled before the system takes the condition into account
pricing procedure dirctly link to fi through the acount keys link to gl accounts
Pricing Procedure:
Pricing procedure: A sequential list of condition types and subtotals.
All condition types permitted in pricing are contained in the pricing procedure.
You determine how the system is to use conditions by specifying requirements for each condition.
The sequence in which the system accesses conditions in the business document is also determined here.
 The reference level provides a method to specify a different basis for the condition type calculation and for grouping conditions for subtotals.
The pricing procedure can contain any number of subtotals between gross and net price.
You can mark a condition type in the pricing procedure as being:
--> a mandatory condition
--> a manually entered condition
--> for statistical purposes only
Pricing Procedure Determination & Overview:
In this example, an order for 120 pieces of a material is created. The system must determine the price automatically.
First, the relevant pricing procedure is determined based on the sales area, customer, and sales document type.
The system reads the condition type of the first step. It determines the assigned access sequence for this condition type.
 The system reads the access sequence. The sequence of condition tables represents the search strategy for finding the relevant condition record.
Each condition table represents one access which can be made for a condition record with the specified key.
The system searches for valid condition records with the key specified by the condition table (accesses).
 If the first access does not find a valid condition record, then the system searches for the next access using the next condition table.
 Once the system finds a valid condition record for an access, it reads the condition record and copies the value that corresponds to the scale into the sales document.
The whole process is repeated for each condition type until the system has finished the entire pricing procedure.
Pricing Configuration:
The condition table contains the keys that can be used for creating dependent condition records.
You can add your own condition tables using table numbers 501 through 999.
An access sequence is composed of one or more condition tables.
After creating the access sequence, it is assigned to a condition type.
 You can also create your own condition types. You determine the characteristics of each condition type, for example, whether it is for surcharges or discounts and whether it should be dependent on values or quantities.
The condition types are combined in the required sequence in the pricing procedure.
Finally, you need to maintain the procedure determination table for the pricing program.
The pricing procedure is determined according to:
>> Sales area
>> Customer pricing procedure field in the customer master
>> Document pricing procedure field in the sales document type.
Account Assignment Group in SD:
I Plays a vitol Role in SD --> Customer Master Record --> Sales General Data
Billing Tab.
Account assignment group for this customer
The account assignment group to which the system automatically posts the sales document.
Use
The system uses the account assignment group as one of the criteria during the automatic determination of revenue accounts.
Procedure
The system automatically proposes the account assignment group from the customer master record of the payer. You can change the default value in the sales document or the billing document.
It also Plays a vitol Role in Material Master --> Sales Organisation Data 2 View.
Account assignment group for this material
Group of materials with the same accounting requirements.
Use
Used by the system when creating an accounting document from a billing document to determine the revenue or sales deduction account.
We can Set Credit Managment at Either Sales Order Level or Delivery Level.
GAP ANALYSIS
Gap means small cracks. In SAP world or in Information Technology world, gap analysis is the study of the differences between two different information systems or applications( ex; existing system or legacy system with Client and new is SAP), often for the purpose of determining how to get from one state to a new state. A gap is sometimes spoken of as "the space between where we are and where we want to be."
Gap Analysis is undertaken as a means of bridging that space. Actual Gap Analysis is time consuming and it plays vital role in Business Blueprint [AS IS Process] stage.
A through Gap Analysis will identify the gaps between how the business operates and its needs against what the package can can't do. For each gap there will be one of three outcomes which must be recorded and auctioned,
1. GAP must be closed and customized software can be developed
2. GAP must be closed but software cannot be written therefore a workaround is required
3. GAP does not need to be closed.
A point worth mentioning here is that at time people confuse between user-exits and Gap Analysis. User exits are standard gate ways provided by SAP to exit the standard code and we can write our own code with the help of ABAP workbench, its not new functionality which we are trying to build in sap but its slight enhancement within the same code.
Gap analysis is start point of Realization and once business Blueprint is finished we have to find the realization of sap system for client requirement and there will be certain gaps when compared to system fit. Those gaps can be closed either by re-engineering of business process to fit with SAP or we have to use USER exits in case of small deviations or complete enhancements with the help of ABAP to fit with the SAP system.
The Gaps can differ from company to company. Most commonly, however, missing functionality is industry-specific.
Examples:
1. MGM Studios and Lycos sometime back worked with SAP to develop its new intellectual property management and media advertising management functionality, respectively.
2. A leading Oral care product company wanted the promotion of free-goods where they wanted 'Buy one get 2 different products free'.
A through gap analysis will identify the gaps between how the business operates ad its needs against what the package can and can't do. For each gap there will be one of three outcomes which must be recorded and actioned.GAPs must be closed and therefore customized software can be developed to close the gap. In some cases GAP must be closed but software cannot be written therefore a workaround is required in other words a business process change is recommended to the client.
In simple terms: Gap means small cracks. In SAP world. In information technology, gap analysis is the study of the differences between two different information systems or applications (ex; existing system or legacy system with Client and new is SAP), often for the purpose of determining how to get from one state to a new state. A gap is sometimes spoken of as "the space between where we are and where we want to be." Gap analysis is undertaken as a means of bridging that space.
Actual gap analysis is time consuming and it plays vital role in blue print stage.
Pricing Scenarios :
There are Client Specific:
Ex:- If the Client is Dealing with Domestic and Exports we have to Maintain the Both and having the Consigment Process we have to do the Consignment Pricing etc.,
Hope this Clairfies your Doubts and Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula

Step by Step process for Pricing in SAP

Hello Experts,
Can any one please send me the documentation for whole process of pricing in SAP , So that it will explain me how it works in SAP.
I don´t need the steps for the configuration.
Thanks

Hi
Pricing and Conditions
The term pricing is used broadly to describe the calculation of prices (for external use by customers or vendors) and costs (for internal purposes, such as cost accounting). Conditions represent a set of circumstances that apply when a price is calculated. For example, a particular customer orders a certain quantity of a particular product on a certain day. The variable factors here - the customer, the product, the order quantity, the date - determine the final price the customer gets. The information about each of these factors can be stored in the system as master data. This master data is stored in the form of condition records.
refer link below
<a href="http://www.sap-basis-abap.com/sapsdlog.htm">PRICING</a>
PRICING:
Pricing is the combination of creating correct pricing procedure that map the business needs & processes, such as correct pricing & discounting, & keeping to the legal requirements placed on the business, such as adhering to the tax laws of the country.
SPRO- IMG- SD- Basic Functions- Pricing- Pricing Control
Create Condition Table: V/03, V/04, V/05
Define Access Sequence: V/07
Define Condition Types: V/06
Define & Assign Pricing Procedure
Maintain Pricing Procedure: V/08
Define CuPP: OVKP
Define DoPP: OVKI. The DoPP indicator is used to determine pricing in conjunction with the sales area & CuPP.
Assign DoPP to Order Types & Billing Types: OVKJ & OVTP
Define Pricing Procedure Determination: OVKK
Create Condition Table: V/03, 04, 05
Put the most general field for e.g., Sales Orgn in the highest position & the most specific field in the lowest. After organizational fields, place fields from doc header before those that come from item level (customer comes before material).
Sales Orgn, Distbn Channel, Div, Cust, Mat: Customer Specific Price
Sales Orgn, Distbn Channel, Div, Price List Type, Mat: Price List
Sales Orgn, Distbn Channel, Div, Mat: Material Price.
Maintain Access Sequence: V/07
Go to new entries, define 4-digit acc seq. Select acc seq, go to Accesses and place the cond tables and check exclusive indicator (which determines that if a cond record is successfully found, the system will stop searching further). Select each cond table and go to Fields.
There are some cond types for which you do not create cond records (header discounts that you can only enter manually). These cond types do not require an access sequence.
Define Condition Type: V/06
They are used in the pricing procedure to define how the cond is going to perform, such as either a %tage or a fixed amount. The cond type can be automatic or it can allow manual changes. Copy the required cond type and rename. Then assign acc seq to cond type.
If you use different calculation types for what are otherwise the same conditions (for e.g., %tage, as fixed amt, qty dependent), you do not have to define different cond types in customizing. You can set different calculation type when maintaining cond records.
Functionality of Condition Types:
Access Sequence
Condition Class: surcharge & discounts or prices
Plus/Minus: -ve, +ve or both
Calculation Type: fixed amt, %tage, qty, wt, voln
Rounding rule: commercial, round up and round down
Group Cond
Manual Entry: whether manual or automatic entry has priority
Header Cond: after entering the header cond type click on the button activate. The cond amt of the header conditon is copied as it is to all the line items in the doc.
Item Cond
Amount/ Percent: check & u can change the amount or % for the cond type during data processing
Delete: check & the cond record may be deleted from the doc.
Value: check & the value of the cond type can be changed during data processing
Calculation Type: check & the cal type can be changed during doc processing
Valid from & to
Scale Basis: determines how the system interprets a pricing scale in a cond, for e.g., the scale can be based on qty, wt, voln
Check Value: indicates whether the scale rates must be entered in ascending or descending order.
Define and Assign Pricing Procedure: V/08
A pricing proc consists of a lists of cond types in a defined order, such as price less discount plus tax. Go to new entries, define 6-digit pricing proc with descp. Select the 6-digit pricing proc and go to Control Data, you will be faced with an empty structure.
Step: the no that determines the sequence no of a cond type with in a procedure
Counter: second mini step with in an actual step
Conditon type: specify the cond type
From & To: if you specify the ref steps in these fields, the cond values of the 2 steps specified and steps in between are totaled
Manual:
Mandatory: whether a cond type is mandatory when system carries out pricing
Statistical: the value represented in this step will not alter the overall value
Print: which cond types should be printed on a doc (order confirmation, invoices)
Subtotal: controls whether & in which fields the cond amts or subtotals are stored
Requirement: for a cond type to be executed in the sales doc the requirement specified here must be satisfied. (It is a gateway)
Alternative Calculation Type: alternative formula to the formula in the std system that determines the cond. In the std SAP system for the cust expected price EDI1, the alt cal type is 9, which means it contains a routine with a logic which states that the difference between the customer expected price & the net value is zero.
Alternative Cond Base Value: alternative formula for determining the cond basis (amt to which the discount or surcharge in a scale refers)
Account Key: this field enables the system to post the sales value to different G/L accounts. ERL: sales revenues, ERS: sales deductions, ERF: freight revenue.
Accruals: this is exclusively for rebate cond types BO01 & BO02. Key, which identifies various types of G/L accounts for accrual postings.
TAX: MWST
Tax is calculated on the following parameters:
Plant
Ship to party region
Customer tax classification
Material tax classification
Pricing Procedure Determination: OVKK: Determination Rule
Before one can proceed with the determination rule, one needs to maintain the CuPP & DoPP. One needs to assign a single character alphanumeric key with a short descp. Then assign the DoPP to the sales doc types. This will ensure that for e.g., all sales orders created using order type OR, which has been assigned a DoPP of 1, will all use the same pricing proc if created in the same sales area & with the same CuPP. In some instances, you may not want to have the same pricing proc for a sales doc, as you may want in a billing doc. For this reason, you may allocate a different DoPP to a billing doc.
Do not forget to assign the CuPP indicator to your CMD in the Sales Screen
Sales Orgn + Distbn + Division + CuPP indicator + DoPP indicator = Pricing Procedure
To Create own Sales Doc Types:
SPRO- IMG- Sales Doc- Sales Doc Header-
Define sales doc types: VOV8. Copy std order type& rename
Assign Sales area to Sales Doc Types:
Combine sales orgn
Combine Distbn channel
Combine division
Assign sales order types to permitted sales area
To create Price List Types:
SPRO- IMG- SD- Basic Functions- Pricing- Maintain Price Relevant Master Data:
Define price list category for customers: OVSI: assign to CMD sales area screen in price list type field, in sales tab page in pricing and statistics section.
Define pricing group for customers: OVSL: assign to CMD sales area screen in price group field, in sales tab page in pricing and statistics section.
Define material group: OVSJ: assign to sales orgn 2 view of MMR in Mat Pricing Group Field.
2 digits character key with description
Cond Type Description Cond Class Calculation Type
BO01 Group rebate Exp reimbursement Percentage
BO02 Mat rebate Exp reimbursement Qty (fixed)
BO03 Cust rebate Exp reimbursement Percentage
BO04 Hierarchy rebate Exp reimbursement Percentage
BO05 Hierarchy rebate / Mat Exp reimbursement Percentage
BO06 Sales Independent Rebate Exp reimbursement Fixed amount
EDI1 Cust Expected Price Prices Quantity
HB00 Discount (value) Discount / Surcharge Fixed amount
HD00 Freight Discount / Surcharge Gross weight
K004 Material Discount / Surcharge Qty / absolute
K005 Customer / Material Discount / Surcharge Qty / absolute
K007 Customer discount Discount / Surcharge Percentage
K020 Price group Discount / Surcharge Percentage
K029 Material Pricing Group Discount / Surcharge Absolute discount by wt
K030 Customer/ Mat Group Discount / Surcharge Percentage
K031 Price Grp/ Mat Pr Group Discount / Surcharge Percentage
K032 Price Grp/ Material Discount / Surcharge Quantity / absolute
KF00 Freight Discount / Surcharge Gross weight
NRAB Free Goods Discount / Surcharge Quantity
PI01 Inter company price Prices Quantity (fixed)
PI02 Inter company % Prices Percentage
RB00 Discount / value Discount / Surcharge Fixed amount
PR00 Price Prices Quantity
VPRS Cost Prices Quantity
RL00 Factoring Discount Discount / Surcharge Percentage
MW15 Factoring Discount Tax Taxes Percentage
SKT0 Cash discount
Customer Specific Price: sales orgn, distbn, division, customer & material
Price List Price: sales orgn, distbn, division, price list type & material
Material Price: sales orgn, distbn, division & material
Customer discount: sales orgn, distbn, division & customer
Customer material discount: sales orgn, distbn, division, customer & material or sales orgn, distbn, customer & material.
Material discount: sales orgn, distbn, division & material or sales orgn, distbn & mat.
Condition Records:
Condition records allow you to store & retrieve pricing data in the system. Pricing elements are generally managed at the sales orgn & distbn channel level. There fore you always have to specify organizational level when creating cond records. In the case of cond records for price groups, freight charges, & cust specific prices & discounts you must also enter the division. As a result, you can create conditions according to product groups with these price elements.
Pricing Elements in Sales Order:
Price: the basis of pricing during sales order processing is the gross price of the mat. The system selects the most specific record- the cust specific price. If it does not exist, the system looks for price list type. If it also does not exist then system takes the basic material price. You can define price list types by customer groups (wholesale or retail) or by currency (price lists for each foreign country dealt with)
Surcharge & Discounts:
Freight Costs: you can create cond record either based on: the first part of the inco term (for e.g. FOB) or on the combination of part 1 & 2 (for e.g. FOB & Boston). There are 2 predefined freight conditions
o KF00: applies to each item in a sales doc.
o HD00: applies to entire document.
Sales Taxes:
Prerequisites for Automatic Pricing:
Necessary data must be maintained in MMR & CMD:
Material Master Data: the price related fields can be found in sales orgn 1 & 2.
Tax Classification
Price Material: you can specify another material as ref for pricing info
Material Group: defines a group of materials for which you want to apply the same cond record.
Cash Discount: whether or not mat qualifies for cash discount
Customer Master Data: the price related fields appear on sales data screen.
CuPP: specify the pricing proc for a customer
Price List: Allow you to apply a mat price in a particular currency to a group of customers e.g. wholesale customers.
Price Group: price group lets you apply a discount to a particular group of customers.
Tax Classification: billing tab page.
HEADER & ITEM CONDITIONS:
The standard system includes cond types that you can apply at only the header level, the header conditions. Cond types that you can only use for items are called item conditions. There are some cond types that can be used at both header & item level:
RA01: percent from gross
RB00: absolute discount
RD00: weight discount
Header Conditions: you cannot create cond records for it; it is entered manually in order processing. Automatic pricing does not take place for them.
HA00: percent discount
HB00: absolute discount
HD00: freight
HM00: order value
Item Conditions: in the std SAP most cond types are defined as item conditions:
K004: mat discount
K005: cust/ mat discount
K007: cust discount
PR01: mat price
KF00: freight
Distribution between Header & Item:
Header conditions apply to all items in the doc & are automatically distributed to all the items. It can be either percentage or an absolute amount.
If you enter a header cond that is based on a percentage (e.g., a dis of 2% ) the system automatically applies this percentage to all the items in the doc.
If the header cond is an absolute amount, there are 2 ways in which the system can distribute the amount among the items in the doc:
Distributed proportionally among the items
Amount entered at header level is duplicated for each item.
You control the distribution of absolute header condition in the Group Price Field per cond type.
HB00: header discount distributed as percentage because it is marked as a header cond & group condition. The system distributes the amt proportionally among the various items, in this case according to the value of the items. The distribution of an absolute header cond need not be based on value. For e.g. you can specify in customizing for sales that the distribution is based on weight & volume of the different items. You can specify the basis of distribution in the Alternative Cond Base Value field in the pricing screen.
RB00: assigns the header discount to each item identically, because it is only marked as header condition.
<b>
REWARD IF HELPS</b>
Message was edited by:
SHESAGIRI GEDILA

Price Procedure configuration

Dear SAP Pantars,
Kindly help me to know the complete configuration steps (i.e both from IMG and from SAP Menu) for the following price calculation in PO, for the particular vendor when we select particular tax code.
Example:
Basic price: price * quanity: 2 *10              = 20.00
Less discounts: 10%                                 = 2.00
Price after discounts:                                 = 18.00
Add Taxes after price dicsounts
a) Excise duty of 4% on 18.00                   = 0.72
b) Education cess on ED of 2%                 = 0.0144
c) sec Ed cess on ED of 1%                      = 0.0072
Price after tax:                                           = 18.7416
Add freight 5% on price after discount:     = 0.9
Net effective price:                                     = 19.6416
Regards,
Prashanth

well thanks god this is a easy one this i can map
first of all you need to tell us which one is recovorable tax and which one is not by saying recovarable i mean are you going to utilize that tax or not
as per me basic excise duty will be added to the material cost so its non recovarable and so it must be added to material cost.
so in the tax procedure it should be maintained with the key non deductible tax.
cess and scess if non recovrable then they will not be coming in the material cost
so the calculation should happen like this
well the scenerio you given is already mapped in std. pricing procedure and for tax you need to make use of tax procedure

Cin-tax

Issue No.1
Short Text
how to prepare PO having discount after excise & tax
Long Text
hi,
Our bussiness requirment is that we want to prepare a PO having
discount after excise and tax.
Basic Price 32.930
Add Excise Duty 4% 1.320
Add Cess .125% .040
Add Education Cess 2% .026
Add H.Ed.Cess 1% .014
CST 2% .687
TOTAL 35.020
ADD Dealer Commission .809
TOTAL 35.829 (Dealer Billing)
Less Discount 1.500 (One dealer shows in bill and another
issue credit note)
Payable amount 34.329 (Actual payable amount to dealer)
Issue No.2
Short Text
Goods Issue against Sample material
Long Text
Hi,
We purchases sample material from outside vendor at factory and send same to
branches through 301 movement .
(a/c entry : Inv. sample -Dr to 3001
& Inv. Sample - Cr. to 2001)
How to show the inventory consumption at branch while delivering to end customer from branch without effecting the customer a/c

Hi VS,
1. Have you maintained correctly the SPRO settings in SPRO -- Logistics General -- Tax on goods movement -- India.
2. Have you maintained master data correctly?
3. Have you maintained condition records correctly?
Once you maintain all the above things correctly then only you will able to process excise related transactions.
Go thru the link, which will help you in understanding the process etc.
http://help.sap.com/saphelp_47x200/helpdata/en/09/ebf138cdd78a4be10000000a114084/frameset.htm
Hope it clarifies.
Thanks,
Viswanath

Cin-exceise-tax

Issue No.1
Short Text
how to prepare PO having discount after excise & tax
Long Text
hi,
Our bussiness requirment is that we want to prepare a PO having
discount after excise and tax.
Basic Price 32.930
Add Excise Duty 4% 1.320
Add Cess .125% .040
Add Education Cess 2% .026
Add H.Ed.Cess 1% .014
CST 2% .687
TOTAL 35.020
ADD Dealer Commission .809
TOTAL 35.829 (Dealer Billing)
Less Discount 1.500 (One dealer shows in bill and another
issue credit note)
Payable amount 34.329 (Actual payable amount to dealer)
Issue No.2
Short Text
Goods Issue against Sample material
Long Text
Hi,
We purchases sample material from outside vendor at factory and send same to
branches through 301 movement .
(a/c entry : Inv. sample -Dr to 3001
& Inv. Sample - Cr. to 2001)
How to show the inventory consumption at branch while delivering to end customer from branch without effecting the customer a/c

TCOde: ME21N
There you have to select in one of the steps Tax. You have to give basic price. All the taxes component will be done automatically.
This will be done by MM person

Can u tell me waht r the steps involved in rebate processing

hi guru's this is suresh.advanced thanks for all gurus

Rebates Processs in SAP is divided into three components
1) Configuring Rebates
2) Setting Up Rebates
3) Managing rebate agreeeements and payments
Pre-requsiistes- Check the following:
1.The payer partner needs toi have the rebate field checked in the customer master on the sales area-billing doc tab.
2.The Billing type must be marked as relevant for rebates.
3.The Sales Organisation must be marked as relevant for rebates.
Condition Technique :
Rebates, use the condition technique, but distinguish themselves from pricing in applying to transactions over time, versus on a transaction basis. Rebates have their wn field catalog and their own condition table naming convention.So you could have two condition table "001" one for pricing and one for rebates, which could have different key fields. You need to use the technical names A001 For pricing and KOTe001 for rebates when you use the query type using transaction SE 16..
Use create access sequence (AS). Enter 1 in field category for rebate specific. AS after going thru the right path of maintaining access sequence for rebates.
The big difference between the rebate and the pricing access sequence is that there is no exclsuion flag available for rebate related AS. This means multiple tables for an access sequence can be aplied at the same time.
Rebate related condition types are identified by codnition class -C.
After defining and creating condition types for rebated include them in the pricing proceedure. The requirement should be 24 here which implies that the accruals are calculated on the basis of invoice/bill.
The other fields- alctyp and altcbv does not allow you to manipulate how a rebate is calculated. Also, remove the requiremnt 24, if u want to see reabtes at order time.
Now payment of rebates:
Payments can be maunal or in full settlement. When you do manual payments, it defines how much can be paid out during a partial settlemetn. You use partial settlement only when rebate agreement is defined for a full year but the paoyouts are supposed to happen on a monthly, quarterly or anyother specified period.
These accurals are based on sales volume and when they are posted billing is created int eh follwoing manner. Provision for accruals is debited and Sales revenue is credited. When rebate credit memo is created
Customer account/ is debited and
Accrual provision account is credited.
Also, please note that when rebates are created without dependent ona material but on customer/material you need to refer to a material for settlement.
With Compliment: Srini
I have this same problem found in:
http://www.sap-img.com/sap-sd/rebate-process-with-ref-to-so.htm
However, can somebody explain it as I have problem in understanding the link.
What exactly do you wish to know in Rebates? The total outline of the Rebate process or each and every step in the SAP system?
First of all rebates are more or less discounts which are offered to customers. The rebates are based on the volume of the business the customer does with you within a specified time. for eg if the customer agrees for Rs.1 Crore worth of business with u in 1 year, then you activate your rebate porocess. if at the end of the year the customer DOES achieve the target u offer him say 2/3/4 % whatever is decided. The rebates are passed on to the customer in the form of Credit notes.
The rebate can be given to the customer at one time or in installments also.
This is broadly the outline of the rebate process.
R.Sreeram
Note : I recomend you to study the theory part of why rebate and why not a discount.
This will help you understand better.
May be I can help you with rebate process.(IN -IMG)
1. define a rebate agreement type
2. define a condition type group
3. define a condition type and place this condition
Type in the pricing procedure.(REQUIREMENT=24)
ALSO IN THE PROCEDURE- ACCRUAL KEY = ERU
YOU ALSO HAVE TO DO THE ACCOUNT DETERMINATION FOR REBATES.
Once you have defined all the 3 and assignment starts.
Assign the agreement type to the condition type group
Assign the cond type group to the condition type.
Condition technique is also used in rebates.
REBATE ACTIVATION- IN CUSTOMER MASTER, SALES ORGANISATION AND FOR THE BILLING DOCUMENT.
After having done this please proceed to maintain the condition record for the rebates (transaction code-vbo1)
Note: if you maintain the requirement coloumn with the requirement as 24 - the rebate will be affected in the billing document and if you dont give the requirement as 24 your rebate will be affected in the sales order.
The rebate process is completed when you have created a credit memo to the customer.
The document type for the partial settlement is R3.
Please make sure you open two screens SO THAT YOU CAN COMPARE THE NEW ENTRIES WHAT EVER YOU'RE DEFINING WITH THAT OF THE STANDARDS or first you try with the standard condition type boo1, boo2
boo3 boo4.
AFTER YOU HAVE FINISHED A COMPLETE SALES CYCLE OF CREATION ORDER , DELIVERY AND BILLING.
GO TO THE CONDITION RECORD IN CHANGE MODE (VB02) AND SETTLE THE ACCOUNT PARTIALLY.
I hope this will be of any help to you.
Praveen
In a simple way,
1. First you need to create a Rebate agreement.
2. Create condition record for rebate giving the rebate rate and accrual rate.
3. when the rebate relevent billing doc is generated, the rebate and accruals are determined and posted in a seperate GL account as a noted item - amount to be settled. Also it gets copied in the rebate agreement.
4. create settlement run using credit memo request and then credit memo to settle this amount with the customer.
Source : SAP-IMG

Base value for excise duty

Hello All,
Base value for Excise duty and different service tax. calculated with the BASB condition type.
can we change the the base value pick up method.
Means i dont want to pick this value fron Net (gross price less discount).
I want to have this value from Calculated Net value with considering freight charge and less discount.
is it possible to change,
Abhinay Waikar.

Hi,
Assign subtotal "5" against the freight condition types in MM calculation schema and then try.

Standard report needed !

Hi,
Is there any standard report available which will show the list of invoices along with the discounts given ?
-Sachin

Dear Sachin
In VF05, the report will show less discount only under the tab "Net Value". But however, if you want the split up details of discount, then you have to develop a zee report table joining KONV and VBRP.
thanks
G. Lakshmipathi

Which item need to tax

hi,
in me23n line item conditions, there are 2 main value. net value(either base on standard or map item value) and effective value (also include of freight, duty)
1) may i know for both standard price and moving average price item, input tax during miro is based on net value(only stock or merchandise item value) or effective value(also include of freight, duty)?
2) most of the case, custom and freight forwarder different vendor from the stock vendor. when do miro for freight and custom, should include input tax?
3) basically i need to know whether standard price or moving average price item, input tax is based on
a) stock or merchandise item value only or
b) stock or merchandise item + duty + freight + etc.
thanks

Hi there,
Taxes on material/ Goods or services depends upon three things wher ther your vendor is taxable, material or service is taxable, and your material/ service availed is taxable or not..
So if the vendor from whom you are procuring the material or services is charging you some taxex you will have to pay that which will directly go to the govt for devlopment purpose.
The net amount of an Po line item less discounts offred by your vendor if any add freight if it also taxable.. Basically transportaion is one kind of service so service tax is applicable on it.
Hope it clears your doubts
Regards
Sujoy

Payment term with fixed date

Dear all,
I want to create a payment term as follows:
100%, 90 Days on the 10th and 25th.
I created a payment term like this:
first entry: 'day limit' - 10 days, 'fixed day' field in the "Base line date calculation" column - 10 days and 'nº of days' - 90 days second entry (for that same payment term): 'day limit' - 25 days, 'fixed day' field in the "Base line date calculation" column - 25 days and 'nº of days - 90 days;
third entry (for that same condition term) 'day limit' - 31 days, 'fixed day' field in the "Base line date calculation" column - 10 days and additional month - 1 and 'nº of days - 90 days;
The system is not giving the expected result. For instance, for a customer with that payment term when document date is 30.09.2012 i should obtain payment date like 10.01.2012 but i obtain 08.01.2012.
I need a field wher to fix day of month for payment. Does it exist?
I hope you can help me.
best regards
Joana Trigo

Dear Trigo,
Unfortunatelly the System do not manage week day it only manage dates
in specific, but there are some options that maybe helpful:-
1. Using the field FIXED DATE:
   Fixed calendar date as part of the date on which the first or second
cash discount period ends and/or the date on which the due date for
date net payment (date on which payment of an open item is due net, that
is with cash no discount deduction) is reached.
2. Could be into Default for baseline date area, not set the indicator
"No default" with this you then have to enter the base date manually
into your document.
3. You have the option "DAY LIMIT":
    Day of the month up until which the correspondig terms are valid.
For terms of payment which depend on whether or not the baseline date is
after or before the 15th of the month, you can define a two-part payment
term under the same terms of payment key. The terms of payment key is
expanded by the day limit entered here. Thus there are two
entries in which different terms can be specified.
For Example:
The following terms of payment require you to enter a day limit:
Documents with an invoice date on or before the 15th of the month
    are payable on the last day of the next month.
Documents with an invoice date after the 15th of the month are
    payable on the 15th of the month after the next month.
Mauri

Cash less discount

Similar Messages

Maybe you are looking for