Pallet Discount
Hi,
We have a requirement where condition type--ZKP3 --Pallet Discount(Percentage condition) should work in such a way that customers are encouraged to buy goods in FULL Pallets & if they are buying in FULL pallets ,this pallet discount should be given to Customers.
Now if a user is maintaing a condition record in VK11 for ZKP3 (e.g. 10% Pallet Discount for 2 PAL(UOM)), then UOM disappears as it is a percentage discount & not a Quantity discount.)
So to correct this we have advised to maintain scales in condition record but its not working for Full pallets as per the requirement ..It is also giving discounts for 2.5 pallets but this way it is not required.
1 PAL=25 SU.
So in order e.g. 55 SU are there , it is now giving discount for 55 SU and not for 50 As desired.
Secondly for Full Pallet discounts routine 22 should be there in ALtCBV but because of this routine 22 ,it was not calculating decimal values(e.g. for 205.56 it was considering discount for 205 only & ignoring .56).
So we removed routine 22 from ALtCBV.
Please advice ,how to get this (Pallet Discount) -percentage condition work correctly to give Full pallet discount to customers , so that customers should be encouraged to buy in Full quantity.
Many thanks in advance.
Points will be awarded.
Thanks & Regards,
Vikas
Use the Below link
[Pallet Discounts|http://help.sap.com/saphelp_erp60_sp/helpdata/en/72/6e0330214411d29a0d0000e8a5bd28/content.htm]
Similar Messages
-
hi,
there is a standard pricing condition type KP00 for full pallet discount. I need to know where the system checks for full pallett ? how the full pallet is calculated by system in sales order ?
regds
pamelaIn V/06 for this condition type, under the tab "Scales", you can see a field "Unit of meas." where PAL would have been assigned.
This means, in material master also, if you maintain the required quantity that will accommodate in a pallet under Additional Data tab, system will consider pallet price based on the pricing condition you maintain.
thanks
G. Lakshmipathi -
I want to configure the Mixed pallet discount.
Question:
How should I maintain data in Material Master Record for following materials
Material M1 and M2 (both material must be of same material group)
Whole Unit of measure : 50units = 1 Pallet
Thanks in advance for your reply.
Regards,
AshishUse the Below link
[Pallet Discounts|http://help.sap.com/saphelp_erp60_sp/helpdata/en/72/6e0330214411d29a0d0000e8a5bd28/content.htm] -
KP02 Mixed Pallet Configuration
Hi
I am trying to understand the KP00 & KP02 condition types for Standard SAP Pallet discounts.
1) KP00 - Full pallet Discount.
2) KP02 - Mixed Pallet Discount( Group Condition & Full pallet discount).
When i define this condition type in Pricing procedure similar to standard SAP "RVA001" it is like below
805 1 kp00
805 2 Kp02
( how does this counter 1 & 2 work in Pricing procedure).
Now i create a condition record for both the condition records .
Create sales order.
Both the condition applied for a Material if it reaches 1 Pallet.
I suppose only ONE Should work and give discount? How does this work?
Any help is highly appreciated.
Thanksthey work together because there is no condition exclusion between them.
regards
ROberto -
Dear all,
We know that KP00 is a condition for calculating pallet discount.But in actual situation, you have your definition about a specific material. Maybe, you want 80 bags of material M-100 equal 1 pallet. Now, my problem is that I don't know how to define this relation.
Thanks,
JustinHi Justin ,
As I know you should define it in the UOM in transaction MM01
Good Luck ,
Gad -
Additional discount on bulk purchase
Dear all,
for the scenario, if a person buys two products,then he/she got 50% discount on third product.please note person will not get any discount if he/she buy only one product,
Can you please let me know how we maintain/configure above scenario
Thanks In advanceHi Mohd,
You can use cond type KP00 (Pallet Discount),
e.g. 1 PAL = 3 EA
1EA = 10Euros
so, every PAL customer buys he shall get 5Euros discount.
Thus if customer buys 3EA then he gets the 3rd EA for 50% discount.
Please extend your description, e.g. if customer buys 4EA then?...; 5EA then?...etc. -
Automatic Pricing for Header condition
Hello,
We have the following scenario.
For an specific Sales Order type we need to charge (surcharge or a fee) a fix $$ amount at the header level. This amount should be charged only if the total value of the order is less then a fixed $$ amount.
Also another condition is for a specific material group we need to charge a fix $$ amount and if this condition is selected then the other condition should not be selected.
Eg:
1) for all material with Material group AB we want to charge(via condition type) 100$ at the header level.
we want this automatically at the header.
2) For all Order type OR we want to charge(I will maintain a condition type) 200$ if the net value of that sales order is less then 5000$. This is not item specific but at the Order header level.
We dont want to manually enter the condition type (surcharge).
I know that for Header conditions we cannot have access sequence and condition records. Then how can the 100$ or 200$ charge condition type come automatically in the Sales Order if the total order value is less then 5000$.
I can have a requirement but what about the condition Record and the access sequence for the Order type or the material group?
Any Ideas?
Thanks
SAP Fanhello, friend.
i have an hypothesis (which is merely a guess because i have not tried this recently), that it is possible to do this, but you have make your condition type both header and item, which means you get to assign an access sequence (enabling condition records). but you must also "tick" the "group condition" in the condition type so that even if this is entered at item level, this applies to the entire document and will be distributed to the items.
the group condition is supposed to be used for manually entered header conditions such as pallet discounts, and i think i might have done this for material groups, but do not recall if i've done this for order type or any other variable at one point. please do us a favor and test it, and post your findings.
regards!!!
Edited by: jonathan y on Jun 1, 2009 3:08 PM -
Urgent Please help......... Condition Formula
Hi all,...
Can you pkeae help me with what i have to do with this requirement,.. Please give me the fields to update in the condition routine.
For a material i have to take the order quantity ( VBAP - KWMENG ) / Pallet Qty ( MARM -UMREZ ).,
Here is how it should work... I did not understand what field to update... What should i assign Order Qty / Pallet Qty ...
Heres an example of how it should work: If the pallet quantity is 25 and the order quantity is 55
Price for each unit is $2.00
Total price = 55 * 2.00 = $110.00
Total number of pallets = 2.2 (55/25)
The % discount from the condition record should be applied on only 2 pallet quantities for 50 units.
The condition value would be 50 * $2 = $100 and the % is applied on the $100. So if the % was 3.00
the condition value is $3.00. The net value of the line is at subtotal 2 or KZWI2.
Thank you all.. I ll surely reward points..Hi Soniya
Why don't you copy KP00- Pallet Discount and change in V/06 calculation type to A-Percentage instead of C-Quantity.
Now your concern is % is on Order Quantity and Not on Pallet Quantity???
Then you can have AltCBV as Order quantity and check
If it doesn't satisfy than AltCTY has to be created
Regards
Jitesh -
Problem Copy control Order to Invoice
Hi All,
I maintained a copy control from order to invoice and in the item category the pricing type is maintained as 'G'(Copy pricing elements unchanged and redetermine taxes). But when I create invoice the condition value for pallet discount is getting recalculated.
There is a requirement for this condition type in the pricing procedure that when the order quantity is greater than the pallet quantity maintained through material master then only the discount should be affected.But when I change the pallet quantity to less than the order quantity,after the order is created and then invoice the order the condition value is going through the requirement and the value is getting changed .
Can anyone tell me why it is recalculating when the invoice is created, it should not reprice the order, but just carry over current pricing to the billing
All useful answers will be rewarded.
Thanks,
Ranjanhi,
Refer to OSS note 24832:
14.05.2008 Page 1 of 10
Note 24832 - Pricing rules / TVCPF
Note Language: English Version: 27 Validity: Valid from 18.05.2004
Summary
Symptom
Depending on the situation, the system should redetermine conditions or
not. For this, a differentiated control is required, for example:
1. When you create sales orders or billing documents, the condition types
are partially redetermined although you want to copy the values from
the reference document.
2. During other transactions, however, you want to redetermine the
condition types instead of copying them.
3. The 'New pricing' function on the item condition screen
redetermines all new conditions, that means it works with pricing
category 'B'. This is undesirable to a certain extent.
4. The same applies to the 'New pricing' function for the entire sales
order.
The following text will explain some examples for the use of the pricing
type implemented for this purpose (KNPRS):
Example 1 **********************************
You want to copy condition type 'VPRS' from the sales order into the
billing document. You are using pricing type 'G'. However, as a consequence
the value of the VPRS condition in the billing document differs from the
value of the goods issue posting.
Example 2 **********************************
You want to copy condition type 'PI01' (price for intercompany billing)
from the sales order into the billing document. You are using pricing type
'G'.
Example 3 **********************************
The costs 'VPRS' are to be redetermined when copying a credit memo request
from a billing document. This is required if you defined the credit memo
item in such a way that no costs are to be determined. Since the pricing
requirements are no longer checked when copying, you have to proceed as
described above to eliminate the VPRS.
Example 4 **********************************
The 'New pricing' function on the item condition screen is to keep the
manual condition, this means the function should behave like pricing
category 'C'.
Example 5 **********************************
The 'New pricing' function for the entire sales order is to keep the
14.05.2008 Page 2 of 10
Note 24832 - Pricing rules / TVCPF
manual conditions, this means the function should behave like pricing
category 'C'.
Example 6 **********************************
Billing is to be carried out using pricing type 'G'. However, condition
types with condition category 'S' and 'T' (standard price or moving costs)
are also to be redetermined. In the standard system this pricing type
copies those condition types from the sales order.
More Terms
KNPRS, TVCPF, TVCPA
Cause and Prerequisites
The pricing type controls which condition types are redetermined or which
are copied unchanged (however, the items are always revaluated). Below,
you will find a description of the pricing type characteris
Note that the specified standard pricing type characteristics
partly do not exist in older releases, or that the standard
pricing type characteristics may be different in the
individual releases. Therefore, the given consulting note
should not be considered to be exhaustive. It merely serves to
explain the principle of how a pricing type is structured and
how its characteristics can be influenced. The exact
characteristic of a pricing type in the release being used can
be seen directly in the source code of Form routine
KONDITIONSVORSTEP in Main program SAPLV61A.
o 'A' (Copy price components and redetermine scales):
No condition types are redetermined. Only the scaled prices are
adapted due to a changed basis.
o 'B' (Complete new pricing):
Completely new pricing (as if you created a new item), manual
conditions are lost.
Restriction: Condition types which are not determined via condition
technique (for example, condition type 'VPRS' or condition types
with KNTYP = 'G' which are determined using formulas) are NOT
redetermined even if you do not change them manually.
o 'C' (Copy manual pricing elements and redetermine the
others):
Completely new pricing, manual ones are copied.
Caution: Here you have to make sure that all condition types that
can possibly be changed manually have T685A-KMANU = 'C' (Manual
entry has priority) in Customizing. Otherwise, it is possible that
the conditions are displayed twice (automatically and manually) and
that both are active.
o 'D' (Copy pricing elements unchanged):
14.05.2008 Page 3 of 10
Note 24832 - Pricing rules / TVCPF
As in pricing type 'A' but the prices are fixed (no scales are
read). Condition base value and value are redetermined.
o 'E' (Adopt price components and fix values):
As in pricing type 'D' but neither condition base value nor value
are redetermined.
o 'F' (Copy pricing elements, turn value and fix):
Only used within the program.
o 'G' (Copy pricing elements unchanged and redetermine
taxes):
a) The following condition types are redetermined:
- Condition class KOAID = 'D' (Taxes)
- Condition class KOAID = 'C' (Volume-based rebate)
- Condition category KNTYP = 'I' (Intercompany billing
conditions)
- Condition category KNTYP = 'R' (Invoice list conditions)
- Condition category KNTYP = 'L' (Always new when copying)
- Condition category KNTYP = 'G' (Cost conditions)
- Condition category KNTYP = 'E' (Cash discount conditions)
All remaining condition types are dealt with like pricing type 'D'.
In particular, with pricing type 'G', the system does not only
redetermine the taxes but also the cost conditions and the
intercompany billing conditions.
o 'H' (Redetermine freight conditions):
The following condition types are redetermined:
- Condition type KNTYP = 'B' (Delivery costs)
- Condition type KNTYP = 'F' (Freight conditions)
- Condition type KNTYP = 'L' (Always new when copying)
o 'I' (Redetermine rebate conditions):
Rebate conditions and scales are redetermined.
o 'J' (Redetermine confirmed purchase net price/value):
Condition types with condition category KNTYP = 'D' (Confirmed
purchase net price/value) are redetermined.
o 'K' (Adopt price components and costs. Redetermine
14.05.2008 Page 4 of 10
Note 24832 - Pricing rules / TVCPF
taxes):
The following condition types are redetermined:
- Condition class KOAID = 'D' (Taxes)
- Condition class KOAID = 'C' (Rebate)
- Condition category KNTYP = 'R' (Invoice list conditions)
- Condition category KNTYP = 'I' (Price for intercompany billing)
- Condition category KNTYP = 'E' (Volume-based rebate)
o 'M' (Copy pricing elements, turn value):
No conditions are redetermined; during copying, the condition
values are multiplied with -1.
o 'N' (Transfer pricing components unchanged, new cost):
Condition types with condition category KNTYP = 'G' (Cost) are
redetermined.
Please note that this pricing type has NO effect on the invoice
since here the goods issue value from the delivery is usually
directly transferred to pricing. Redetermination of the settlement
price by subsequently reading the material valuation segment when
executing pricing type "N" would result in the fact that the goods
issue value information were irretrievably lost.
This standard behavior can be changed by a modification only. If
required, please contact your local consultant or SAP Remote
Consulting.
o 'O' (Redetermine variant conditions):
Condition types with condition category KNTYP = 'O' (Variants) are
redetermined.
o 'P' (Revaluation only):
The system does not redetermine any conditions; only the
revaluation occurs.
o 'Q' (Redetermine calculation conditions):
Condition types with condition category KNTYP = 'Q' (Costing) are
redetermined.
o 'U' (Redetermine precious metal conditions):
Condition types with condition category KNTYP = 'U'
(Discount/surcharge for precious metals) are redetermined.
Solution
There are two options to change the standard behavior:
14.05.2008 Page 5 of 10
Note 24832 - Pricing rules / TVCPF
1. Set up a new pricing type (for example, 'X') and allocate the pricing
type in the document flow (copying control in the IMG, Customizing
depending on the source and target document type via Transactions
VTAA, VTAF, VTLA, VTLF and VTFF).
2. Change the pricing type used in the standard system.
Procedure
For both purposes, USEREXIT_PRICING_RULE is used in Program RV61AFZA. This
is called after the setup of internal table STEU which defines the behavior
of pricing types.
Example 1 ******************************
Picing type 'X' is to be set in a way that condition 'VPRS' (which has
condition category 'G') is not redetermined during the billing. Otherwise
it behaves as pricing type 'G'.
Up to Release 4.0B, USEREXIT_PRICING_RULE can be implemented as follows:
FORM USEREXIT_PRICING_RULE
STEU-KNPRS = 'X'.
STEU-KNTYP = 'LRIE......'.
IF KOMK-KNUMA IS INITIAL.
STEU-KOAID = 'CD........'.
ELSE.
STEU-KOAID = 'D.........'.
ENDIF.
STEU-MAUEB = ' '.
APPEND STEU.
ENDFORM.
In order to ensure that pricing type 'X' acts exactly like pricing type
'G', the FORM routine USEREXIT_PRICING_COPY in Program RV61AFZA is to be
used in releases lower than Release 4.0A (if you create a document with
reference to another document, this is called: copying control; here, the
MODE is the pricing type):
FORM USEREXIT_PRICING_COPY.
IF MODE CA 'X'.
IF KONV-KSTEU NA 'CEF'.
KONV-KSTEU = 'D'.
ENDIF.
ENDIF.
ENDFORM.
In this case, you should note that the billing document contains a special
rule concerning cost condition 'VPRS'. If the goods issue for the delivery
note to be billed is posted, the value of the goods issue is copied into
condition 'VPRS'. This is hard-coded. You can prevent this by setting the
field TKOMP-WAVWR to zero in include LV60AFZZ,
USEREXIT_PRICING_PREPARE_TKOMP.
In higher releases, pricing type 'K' is also available, which copies the
VPRS of the order to the billing document and does not redetermine it
unless there is no goods issue posting (otherwise, the above-mentioned
special rule applies.)
14.05.2008 Page 6 of 10
Note 24832 - Pricing rules / TVCPF
Example 2 *********************************
Pricing type 'Y' is to be set in a way that this works as pricing type 'G'
but without redetermining the intercompany billing conditions 'PI01' and
'PI02'. They have condition category 'I'.
Changes in program RV61AFZA:
FORM USEREXIT_PRICING_RULE.
STEU-KNPRS = 'Y'.
STEU-KNTYP = 'GLRE.......'.
IF KOMK-KNUMA IS INITIAL.
STEU-KOAID = 'CD........'.
ELSE.
STEU-KOAID = 'D.........'.
ENDIF.
APPEND STEU.
ENDFORM.
In order to ensure that pricing type 'Y' acts exactly like pricing type
'G', the FORM routine USEREXIT_PRICING_COPY in Program RV61AFZA is to be
used:
FORM USEREXIT_PRICING_COPY.
IF MODE CA 'Y'.
IF KONV-KSTEU NA 'CEF'.
KONV-KSTEU = 'D'.
ENDIF.
CLEAR: KONV-SAKN1.
ENDIF.
ENDFORM.
EXAMPLE 3 *********************************
Pricing type 'Z' is to be set in the same way as pricing type 'D', but this
time the costs are to be redetermined. Up to Release 4.5B, you can
implement USEREXIT_PRICING_RULE as follows (as of Release 4.6A, pricing
type 'N' is available for this procedure):
FORM USEREXIT_PRICING_RULE.
STEU-KNPRS = 'Z'.
STEU-KNTYP = 'G.........'.
STEU-KOAID = '..........'.
STEU-MAUEB = ' '.
APPEND STEU.
ENDFORM.
In order to ensure that pricing type 'Z' acts exactly like pricing type
'D', the FORM routine USEREXIT_PRICING_COPY in Program RV61AFZA is to be
used:
FORM USEREXIT_PRICING_COPY.
IF MODE CA 'Z'.
IF KONV-KSTEU NA 'CEF'
KONV-KSTEU = 'D'.
ENDIF.
ENDIF.
14.05.2008 Page 7 of 10
Note 24832 - Pricing rules / TVCPF
ENDFORM.
Note: To correct the problem, you should define your own pricing types. In
some cases, it may be required to change existing pricing types. This is
required if you want to influence the reaction to certain field changes in
the sales order (see Note 26115 for this). This also allows you to
influence the 'New pricing' function in the sales order and billing
document. This function uses pricing type 'B'.
EXAMPLE 4 *********************************
The 'New pricing' function is meant to keep the manual changes. By default,
pricing type B' is called. As of Release 4.5A, however, you have the option
to store another pricing type for this purpose in Customizing of the
pricing procedure (Transaction V/08).
In USEREXIT_CHANGE_PRICING_RULE of program MV61AFZA, you can
replace pricing type 'B' with another pricing type, for
example, 'C' up to Release 4.0B.
FORM USEREXIT_CHANGE_PRICING_RULE USING PRICING_RULE.
IF PRICING_RULE = 'B'.
PRICING_RULE = 'C'.
ENDIF.
ENDFORM.
EXAMPLE 5 **********************************
The 'New pricing' function is to be set for the entire sales order in a way
that manual changes are kept. In the standard system, pricing type 'B' is
called. As of Release 4.5A, however, you have the option to store another
pricing type for this purpose in Customizing of the pricing procedure
(Transaction V/08).
Up to Release 4.0B, a solution is only possible by means of a modification
in program MV45AF0F:
FORM FCODE_KONB.
PERFORM PREISFINDUNG_GESAMT USING CHARB. <<<<<<<<<< delete
PERFORM PREISFINDUNG_GESAMT USING CHARC. <<<<<<<<<< insert
ENDFORM.
FV45PF0P has to be changed in the same way:
FORM PREISFINDUNG_NEU.
Aufruf neue Preisfindung
PERFORM PREISFINDUNG USING CHARB. <<<<<<<<<< delete
PERFORM PREISFINDUNG USING CHARC. <<<<<<<<<< insert
geänderte Informationen in Beleg übernehmen
PERFORM VBAP_BEARBEITEN.
PERFORM VBAP_BEARBEITEN_ENDE.
ENDFORM.
14.05.2008 Page 8 of 10
Note 24832 - Pricing rules / TVCPF
EXAMPLE 6 *********************************
Pricing type 'X' is to be set so that it functions like pricing type 'G',
but also redetermines condition categories 'S' and 'T'.
Change in Program RV61AFZA:
FORM USEREXIT_PRICING_RULE
STEU-KNPRS = 'X'.
STEU-KNTYP = 'GLRIEST...'.
IF KOMK-KNUMA IS INITIAL.
STEU-KOAID = 'CD........'.
ELSE.
STEU-KOAID = 'D.........'.
ENDIF.
STEU-MAUEB = ' '.
APPEND STEU.
ENDFORM.
To ensure that pricing type 'X' behaves exactly like pricing type 'G', use
FORM routine USEREXIT_PRICING_COPY in Program RV61AFZA:
FORM USEREXIT_PRICING_COPY.
IF MODE CA 'X'.
IF KONV-KSTEU NA 'CEF'.
KONV-KSTEU = 'D'.
ENDIF.
ENDIF.
ENDFORM.
Additional information ***********************
You can display the standard behavior of the pricing types in FORM routine
KONDITIONSVORSTEP (up to Release 3.1I in Include LV61AF0K, as of Release
4.0A in Include LV61AA12). There, for each pricing type, a line exists in
internal Table STEU. The fields have the following meaning:
o KNPRS
This is the pricing type used.
o KNTYP
This field contains a positive list of the pricing categories (up
to 10 values can be entered).
o KOAID
This field contains a positive list of the condition classes (up to
10 values can be entered).
o MAUEB
This field specifies whether manual changes should be copied.
o STFKZ
This field contains a positive list of the scale indicators (up to
14.05.2008 Page 9 of 10
Note 24832 - Pricing rules / TVCPF
5 values can be entered).
o NOTYP
This field contains a negative list of the condition categories (up
to 5 values can be entered).
o KDUPL
This field contains a positive list of the structure conditions (up
to 3 values can be entered).
o NOKDUPL
This field contains a negative list of the structure conditions (up
to 3 values can be entered).
o KFKIV
This field specifies whether intercompany billings should be
redetermined ('.' or 'X' can be entered).
o KVARC
This field specifies whether variant conditions should be
redetermined ('.' or 'X' can be entered).
o PRSQU
This field specifies whether the price source should be taken into
account ('.' or SPACE can be entered).
Note that most condition attributes (fields of the XKOMV structure) can
also have the value SPACE. To use the above 'CA' or 'NA' statements in the
IF statements also in these cases as required, you can fill the fields of
the STEU line with a corresponding number of '.' characters. These values
are mainly checked in FORM routine XKOMV_AUFBAUEN_PRUEFEN (up to Release
3.1I in Include LV61AF0X, as of Release 4.0A in Include LV61AA65).
Header Data
Release Status: Released for Customer
Released on: 18.05.2004 13:18:36
Priority: Recommendations/additional info
Category: Consulting
Main Component SD-BF-PR Pricing
The note is not release-dependent.
14.05.2008 Page 10 of 10
Note 24832 - Pricing rules / TVCPF
Support Packages
Support Packages Release Package Name
DIMP 471 SAPKIPME06
Related Notes
Number Short Text
1009170 Date of services rendered in the credit memo process
992808 Pricing type 'T': Redetermine tax conditions only
547570 FAQ: VPRS in pricing
410907 Allowed pricing types BAPISDLS-PRICING III
195094 Manual prices during intercompany billing
117347 Pricing type K modified for condition category L
114756 Customer hierarchy determination for pricing
102961 New pricing type for milestone billing plans
45326 No prices for customer-specific pricing type
26115 Conditions not updated during field change
Award opints if useful.
Regards,
Raghu.
Edited by: Raghuram Saripalli on May 14, 2008 11:12 AM -
Help me with table and fields in SD
Hi gurus,
please find me these tables fields.
Sales Document Number
Req Delivery Date
Delivery Order Document
Billing Document Number
Billing Date
Gross Sales
Pallets Discount
Trade Discount
Commission Fees
Royalty Fees
Management Fees
each answer will b fully rewarded.
thanksHi,
Sales Document Number - VBAK-VBELN
Req Delivery Date - VBAK-VDATU
Delivery Order Document - LIKP-VBELN
Billing Document Number - VBRK-VBELN
Billing Date - VBRK-FKDAT
Regards,
Himanshu -
Why are there no BMC discounts on qualifying pieces for 2 ASF entry points?
I've had no luck whatsoever trying to log a case for support, I can't navigate the already cumbersome SAP Support Portal without getting errors so I thought I would try the forums... this is my first post:
I have a Standard Automated Letter (rate category regular) Presort, there is nothing unusual about its setup but the results seem to be incorrect: some pieces aren't getting appropriate DBMC discounts.
About the presort job and the output results:
u2022 contains all possible BMC & ASF entry points
u2022 output for all entry points look good EXCEPT for 2 ASFs: ASF-BUFFALO and ASF-OKLAHOMA CITY
u2022 the Postage Statement shows that all pieces that qualify for those 2 ASFs are not getting the DBMC discount (Entry Rate="None" for those pieces), although based on the ZIP ranges they appear to qualify for the discount
u2022 I double checked each of these 2 ASFs on USPS's FAST site to verify the ZIP ranges
other details:
u2022 currently using Presort Views 7.90c, Revision 3 (with Engine Revision 4)
u2022 each entry point not getting the discount has 1 Mixed AADC tray (I posted AP.Ctn_Level to the output files for ease of finding this out), however I'm not sure why this would affect any discounts
u2022 if Mixed AADC trays ARE what's causing the discount to not apply then I believe Presort is not processing these pieces correctly
As a test to see if the output would be different I changed a setting that I've never had to change before: I reran the presort with the ENTRY POINT TYPE changed (for only the 2 ASFs in question) from ASF to BMC-- the resulting Postage Statement shows almost all pieces in these ASFs (except 34 Mixed AADC pieces in ASF-BUFFALO) are now getting the DBMC discount! This may serve as some sort of workaround but I don't believe the results are 100% correct, the Entry Point Type for ASFs should be set to ASF otherwise the information in the Mail.dat files may cause a problem.
A couple more things to note just in case they affect anything: the presort is using a Basic Service IMB, and the scheme that these ASFs are qualifying under is Letter Trays on Pallets.
Is the output from Presort actually incorrect, or is there a setting (something that won't affect the other entry points) that can to be changed so the output will be correct?Roy,
We are aware of an issue with relabing BMC pallets to get the correct discounts in 7.90. There are some work arounds for this until it is corrected in the software. In order to give you the best work around for your job please open a support case. Below are the steps to create a message for support.
To log a case go to the SAP Service Market Place
1. Go to http://service.sap.com.
2. Click on SAP Support Portal.
3. Enter your S-User ID and password and click u201COKu201D.
4. Click u201COKu201D on digital certificate.
5. Enter your S-User ID and password again and click OK.
6. Click OK on the following screen.
7. (This step is Optional) Setting up your Single Sign-on allows the site to remember your login and not prompt for it so frequently. To do this, click my Profile at the top of the page. Then click Maintain my Single Sign-on Certificate on the left of the page and follow the instructions.
8. After the Single Sign-On, Click on Help & Support and click Report a Product Error. Under System Search, click the drop down arrow next to your installation and choose your system, and click Search and then click on the BOB link.
9. When creating a SAP message it is required to search for Notes. (Knowledge Base articles) to see if you can find an answer to your question without having to log the message for support. In the Search Terms area, type your question and click Continue.
10. If you do not see any Notes pertaining to your question click on Create Message.
11. Choose the correct Component for the product you are creating the message for. The component is the support Q that your call will go into so the correct team can assist you. To do this click on the icon next to the icon next to the Component window to see a drop down list.
12. Click the arrow by BOJ-EIM to see a more detailed list. By each component the names of the u201Cproductsu201D you are using are listed. Choosing the correct component will get your Message logged for the correct support team.
For example:
a. BOJ-EIM-COR is used for ACE, DataRight IQ, Match/Consolidate, IACE, and FirstPrep products.
b. BOJ-EIM-COM is used for DeskTop Mailer, Business Edition, Presort, PrintForm, Label Studio
c. BOJ-EIM-DEP is used for DQXI, Data Insight, eDQ Infa, SAP Siebel, PSFT, Oracle, Rapid Library
d. BOJ-EIM-DF is used for Data Federator
e. BOJ-EIM-DI is used for Data Integrator, Text Analysis, Data Services
f. BOJ-EIM-DS is used for Data Services, Fazi/Fuzzy
g. BOJ-EIM-MD is used for Metadata Manager and Composer
h. BOJ-EIM-RMA is used for RapidMarts, BOW
13. After choosing the component, fill in any remaining required/optional items. **Required fields under Problem Details are flagged with a red asterisk.
· In the Short Text box, enter a brief description of the question or issue.
· In the Long Text box, you can go into further detail about what you are seeing or questioning.
· On this page also you can select to attach files if needed (please zip your files).
· When you are finished you can either click on Save Message or Send Message. If you click on Save
Message, the message WILL NOT be sent to support, it will remain in the Draft section of your u201Cmy
Inboxu201D for you to send later.
· If you want to send the message to technical assurance now click Send Message.
· You can see the messages you have u201Csentu201D to support by clicking My Inbox and viewing your Sent
Items.
Thanks,
Kendra -
Efiicient Logistical Units - Shipping Discounts
Hi,
I have created a routine (RV64A988) in vofm in condition value..The requirement is to provide shipping discounts..These discounts are given to encourage Customers to order in shipment. They will be given as header conditions on the Sales Order and should be split down over the lines in proportion.
Condition maintained for the following Scales
7 -> 29 Pallets 23 EUR per Pallet
30 -> 55 Pallets 31 EUR per Pallet
56 -> 62 Pallets 37 EUR per Pallet
Sales Order for 1300 CS & Sales Order for 2000 CS (current sales order)
1. Calculate how many Pallets this equates to
a. Look at total Pallets field in Sales Orders and add up.
2. Check which rate this is in the Scale
a. Check 33 < 29. If yes stop, if not continue
b. Check 33 < 55. If yes stop, if not continue
c. Check 33 < 62. If yes stop
3. Calculate Condition amount
a. Sales Order 1 = 31 EUR * 13 = 403 EUR
b. Sales Order 2 = 31 EUR * 20 = 620 EUR
below is the code written by me..but its not working as required..
IF xkomv-kschl EQ 'ZFTD'.
CALL FUNCTION 'MARM_SINGLE_READ'
EXPORTING
KZRFB = ' '
MAXTZ = 0
MATNR = KOMP-MATNR
MEINH = 'PAL'
IMPORTING
WMARM = MARM
EXCEPTIONS
WRONG_CALL = 1
NOT_FOUND = 2
OTHERS = 3.
IF sy-subrc eq 0.
IF MARM-UMREZ GT 0.
ZZMGLME1 = komp-mglme / 1000.
ZZMGLME2 = ZZMGLME1 mod MARM-UMREZ.
ZZMGLME = ( ZZMGLME1 - ZZMGLME2 ) / marm-umrez.
ENDIF.
ENDIF.
select * from vbak into table it_vbak
where kunnr = komk-kunwe
AND VDATU = KOMK-VDATU.
if not it_vbak[] is initial.
clear: it_vbak.
loop at it_vbak.
ZZMGLME3 = ZZMGLME3 + it_vbak-ZZTOTPAL / 1000.
endloop.
ZZMGLME3 = ZZMGLME3 + ZZMGLME.
it_konm[] = h_mem_konm[].
loop at it_konm.
ZZMGLME4 = it_konm-kstbm / 1000.
check ZZMGLME3 GE ZZMGLME4.
if sy-subrc eq 0.
xkomv-kbetr = it_konm-kbetr.
xkwert = ZZMGLME * it_konm-kbetr.
endif.
endloop.
endif.Jakas,
This forum is for the "SQL Developer" tool - you might get a better response on the "SQL and PL/SQL" forum (PL/SQL).
theFurryOne -
Flat Mail not qualifying for Discount
I've selected an SCF for drop ship in my presort view job where the default Zip Ranges are populated.
However when the file is presorted, the zips that are qualifying are the Zips that are for letter sized pieces. The others are qualifying for no entry/no discount. Below is the entry point.
BEGIN Entry Point Description =================================
Entry Point Name (to 35 chars)....... = SCF-TAMPA L&DC
+ Value in PostWare Field Entry_ID... =
Entry Point Post Office City (20 chrs)= TAMPA
Entry Point Post Office State (2 chrs)= FL
Entry Point Post Office ZIP Code (10) = 33605-6001
Entry Point Drop Site Key (to 9 chars)= J007646
Entry Point Type (see NOTE).......... = SCF
Scheme Nums this Entry Pt (see NOTE). = ALL
Override USPS Mail Direct Disc (Y/N). = N
PER/STD/PSVC QFY for DDU Rate (Y/N).. = Y
PER/STD/PSVC Use USPS DDU Data(Y/N).. = Y
Origin Post Office City (to 20 chars) = BOCA RATON
Origin Post Office State (to 2 chars) = FL
Origin Post Office ZIP Code (10 chars)= 33431-6317
Origin Post Office ID (10 chars)..... =
FAST Content ID (9 chars)............ =
FAST Scheduler ID (12 chars)......... =
Create Undrfill Local 3DG/SCF Ctns Y/N= Y
Create Small Service Area Plt (Y/N).. = Y
Min SCF/ASF Local 3DG Pallet Weight.. = 250
Min SCF/ASF Local SCF Pallet Weight.. = 250
Min SCF/ASF Loc 3DG Plt Tray Ft(1-144)=
Min SCF/ASF Loc SCF Plt Tray Ft(1-144)=
Min Pieces (see NOTE)................ = 200
Min Pounds (see NOTE)................ = 50
PER IC Disc Eligibility(ALL/SUB/NONE) = NONE
PER County of Publication............ =
Estimated Drop Date (MMDDYYYY)....... = 01032011
Estimated Drop Time (HHMM)........... =
Appointment Number (12 chars)........ =
Del Window Start Date (MMDDYYYY)..... =
Del Window End Date (MMDDYYYY)....... =
IDEA Pstg Stmt Mlg Date (MMDDYYYY)... =
IDEA USPS Pick Up (Y/N/NONE)......... =
IDEA Scheduled Ship Date (MMDDYYYY).. =
IDEA Scheduled Ship Time (HHMM)...... =
IDEA CSA Agreement ID (10 chars)..... =
IDEA CSA Trip ID (10 chars).......... =
Range (lower ZIP-upper ZIP).......... = 33500-33999
PER/STD/PSVC Range QFY for DDU (Y/N). = no
Range (lower ZIP-upper ZIP).......... = 34100-34299
PER/STD/PSVC Range QFY for DDU (Y/N). = no
Range (lower ZIP-upper ZIP).......... = 34600-34699
PER/STD/PSVC Range QFY for DDU (Y/N). = no
ENDHere is an example:
USPS Qualification Report Postalsoft (R) Presort 8.00c.05.00 Page 16
Mailer Name: EARTH MEDIA Mail Id: 0003 Date: / /
Entry Point: (3) SCF-TAMPA L&DC, TAMPA, FL 33605-6001
Presort: (1) STD, Packages on Pallets CAR/ATM (DMM 705.8)
Pkg Running
Group Dest Zip Ver ID WS HD CR 5B 3B AB MB 5D 3D AD MD Totals
34228 All 24 12877
34229 All 38 12915
34235 All 53 12968
34287 All 32 13000
34293 All 78 13078
339S 339 All 85 13163
341 All 38 13201
337 All 42 13243
338 All 72 13315
342 All 28 13343
Pallet: 2 Pallet Dest: NDC 32099
Pallet Version Totals
Ver ID WS HD CR 5B 3B AB MB 5D 3D AD MD Wt (lbs)
All 0 0 494 7451 265 0 0 0 0 0 0 615.7500
Pallet Total 0 0 494 7451 265 0 0 0 0 0 0 615.7500
Pallet Rate Summary Pieces
Basic (CR) 494
TOTAL Carrier Route 494
Automation 5 Digit Barcode (5B) 7451
Automation 3 Digit Barcode (3B) 265
TOTAL Automation 7716
Pallet Total 8210
Pallet Total Weight: 615.7500 -
Hi,
We have a pallet created by Presort destined for SCF Oklahoma City, but it did not receive the SCF discount. It appears the SCF is open, so I'm not sure it didn't get the discount. Can anyone shed some light on this?
Thanks a lot,
BillI think the best thing to do is contact customer support directly. They will want to know the mail class, shape, and the presort level of the pallet in question.
Then they can look at [fast.usps.com|http://fast.usps.com] to see what kinds of mail that particular facility is accepting. -
Dear Guru
i have 3 customer, first customer order 5nos of XXX product and Second Customer order 10nos of XXX product and Third customer order 15nos of XXX product
condition, if customer order 1 to 5 means = 5% discount and 6 to 10 = 8% discount and 11 and above = 10% discount. how i can assing in pricing procedure.
regards
Mohammed Renu
[email protected]Hi
Try with<b> Scales in Condition</b> Record Use combination of Customer and Material discount as Condition type
VK11 SELECT THE CONDITION TYPE
enter the customer code and select scales on the tool bar <b>specify u r upper limit and lower limit and the discount %
OR ELSE TRY WITH THE FOLLOWING PROCEDURE</b>
You can try this :-
1. Define/Select a UOM for selling in bulk (i.e. cas, pallet, box whatever)
2. Maintain UOM conversion between your base UOM and this new UOM
3. Configure you bulk pricing condition type by usual means (it should be a base price rather than discount).
4. Place this new bulk price behind your normal "PR00" price in the pricing procedure
5. Create a new condition base value routine via VOFM where you check XKWERT to see if it is a whole number. If it is not then set XKWERT to zero.
6. Assign this new routine to your bulk price condition in your pricing procedure in ALT condition base value column.
7. Maintain bulk price condition record in the Bulk UOM.
Message was edited by:
SHESAGIRI.G
Maybe you are looking for
-
Hi, I am attempting to use the action framework within OBIEE 11g, specifically invoke a web service. When I go to New -> Action I get a server error: An error occured during processing of the SSL protocol 1093359936:error:14090086:SSL routines:SSL3_G
-
How convert pdf without damage the structure original file
I have a issue, when I converted a excel document to PDF this document damage the structure , I have 3 tables and it is disorganized. How can I conserve the original organization??
-
Fireworks web designs when using slices not rendering properly in IE
When I create web pages in Fireworks CS6 and use slice tool then export the html, IE 8 and 9 renders borders and misaligned pixels. But when I view the html in Chrome, Safari or Firefox the html pages are rendered as I want them to render. Am i doing
-
Can i use my ipad while it is charging?
Cna I use the ipad while it is plugged in and charging?
-
Does any one know how to replace the hd in a 12 inch PowerBook G4?
I need to find a manual for replacing the hard drive in a 12 inch PowerBook G4. Has anyone replaced the hard drive for the 12 inch PowerBook G4. Thanks