No cond in p.o print
Hello Sir,
I have maint two cond... 1) JES3 & 2) ZES3 for A service p.o.. in FV11, so these are get displaying in INVOIVE -
TAXES tab but not visible in print preview, as these
cond. are not visible in condition tab in ITEM DETAIL , pl guide me wat to do ? .wat to do to display these cond in print preview.
KM
for making conditions to appear at item level you have to go condition type and there you have to tick item condition if you wana to make it item condition .
Now you have to go to calculation schema and there you have to include this condition type .if you wanna to make condition as manaul then you have to tick the manaual conditon .if you dont make condition manual then automatically your condtion will come.if you have made other setting perfect and assigned vendor schema to vendor master.
If you wanna to print the these condition in the PO print then in calculation schema for the condition which you wanna to print set print indicator X.
they will be taken care in the print preview,
hope this will help you
regards
Similar Messages
-
No Cond. are appearing in Print Preview of P.O ?
Dear All Guru's ,
Kindly help as in print Preview only JMOP= 14% is appearing while the other condition which are maintained in FV11 are not displaying ( JEC1 & JSEP ) .Pl help what setting are to be done to display these conditions.
regards
sap11Hi,
The CIN conditions cannot be printed in PO, this is limited functionality. Read the note:
Note 952287 - CIN: Limited Functionalities in Country Version India
1. Printing of taxes in Purchase order
Please note that printing of taxes in PO is not supported by country version India. If you need to print the taxes then you need to bring them into the MM procedure using condition types. You may use the condition type JEXS to bring the total taxes into the pricing procedure. Assigning a print flag in tax procedure will not help you in printing taxes.
What you have to do is tell the ABAP programmer to get the calculation done is smartform program.
This is the way you can show the break up in printing.
I think some programme logic is given in some threads in Forum-ABAP General.
This can only be acheived by programming in smart form.
Regards
Rajesh -
Cond type to be printed in po but without calculation
Hi Experts,
I want to maintain one condition type in pricing procedure.
But it should be inactive in nature, it should not take part in landed cost calculation.
But it should be printed in PO.
Please suggest how can I achieve that.
RegardsHi,
Create a Condition type in M/06 as per ur requirement.
Add that Condition type in ur MM pricing procedure and tick the stastical check box and mark X in Print and try.
Regards
Edited by: Varaghamurthy Chakravarthy Kannan on Feb 18, 2009 2:01 PM -
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
VenkatHi 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.
ThanksHi
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 -
Why did I get a "You Have Missed a Print" message with Condé Nast At Home?
You will miss a scheduled print if your computer is turned off or not connected to the Internet, or if you are logged out. When you see the “You have missed a print” message, you can click Print to print now, or Skip.
You can set your Condé Nast At Home application to automatically do the same thing every time you miss a print.
Open the Condé Nast At Home application.
Click the wrench icon () to open the Settings dialog.
If you want missed items to print immediately when you log in, select Automatically. If you want to be asked before an item is printed, select When Prompted. If you always want to skip missed items, select Never.
Click Save in the Settings dialog to save your changes.
Did this answer your question? If it did, why not click the Kudos! button to the left?
If it didn’t answer your question about a printing problem, click Reply to ask the community, or search the forum for other posts that might help.
Or, click here to go back to the Guide to Printing Condé Nast At Home Scheduled Content.
Condé Nast At Home (c) 2011 Condé Nast. All Rights Reserved.
I work on HP's behalf.hi i'm a new user and i'd like to be able to print a PAST crossword from the Universal Crossword please know this is not a printing problem but i hope you will be able to help me find an archived crossword puzzle for April 24, 2012 Thank You!
-
How to print terms and cond of a PO in a fresh page in smartforms??
hi All,
My requirement is as follows...
i need to print terms and conditions of a purchase order after the main window and the amount has been printed. the terms and conditions should be in a fresh page. i.e if the line items items and the amounts window occupies two pages. then terms and conditions should be printed on a fresh page i.e 3. the terms and conditins are many so it will occupy a full page. how do i call this page after all line items are printed??
Any pointers reg this would be highly appreciated.
Regards,
Sreekanth.Hi,
do the following steps:
1.Create a New Page for Terms & Conditions (lets say Page3).
2.First u describe the no of lines in your Internal table into a variable.
3.In the LOOP create a counter & increase the counter for every line. also create another variable to set the flag when the Counter reaches the no of lines in internal table.
4.Now, write a condition in Program lines if Counter = No of Lines in internal table, set the flag variable to 'X'.
5.Now create a condition on Page, IF FLAG = 'X', GO TO PAGE 3.
Eg:
DATA : gv_counter TYPE i,
gv_lines TYPE i,
gv_flag.
describe table itab lines gv_lines.
LOOP AT itab.
clear : gv_flag.
gv_counter = gv_counter + 1.
IF gv_counter = gv_lines.
gv_flag = 'X'.
clear : gv_counter.
ENDIF.
Now U create a COMMAND in LOOP, Go to New Page (Give Page3) and conditions tab (write gv_flag = 'X').
endloop.
Hope it solves!!
Rgds,
Pavan -
I want cond type JIP5 used for vat reimbursable to be printed in PO
Hi Experts,
In our organization we are addressing vat reimbursable part by using tax code say R2, which is being chosen in invoice tab of item detail section in PO.
The condition type used JIP5 using taxinj, but when we take printout of the PO this condition not get printed, so supplier get confused that whether we are going to pay them vat or not.
Since this is not maintained in condition tab and is not an item condition so it is not getting printed.
Please guide how to tackle this situation so that the same get printed as well as the FI effects remain same as it is.
Regards,Hi,
If you are using SAP Standard print program and form for PO printout then go to OBQ3 and In Tax Procedure TAXINN, maintain the print indicator as X for Condition type JIP5 in "Print" column and check.
If it is a developed one then take help of ABAPer to get it printed. -
How do I set up my Condé Nast At Home scheduled content application?
The steps are pretty simple:
Open the Condé Nast At Home application. The application should open as soon as installation is complete. You can also open the program by clicking your desktop icon, or by clicking Start, then All Programs, then the name of the particular application.
To set up the application to print your Condé Nast At Home items, follow these steps:
(1) Select each of the days when you want prints.
(2) Select the time of day when you want your prints (these are in hourly slots).
(3) Select your printer from the list (PDF and XPS writers are not supported). .
(4) Don’t forget to click Save when you’re through!
You can also click the wrench icon () to open the Settings dialog, where you can:
(1) Turn Scheduled Printing On or Off (you might want to turn scheduled printing Off when you go on vacation, for instance).
(2) Set the desired action for when a scheduled print is missed. If you want the item to print immediately when you log in, select Automatically. If you want to be asked before an item is printed, select When Prompted. If you just want to skip missed items, select Never.
(3) Click Save in the Settings dialog to save your changes.
Don’t forget that on the days and times you’ve selected, your printer must be turned on, have paper, and be connected to your computer, and your computer must be on and connected to the Internet. Happy printing!
Did this answer your question? If it did, why not click the Kudos! button to the left?
If it didn’t answer your question about a printing problem, click Reply to ask the community, or search the forum for other posts that might help.
Or, click here to go back to the Guide to Printing Condé Nast At Home Scheduled Content.
Condé Nast At Home (c) 2011 Condé Nast. All Rights Reserved.
I work on HP's behalf.scooter has provided links to Apple's pages for the AirPort Express and AirPort Extreme base station (AEBS).
Both of these devices are IEEE 802.11g wireless routers (also called base stations). If you have an Ethernet connection to the Internet (for example DSL or cable modem), you can connect either of these devices directly to that connection and create a wireless network. Since Ethernet and IEEE 802.11g are worldwide standards you can connect any compatible device (including PCs running Windows).
Every computer needs a unique IP address. You can think of an IP address as a street address for your house. A unique address guarantees that items addressed to you get to you.
Typically ISPs provide users with a single (one) public IP address. A public IP address is visible to anyone on the Internet. A router uses the single IP address provided by the ISP and creates multiple local (non-public) IP addresses for you computers. This allows you to use multiple computers.
If you need to connect both wireless and Ethernet computers you will need the AEBS. The AEBS provides a separate LAN port for Ethernet computers.
BTW, you can accomplish the same thing with any inexpensive wireless router.
The advantage of the AEBS over other routers is (a) built-in 56k modem for connecting to a dial-up ISP and (b) USB port for a single compatible printer.
The advantage of the AirPort Express over other routers is (a) sound output port for streaming music to a stereo and (b) USB port for a single compatible printer. -
There is no printer output when using the PrintOut method
I have a VB6 app with CR XI, and a customer found a situation that when printing a report directly to the printer using the PrintOut method, there is no printer output or error message.
Some reports using the same code print normally, but a report that is preceded by another print call, presents this behavior.
And when the output is directed to the screen, we can see the report.
Could someone give me an idea of what is the problem?
Thanks,
Isis
SP - Brazil
The code used is below:
Set rpt = applic.OpenReport(App.Path & "SEFoto" + TipoRPT + ".rpt")
rpt.FormulaSyntax = crCrystalSyntaxFormula
rpt.FormulaFields.GetItemByName("Empresa").Text = "'" + Company + "'"
rpt.FormulaFields.GetItemByName("Idioma").Text = "'" + Idioma + "'"
rpt.FormulaFields.GetItemByName("Versao").Text = "'" + Versao + "'"
' ... Some lines to compose the selection formula
rpt.RecordSelectionFormula = Cond
' To evaluate the image length:
Arq = rsTMP3!FT_Arquivo
ImageScaling = FatorDeReducao(Arq, "F")
' To reduce the image length:
AchouOLE = False
For Each oSection In rpt.Sections
For Each oObject In oSection.ReportObjects
If oObject.Name = "PictureFoto" Then
Set oOleObject = oObject
AchouOLE = True
Exit For
End If
Next oObject
If AchouOLE Then Exit For
Next oSection
With oOleObject
.Suppress = True
.XScaling = ImageScaling ' 0.5 = 50%, 1 = 100%
.YScaling = ImageScaling
.Suppress = False
End With
Aguarde.Show 1
If DestinoRel = 9 Or DestinoRel = 1 Then ' Padrão ou impressora
rpt.PrintOut True ' <<<---- Here using true or false nothing happens
Else
PrintRPTtela rpt, "Fotos" ' <<<--- Here it works fine
End IfHi Isis,
Not sure if you have applied any service Packs to CR? If please do so and test again. Then you can upgrade to CR XI R2 for free, use your XI Keycode and download Service Pack 4 from this link:
https://smpdl.sap-ag.de/~sapidp/012002523100011802732008E/crxir2_sp4_full_build.exe
You'll find the distribution files for your app also from that same download area.
If you don't want to upgrade to XI R2 then download all patches from XI and test again. This issues rings a bell that it may have been fixed.
Thank you
Don -
HOW TO PRINT THE MATTER IN FOR ALL ENTRIES
HI HOW T PRINT THE FOR ALL ENTRIES MATTER
Hi Naresh,
You can only use FOR ALL ENTRIES IN ...WHERE ...in a SELECT statement.
SELECT ... FOR ALL ENTRIES IN itab WHERE cond returns the union of the solution sets of all SELECT statements that would result if you wrote a separate statement for each line of the internal table replacing the symbol itab-f with the corresponding value of component f in the WHERE condition.Duplicates are discarded from the result set. If the internal table itab does not contain any entries, the system treats the statement as though there were no WHERE cond condition, and selects all records (in the current client).
For example:
SELECT * FROM sflight INTO wa_sflight
FOR ALL ENTRIES IN ftab
WHERE CARRID = ftab-carrid AND
CONNID = ftab-connid AND
fldate = '20010228'.
This condition, return all entries of the sflight.
When using FOR ALL ENTRIES the number of matching records is restricted to the number of records in the internal table. If the number of records in the database tables is too large then join would cause overheads in performance. Additionally a JOIN bypasses the table buffering.
Thanks,
Reward If Helpful. -
Print Packing List from Delivery at Goods Issue
We are facing an issue with our packing list for a division we are going live with in three weeks. Our current business process for our plants already on SAP is to create the Packing List when the Delivery is created, with timing code "3" in the Packing List output condition, but to not print it until the "Check-in" button is clicked with the Shipment in VT02N based on an activity profile.
However, for the service shipments in this division going live August 1, we do not need to create a Shipment nor generate a Bill of Lading from VT02N. We will post goods issue from the Delivery itself, and we want the Packing List to print at the time of Post Goods Issue from the Delivery. We have an access sequence for these service Deliveries with Shipping Point/Distribution Channel/Delivery Type, so only Distribution Channel 02 Deliveries will have Goods Issue from the Delivery, but we are not sure how to get the Packing List to not print until Goods Issue. Any advice would be appreciated.
Regards,
Jeff StewartGo to IMG>Logistics Execution>Shipping> Basic Shipping Functions>Output Determination> Maintain Output Determination for Outbound Deliveries.
Select the Procedure you are using and check the control data to find the Cond. Type you are executing at the moment of the Outbound Delivery.
Check the fifth column and see you have plenty of options, check them out helped by an ABAP team member; if there is nothing already there, just ask him/her to create a new routine with the validation you need and set it there.
This is the same that Joao is suggesting I just went a little bit more in details.
Good luck Jeff! -
Not able to see Print Preview of Purchase Order.
Dear All ,
I m not able to see the Print preview of Purchase Order , as the P.O is well release , but as i m click on Print Preview , an info displays in task bar , -> " Error in OPEN_FORM for document 4501472103
Message no. ME142
Procedure
Report the error to your system administrator.
I request you to pl help how to fix this problem.
Rgds,
sap11thanx for your support , here i need to know one thing that i had gone to MN06 to display the cond. record , here for the output type i m using in P.O
Given below different key comb. are maintained for same p.o , but as p.o was created then in message tab the first combination of fax was displayed and for this combi when clicking on print preview the message came for " Error in open _form " .
1) P doc type / P. org./ Vendor = Medium = 2 ( fax) / Date / time = 1 , is maintained
2) P Doc. Type / P.org / Pgrp = Medium = 1 / date/ time = 1 is maintained.
3) P Doc. Type / P.org = Medium = 1 / date/ time = 1 is maintained
4)P org. = Medium = 1 / date/ time = 3 is maintained
Here my querry is that as medium = 1 ( print output ) is also maintain then why Other comb, were not triggered , why only Comb. for medium -=2 ( fax ) was trigered , and after that as i changed the medium to 1 , i m able to see print preview , why ?
why i m not able to see p prwe for medium 2 ?
Thanx n rgds,
sap11 -
I have an array that continues to print out null but when I trace it exactly after I store it, it stores what I want it to store. "White Bread"
Here is where the errors at:
int orderNum = 0;
while(orderNum < cartItems)
printItems = "<html>" + printItems + "<br>1" + itemNameStrings[orderNum] + "</html>";
System.out.println(printItems);//Trace
System.out.println(cartItems);//Trace
System.out.println(orderNum);//Trace
System.out.println(itemNameStrings[orderNum]);//Trace
orderNum++;
}And here is the whole project:
import java.io.*;
import javax.swing.*;
import java.awt.*;
import java.awt.event.*;
import java.util.*;
import javax.swing.border.*;
import java.text.*;
public class AdrianP1 implements ActionListener
//---------------GLOBAL DECLARING------------------
DecimalFormat Currency = new DecimalFormat("#0.00 dollars");//Currency
//Changing Variables (void)
String printItems = "Items";
int arraySize = 2;
String[] itemNameStrings;
boolean first = true;
boolean order = false;
String itemName = "Error";
double itemCost = 0.00;
int cartItems = 0;
//Main Frames
final JFrame frame = new JFrame("Subway Sandwich Store");
JFrame mainFrame = new JFrame("Subway Sandwich Store | Welcome");
JFrame menuFrame = new JFrame("Subway Sandwich Store | Main Menu");
JFrame instrucFrame = new JFrame("Subway Sandwich Store | Instructions");
JFrame playFrame = new JFrame("Subway Sandwich Store | Play Game");
JFrame breadFrame = new JFrame("Subway Sandwich Store | Order Bread");
JFrame toppingFrame = new JFrame("Subway Sandwich Store | Order Toppings");
JFrame condimentFrame = new JFrame("Subway Sandwich Store | Order Condiments");
JFrame confirmFrame = new JFrame("Subway Sandwich Store | Confirm Your Order");
JFrame cartFrame = new JFrame("Subway Sandwich Store | Your Cart");
//---Main Buttons---
final JButton mainMenuButton = new JButton("Main Menu");
final JButton mainMenuButton1 = new JButton("Main Menu");
final JButton mainMenuButton2 = new JButton("Main Menu");
final JButton mainMenuButton3 = new JButton("Main Menu");
final JButton goBackButton = new JButton("Go back");
final JButton goBackButton1 = new JButton("Go back");
final JButton goBackButton2 = new JButton("Go back");
final JButton goBackButton3 = new JButton("Go back");
final JButton goBackButton4 = new JButton("Go back");
final JButton playButton1 = new JButton("Order Now!");
final JButton playButton2 = new JButton("Order Now!");
final JButton instrucButton = new JButton("Instructions");
final JButton exitButton = new JButton("Exit");
//---Play Buttons---
final JButton checkButton = new JButton("Check Out");
final JButton checkButton1 = new JButton("Check Out");
final JButton cartButton = new JButton("Cart (" + cartItems + ")");
final JButton breadButton = new JButton("Bread");
final JButton toppingsButton = new JButton("Toppings");
final JButton condimentsButton = new JButton("Condiments");
//-------Bread------
double bwCost = 0.50, bwlCost = 0.50, biCost = 0.75, bhCost = 0.50;
boolean whiteB = false, wholeB = false, italB = false, harvestB = false;
final JButton whiteBreadButton = new JButton("Order White");
final JButton wholeBreadButton = new JButton("Order Wheat");
final JButton italianBreadButton = new JButton("Order Italian");
final JButton harvestBreadButton = new JButton("Oder Harvest");
//-----Toppings-----
JButton orderTopButton = new JButton("Order the Selected Topping");
JLabel pictureTop;
JComboBox toppingList;
//----Condiments----
final JButton ketchupButton = new JButton("Order Ketchup");
final JButton mustardButton = new JButton("Order Mustard");
final JButton relishButton = new JButton("Order Relish");
//-----Confirm------
final JLabel confirmTextLabel;
final JButton acceptButton = new JButton("Accept");
final JButton declineButton = new JButton("Decline");
//----Cart Screen---
final JLabel cartItemLabel = new JLabel("<html><u>Items</u><br>No Items.</html>", JLabel.LEFT);
final JLabel cartPriceLabel = new JLabel("<html><u>Price</u><br>No Items.</html>");
//-------------END GLOBAL DECLARING-----------------
//ActionPerformed Method
public void actionPerformed(ActionEvent event)
if(event.getSource()==mainMenuButton || event.getSource()==mainMenuButton1 || event.getSource()==mainMenuButton2 || event.getSource()==mainMenuButton3)
playFrame.setVisible(false);
mainFrame.setVisible(false);
instrucFrame.setVisible(false);
menuFrame.setVisible(true);
if(event.getSource()==goBackButton || event.getSource()==goBackButton1 || event.getSource()==goBackButton2 || event.getSource()==goBackButton3 || event.getSource()==goBackButton4)
cartFrame.setVisible(false);
confirmFrame.setVisible(false);
condimentFrame.setVisible(false);
toppingFrame.setVisible(false);
breadFrame.setVisible(false);
instrucFrame.setVisible(false);
playFrame.setVisible(true);
if(event.getSource()==instrucButton)
menuFrame.setVisible(false);
instrucFrame.setVisible(true);
if(event.getSource()==playButton1 || event.getSource()==playButton2)
instrucFrame.setVisible(false);
menuFrame.setVisible(false);
playFrame.setVisible(true);
if(event.getSource()==breadButton)
playFrame.setVisible(false);
menuFrame.setVisible(false);
breadFrame.setVisible(true);
if(event.getSource()==toppingsButton)
playFrame.setVisible(false);
toppingFrame.setVisible(true);
if(event.getSource()==condimentsButton)
playFrame.setVisible(false);
condimentFrame.setVisible(true);
if(event.getSource()==acceptButton)
++arraySize;
itemNameStrings = new String[arraySize];
itemNameStrings[cartItems] = itemName;
System.out.println(itemNameStrings[cartItems]);
cartItems++;
cartButton.setText("Cart (" + cartItems + ")");
confirmFrame.setVisible(false);
playFrame.setVisible(true);
if(event.getSource()==declineButton)
confirmFrame.setVisible(false);
playFrame.setVisible(true);
if(event.getSource()==cartButton)
int orderNum = 0;
while(orderNum < cartItems)
printItems = "<html>" + printItems + "<br>1" + itemNameStrings[orderNum] + "</html>";
System.out.println(printItems);//Trace
System.out.println(cartItems);//Trace
System.out.println(orderNum);//Trace
System.out.println(itemNameStrings[orderNum]);//Trace
orderNum++;
cartItemLabel.setText(printItems);
System.out.println(printItems);
playFrame.setVisible(false);
cartFrame.setVisible(true);
if(order==true)
if(event.getSource()==whiteBreadButton)
whiteB = true;
itemName = "White Bread";
itemCost = bwCost;
confirmTextLabel.setText("<html>Would you like to purchase <u>" + itemName + "</u> <br>for a cost of <u>$" + Currency.format(itemCost) + "</u>?</html>");
breadFrame.setVisible(false);
confirmFrame.setVisible(true);
if(event.getSource()==wholeBreadButton)
wholeB = true;
confirmFrame.setVisible(true);
if(event.getSource()==italianBreadButton)
italB = true;
confirmFrame.setVisible(true);
if(event.getSource()==harvestBreadButton)
harvestB = true;
confirmFrame.setVisible(true);
if(event.getSource()==exitButton)
System.exit(0);
if(event.getSource()==toppingList)
JComboBox cb = (JComboBox)event.getSource();
String toppingName = (String)cb.getSelectedItem();
updateLabel(toppingName);
//Main Method
public static void main(String[] args) throws Exception
new AdrianP1();
//Constructive and Starting Method
AdrianP1()
//--------------------------Action Listeners----------------------------------
//Creates all action listeners
mainMenuButton.addActionListener(this);
mainMenuButton1.addActionListener(this);
mainMenuButton2.addActionListener(this);
mainMenuButton3.addActionListener(this);
goBackButton.addActionListener(this);
goBackButton1.addActionListener(this);
goBackButton2.addActionListener(this);
goBackButton3.addActionListener(this);
goBackButton4.addActionListener(this);
exitButton.addActionListener(this);
instrucButton.addActionListener(this);
playButton1.addActionListener(this);
playButton2.addActionListener(this);
breadButton.addActionListener(this);
toppingsButton.addActionListener(this);
condimentsButton.addActionListener(this);
//Bread buttons
whiteBreadButton.addActionListener(this);
//Final buttons
cartButton.addActionListener(this);
acceptButton.addActionListener(this);
declineButton.addActionListener(this);
//--------------------------Splash Screen----------------------------------
//Declaring
order = false;
final ImageIcon welcomePic = new ImageIcon("welcome.jpg");
final JPanel sMainPanel = new JPanel(new BorderLayout());
final JPanel sTopPanel = new JPanel(new BorderLayout());
final JPanel sButtonPanel = new JPanel(new FlowLayout ());
final JLabel sTextLabel = new JLabel("Please click the button below", JLabel.CENTER);
final JLabel label = new JLabel("Subway Sandwich Store");
final JLabel welcomeLPic = new JLabel(welcomePic);
sTopPanel.add(welcomeLPic , BorderLayout.NORTH);
sTopPanel.add(sTextLabel);
sButtonPanel.add(mainMenuButton1);
sMainPanel.add(sTopPanel , BorderLayout.CENTER);
sMainPanel.add(sButtonPanel , BorderLayout.SOUTH);
mainFrame.setContentPane(sMainPanel);
mainFrame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
mainFrame.pack();
mainFrame.setVisible(true);
mainFrame.setSize(350,390);
//--------------------------Main Menu----------------------------------
//Declaring
order = false;
final ImageIcon mainMenuImage = new ImageIcon("mainMenuImage.jpg");
final JPanel mMainPanel = new JPanel(new BorderLayout());
final JPanel mTopPanel = new JPanel(new BorderLayout());
final JPanel mButtonPanel = new JPanel(new FlowLayout());
final JLabel imageLabel = new JLabel(mainMenuImage);
final JLabel textLabel = new JLabel("Please click a button", JLabel.CENTER);
mTopPanel.add(imageLabel , BorderLayout.NORTH);
mTopPanel.add(textLabel , BorderLayout.CENTER);
mButtonPanel.add(playButton1);
mButtonPanel.add(instrucButton);
mButtonPanel.add(exitButton);
mMainPanel.add(mTopPanel, BorderLayout.CENTER);
mMainPanel.add(mButtonPanel, BorderLayout.SOUTH);
menuFrame.setContentPane(mMainPanel);
menuFrame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
menuFrame.pack();
menuFrame.setVisible(false);
menuFrame.setSize(350,390);
//--------------------------Instructions----------------------------------
//Declaring
order = false;
final JPanel iTopPanel = new JPanel(new BorderLayout());
final JPanel iButtonPanel = new JPanel(new FlowLayout());
final JPanel iMainPanel = new JPanel(new BorderLayout());
final JLabel iTextLabel = new JLabel("Instructions go HRER!", JLabel.CENTER);
iTopPanel.add(iTextLabel);
iButtonPanel.add(mainMenuButton3);
iButtonPanel.add(playButton2);
iMainPanel.add(iTopPanel, BorderLayout.CENTER);
iMainPanel.add(iButtonPanel, BorderLayout.SOUTH);
iTopPanel.setBorder(BorderFactory.createTitledBorder("Instructions"));
instrucFrame.setContentPane(iMainPanel);
instrucFrame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
instrucFrame.pack();
instrucFrame.setVisible(false);
instrucFrame.setSize(350,390);
//--------------------------Play Game----------------------------------
//Declaring
order = false;
final ImageIcon playImage = new ImageIcon("playGameImage.jpg");
final JPanel pTopPanel = new JPanel(new BorderLayout());
final JPanel pInstrucPanel = new JPanel(new FlowLayout());
final JPanel pButtonPanel = new JPanel(new FlowLayout());
final JPanel pButton1Panel = new JPanel(new FlowLayout());
final JPanel pButton2Panel = new JPanel(new FlowLayout());
final JPanel pMainPanel = new JPanel(new BorderLayout());
final JLabel pImageLabel = new JLabel(playImage);
final JLabel pTextLabel = new JLabel("Click below to customize your sandwich; or check out", JLabel.CENTER);
pTopPanel.add(pButton2Panel, BorderLayout.NORTH);
pTopPanel.add(pImageLabel, BorderLayout.CENTER);
pInstrucPanel.add(pTextLabel, BorderLayout.SOUTH);
pButton1Panel.add(breadButton);
pButton1Panel.add(toppingsButton);
pButton1Panel.add(condimentsButton);
pButton2Panel.add(checkButton);
pButton2Panel.add(cartButton);
pButton2Panel.add(mainMenuButton2);
pButtonPanel.add(pButton1Panel);
pMainPanel.add(pTopPanel, BorderLayout.NORTH);
pMainPanel.add(pInstrucPanel, BorderLayout.CENTER);
pMainPanel.add(pButtonPanel, BorderLayout.SOUTH);
pInstrucPanel.setBorder(BorderFactory.createTitledBorder("Instructions"));
playFrame.setContentPane(pMainPanel);
playFrame.setDefaultCloseOperation(playFrame.EXIT_ON_CLOSE);
playFrame.pack();
playFrame.setVisible(false);
playFrame.setSize(350,390);
//--------------------------Order Bread----------------------------------
//Declaring
order = true;
final ImageIcon whiteBImage = new ImageIcon("whiteB.jpg");
final ImageIcon wheatBImage = new ImageIcon("wheatB.jpg");
final ImageIcon italianBImage = new ImageIcon("italianB.jpg");
final ImageIcon harvestBImage = new ImageIcon("harvestB.jpg");
final JPanel bTopPanel = new JPanel(new GridLayout(0,2));
final JPanel bCenterPanel = new JPanel(new FlowLayout());
final JPanel bButtonPanel = new JPanel(new FlowLayout());
final JPanel bMainPanel = new JPanel(new BorderLayout());
final JLabel whiteBLabel = new JLabel(whiteBImage);
final JLabel wheatBLabel = new JLabel(wheatBImage);
final JLabel italianBLabel = new JLabel(italianBImage);
final JLabel harvestBLabel = new JLabel(harvestBImage);
final JLabel bInstrucTextLabel = new JLabel("Please click the button below a bread to choose", JLabel.CENTER);
bTopPanel.add(whiteBLabel);
bTopPanel.add(wheatBLabel);
bTopPanel.add(whiteBreadButton);
bTopPanel.add(wholeBreadButton);
bTopPanel.add(italianBLabel);
bTopPanel.add(harvestBLabel);
bTopPanel.add(italianBreadButton);
bTopPanel.add(harvestBreadButton);
bCenterPanel.add(bInstrucTextLabel);
bButtonPanel.add(goBackButton1);
bMainPanel.add(bTopPanel, BorderLayout.NORTH);
bMainPanel.add(bCenterPanel, BorderLayout.CENTER);
bMainPanel.add(bButtonPanel, BorderLayout.SOUTH);
bTopPanel.setPreferredSize(new Dimension(200, 270));
bTopPanel.setMinimumSize(new Dimension(200,270));
bTopPanel.setMaximumSize(new Dimension(200,270));
bCenterPanel.setBorder(BorderFactory.createTitledBorder("Instructions"));
breadFrame.setContentPane(bMainPanel);
breadFrame.setDefaultCloseOperation(breadFrame.EXIT_ON_CLOSE);
breadFrame.pack();
breadFrame.setVisible(false);
breadFrame.setSize(350,390);
//--------------------------Order Toppings----------------------------------
//Declaring
order = true;
final JPanel tTopPanel = new JPanel(new FlowLayout());
final JPanel tCenterPanel = new JPanel(new FlowLayout());
final JPanel tActionPanel = new JPanel(new BorderLayout());
final JPanel tButtonPanel = new JPanel(new FlowLayout());
final JPanel tMainPanel = new JPanel(new BorderLayout());
final JLabel tInstrucTextLabel = new JLabel("<html>Please select a topping from the drop down list above<br> and then click order</html>");
//Creates list of toppings - file paths must match name
String[] toppingStrings = { "Olives", "Tomatoes", "Lettuce", "Turkey", "Ham", "Select a Topping"};
pictureTop = new JLabel();
//Selects item at index 5
toppingList = new JComboBox(toppingStrings);
toppingList.setSelectedIndex(5);
tActionPanel.add(toppingList , BorderLayout.NORTH);
tActionPanel.add(pictureTop , BorderLayout.CENTER);
tActionPanel.add(orderTopButton , BorderLayout.SOUTH);
tCenterPanel.add(tInstrucTextLabel);
tButtonPanel.add(goBackButton2);
tMainPanel.add(tActionPanel , BorderLayout.NORTH);
tMainPanel.add(tCenterPanel , BorderLayout.CENTER);
tMainPanel.add(tButtonPanel , BorderLayout.SOUTH);
//Must go in this method, do not put in main
toppingList.addActionListener(this);
pictureTop.setFont(pictureTop.getFont().deriveFont(Font.ITALIC));
pictureTop.setHorizontalAlignment(JLabel.CENTER);
updateLabel(toppingStrings[toppingList.getSelectedIndex()]);
pictureTop.setBorder(BorderFactory.createEmptyBorder(10,0,0,0));
//Preferred size - widest image and the height of the tallest image
pictureTop.setPreferredSize(new Dimension(177, 132));
tCenterPanel.setBorder(BorderFactory.createTitledBorder("Instructions"));
toppingFrame.setContentPane(tMainPanel);
toppingFrame.setDefaultCloseOperation(toppingFrame.EXIT_ON_CLOSE);
toppingFrame.pack();
toppingFrame.setVisible(false);
toppingFrame.setSize(350,390);
//--------------------------Order Condiments----------------------------------
//Declaring
order = true;
final ImageIcon condimentsImage = new ImageIcon("condiments.gif");
final JPanel cTopPanel = new JPanel(new FlowLayout());
final JPanel cCenterPanel = new JPanel(new FlowLayout());
final JPanel cButtonPanel = new JPanel(new BorderLayout());
final JPanel cMainPanel = new JPanel(new BorderLayout());
final JLabel cInstrucTextLabel = new JLabel("<html>Please select a button below to order a Condiment</html>", JLabel.CENTER);
final JLabel condimentsLabel = new JLabel(condimentsImage);
cTopPanel.add(goBackButton3);
cTopPanel.add(condimentsLabel);
cCenterPanel.add(cInstrucTextLabel);
cButtonPanel.add(mustardButton , BorderLayout.WEST);
cButtonPanel.add(ketchupButton , BorderLayout.CENTER);
cButtonPanel.add(relishButton , BorderLayout.EAST);
cMainPanel.add(cTopPanel , BorderLayout.NORTH);
cMainPanel.add(cCenterPanel , BorderLayout.CENTER);
cMainPanel.add(cButtonPanel , BorderLayout.SOUTH);
cCenterPanel.setBorder(BorderFactory.createTitledBorder("Instructions"));
condimentFrame.setContentPane(cMainPanel);
condimentFrame.setDefaultCloseOperation(condimentFrame.EXIT_ON_CLOSE);
condimentFrame.pack();
condimentFrame.setVisible(false);
condimentFrame.setSize(350,390);
//--------------------------Confirmation Screen----------------------------------
final JPanel coMainPanel = new JPanel(new BorderLayout());
confirmTextLabel = new JLabel("<html>Would you like to purchase <u>" + itemName + "</u> <br>for a cost of <u>$" + Currency.format(itemCost) + "</u>?</html>", JLabel.CENTER);
final JPanel coTopPanel = new JPanel(new FlowLayout());
final JPanel coButtonPanel = new JPanel(new FlowLayout());
final JPanel coCenterPanel = new JPanel(new FlowLayout());
coTopPanel.add(goBackButton);
coCenterPanel.add(confirmTextLabel);
coButtonPanel.add(acceptButton);
coButtonPanel.add(declineButton);
coMainPanel.add(coTopPanel , BorderLayout.NORTH);
coMainPanel.add(coCenterPanel , BorderLayout.CENTER);
coMainPanel.add(coButtonPanel , BorderLayout.SOUTH);
coCenterPanel.setBorder(BorderFactory.createTitledBorder("Correct?"));
confirmFrame.setContentPane(coMainPanel);
confirmFrame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
confirmFrame.pack();
confirmFrame.setVisible(false);
confirmFrame.setSize(350,390);
//------------------------------Cart Screen----------------------------------
final JPanel caMainPanel = new JPanel(new BorderLayout());
final JPanel cartRPanel = new JPanel(new BorderLayout());
final JPanel caButtonPanel = new JPanel(new FlowLayout());
final JPanel caCenterPanel = new JPanel(new FlowLayout());
caCenterPanel.add(cartRPanel);
cartRPanel.add(cartItemLabel , BorderLayout.WEST);
cartRPanel.add(cartPriceLabel , BorderLayout.EAST);
caButtonPanel.add(goBackButton4);
caButtonPanel.add(checkButton1);
caMainPanel.add(caCenterPanel , BorderLayout.CENTER);
caMainPanel.add(caButtonPanel , BorderLayout.SOUTH);
//cartItemLabel.setAlignmentX(Component.LEFT_ALIGNMENT);
//cartItemLabel.setHorizontalTextPosition(SwingConstants.LEFT);
caCenterPanel.setBorder(BorderFactory.createTitledBorder("Your Items"));
cartFrame.setContentPane(caMainPanel);
cartFrame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
cartFrame.pack();
cartFrame.setVisible(false);
cartFrame.setSize(350,390);
//--------------------------End of Constructive Method---------------------------
//Updates the label when combo box is changed
protected void updateLabel(String name)
ImageIcon icon = createImageIcon("images/" + name + ".jpg");
//Sets the image of the icon
pictureTop.setIcon(icon);
if (icon != null)
pictureTop.setText(null);
else
pictureTop.setText("Image not found");
//Returns an ImageIcon, or null if the path was invalid to the icon
protected static ImageIcon createImageIcon(String path)
java.net.URL imgURL = AdrianP1.class.getResource(path);
if (imgURL != null)
return new ImageIcon(imgURL);
else
//Prints out if file is not found in system window
System.out.println("Couldn't find file: " + path);
return null;
public void updateConfirm()
//------------------NOT IN USE-------------------
if(whiteB==true)
itemName = "White Bread";
itemCost = bwCost;
if(wholeB==true)
if(italB==true)
if(harvestB==true)
//------------------NOT IN USE-------------------
public void receiptPrint ()
//------------------NOT IN USE-------------------
final JLabel receiptLabel = new JLabel("<html>Your PST:<br>Your GST:<br>Your Total:</html>");
final JPanel receiptPanel = new JPanel(new FlowLayout());
receiptPanel.add(receiptLabel);
receiptLabel.setFont(new Font("Serif", Font.PLAIN, 15));
receiptPanel.setBorder(BorderFactory.createTitledBorder("Your Receipt"));
//------------------NOT IN USE-------------------
}I'm certainly not going to read all of that, perhaps someone else here will.You really think so? I seriously doubt it.
@OP: Please go through these links:
[How to ask questions the smart way|http://catb.org/~esr/faqs/smart-questions.html]
SSCCE
db -
Dear Experts,
As per our business scenario presently we are creating Proforma Invoice with reference to Sales Order number and taking print out of respective output. But now we are facing some problems from user level. Now we have decided to keep proforma Invoice but we don't want to take print of this, we just want to preview/display of that. Can you please advice me whether it is possible or not. How can I stop printing of that?
Your suggestions will be highly appreciated.
Best Regards.
Ripon Kumar PaulIf I want to stop Proforma Invoice service for any particular document type then how can I do that?
If you mean -
For sales doc type OR, RO you would like to have printouts of Proforma invoice; & for Z1OR you would NOT like to have printout of Proforma invoice, then -
You have to create a condition table with fields Billing Type, Sales doc type
This condition table you have to put in your access seq (0001)
Then in VV31, you have to create condition tables for F5, OR; F5, RO but NOT for F5, Z1OR. By this way, system shall NOT find valid condition record RD00 specifically for Z1OR thus NO printout of Proforma invoice for Z1OR, but shall find and print for OR and RO.
Please note you shall have to delete the cond record for cond table Billing type; as already advised.
Maybe you are looking for
-
How can i use paypal for my funding source
I've set it up and authorized it thru paypal, but it still does not pay my ballance. I can't update any apps or even download free ones, because I have a $2 ballance. I want to use my paypal account to pay this. Any ideas???
-
Hi, I need to get the long text that we maintained in CJ20n tcode under long text at project level. I need to display the same in Script layout or report. I didnot find any table or functional module to get it. please help me out. regards, Chandra
-
Hi. I have an old macbook but currently it is not working as the charger was spoilt (I threw it away) and i have yet to get a new one. just a few months ago, my family bought a mac desktop. however, since i have not yet backed up or retrieve the file
-
How to really "share" library, not just stream?
My husband and I each have a macbook. I have 99% of the music on my computer and "share" my library with him. In iPhoto I do the same thing so he can drag the photos he wants onto his will the rest stay on my computer. He is unable to drag music onto
-
Having just completed a back up with time machine prior to upgrading the browser I cannot locate the 13,000 images that I have stored in iphoto, neither on time machine nor the external hard drive. Where would they be? I have checked several other