Proposed pricing

Hi
I do some stuff for non-profit bodies, and some educational bodies, these are usually strapped for any money at all, I was just wondering if the new pricing model might reflect these kind of organisations who might opt for DW as a Web editor & have chosen this due to the InContext option to allow oganisational members to edit the pages, and if Adobe might consider keeping InContext free for non-profits & educational sites.
Obviously Adobe needs to make money it's a business but if Incontext stays free for at least some of us it's a big incentive to keep on being a DW user, buy new licenses when new versions come out and so on, I must say Incontext is a BIG selling point for anyone who needs to give access to non-techies. When the pricing starts to happen you'll probably see companies with the cash keeping on with InContext but non-profits will proably be forced to consider transfering their sites to free Wikis and things like this, with the loss of the Adobe license free and conversion of their approach to web development from traditional editors to alternative Web 2.0 solutions offered online (which are very attractive to organisations like this). The advantage of InContext over Web 2.0 is the integrated, simplified interface, but given the choice or paying a reaccuring free or going with the WIki most will ditch DW (and maybe associated products like Fireworks, Acrobat and Flash used to do Web development) altogether and go with the WIki option. If Incontext however stays free for some users it would seriously hold the web development market, as it's a much more attractive solution than a lot of other open source cms, wikis etc.

Thanks for your feedback wylfa1. I will pass it along to the product team.
Best regards,
Corey

Similar Messages

The proposed pricing for this wonderful program

I really like this program and see the pricing starting in April will be around $19 per month. That may be great for agencies. Will there be a separate licensing fee for freelancers? I'm willing to pay $75 per year.

Hello testerddrrttd,
Thank you, we're glad you like BrowserLab. We're going to make a pricing announcement in a couple of weeks, so stay tuned.
Regards,
Bruce

New "throttled" ICE pricing model proposal to Adobe

First off I agree that the ICE service should not be free, but for it to be worth while from a business standpoint, and at $20 per month paid to Adobe, the "web shop" would need to charge at least $10 per month to each client to use the service. It's a given that most clients won't want to pay more than $10 a month for the ICE service unless their web site is a large one. So if Adobe needs $20 a month for 5 domains in the current price proposal, the web shop would need to have 2 clients using it right away just to break even and acquire 3 clients just to start making a profit. The proposed pricing model puts much more "pressure" on the web shop's side to sign people up on the service as fast as possible starting out. The situation becomes even more evident if the web shop has 6 clients and is now paying $40 a month to Adobe for two base accounts. With 5 clients and one base account the web shop profits $50-($20 to Adobe)=$30 total per month. With 6 clients and two base accounts the web shop profit takes a dip with $60-($40 to Adobe)=$20 total profit per month. So the current pricing model becomes a kind of stair-stepping profit and loss situation for the web shop when they don't have each base account "loaded up" per say.
A MUCH better pricing strategy for both Adobe and web shop owners would be for Adobe to create an initial 3 domain base account for $10 a month and then "throttle the price" for each additional domain. This would lower the initial profit risk for the web shop greatly. Let me illustrate... Let's say Adobe charges a base price of $10 a month for a 3 domain base account to start with. Then for every NEW domain there is an additional $5 a month charge. Ok, so let's say the web shop has 5 client domains... now we have a a base price of $10 (3 domains in the base) + 2 NEW domains and that's a total of a $20 total per month paid to Adobe. Now for 5 domains Adobe is STILL making the $20 a month it needs. At this point though, the web shop has 5 committed ICE clients and is charging a minimum of $10 per domain so they receive $50 per month minus the $20 paid back to Adobe for a total profit of $30 per month. If the web shop has 6 client domains then the total profit is $25 to Adobe rather than having to pay $40 per month with the current proposed pricing model. Now we must look at how this pricing strategy "benefits" Adobe, because at 6 domains Adobe was previously getting $40 for two base accounts with 5 domains in each. BUT if they go with a throttled pricing model those same 10 domains now would mean $45 per month ($10 base + 7 new domains at $5 each for $35) instead of the previous $40 per month for Adobe. Ok, wait a second (I can hear most of you saying it now) why would we now pay Adobe an extra $5 per month for 10 domains? The answer is simple, because previously they would be getting $40 a month for say 6 domains whereas now they would only get (($10 + 3 new domains x $5 each = $15)) = a total of $25 per month for 6 domains. This is very fair because Adobe now takes on a lower rate per month as the domain counts ramp up, but now at the 10 domain mark they would be getting $45 per month instead of $40.
Overall this strategy eliminates the starting risk for the web shop, ensures the web shop's profit right away, and in the long run Adobe profits a little bit more for higher domains counts. Both sides get a much better deal with a throttled pricing model!
And as a last note of "profitable hope" for the web shop readers, you could also base your ICE monthly service price on the size of each client's web site. For example: 20 pages or less = $10 per month, 21- 50 pages = $15 per month and for large web sites above 50 pages you could go with $20 per month. This is actually still fair, because if you think about it you still have to provide ICE code support for each page should something go wrong and provide support for ICE user e-mail questions, training, etc. So the more page support you have to deal with code-wise, e-mail-wise, or even phone-wise the more it should justify a higher monthly cost back to your client for having a larger web site to maintain overall.

First off I agree that the ICE service should not be free, but for it to be worth while from a business standpoint, and at $20 per month paid to Adobe, the "web shop" would need to charge at least $10 per month to each client to use the service. It's a given that most clients won't want to pay more than $10 a month for the ICE service unless their web site is a large one. So if Adobe needs $20 a month for 5 domains in the current price proposal, the web shop would need to have 2 clients using it right away just to break even and acquire 3 clients just to start making a profit. The proposed pricing model puts much more "pressure" on the web shop's side to sign people up on the service as fast as possible starting out. The situation becomes even more evident if the web shop has 6 clients and is now paying $40 a month to Adobe for two base accounts. With 5 clients and one base account the web shop profits $50-($20 to Adobe)=$30 total per month. With 6 clients and two base accounts the web shop profit takes a dip with $60-($40 to Adobe)=$20 total profit per month. So the current pricing model becomes a kind of stair-stepping profit and loss situation for the web shop when they don't have each base account "loaded up" per say.
A MUCH better pricing strategy for both Adobe and web shop owners would be for Adobe to create an initial 3 domain base account for $10 a month and then "throttle the price" for each additional domain. This would lower the initial profit risk for the web shop greatly. Let me illustrate... Let's say Adobe charges a base price of $10 a month for a 3 domain base account to start with. Then for every NEW domain there is an additional $5 a month charge. Ok, so let's say the web shop has 5 client domains... now we have a a base price of $10 (3 domains in the base) + 2 NEW domains and that's a total of a $20 total per month paid to Adobe. Now for 5 domains Adobe is STILL making the $20 a month it needs. At this point though, the web shop has 5 committed ICE clients and is charging a minimum of $10 per domain so they receive $50 per month minus the $20 paid back to Adobe for a total profit of $30 per month. If the web shop has 6 client domains then the total profit is $25 to Adobe rather than having to pay $40 per month with the current proposed pricing model. Now we must look at how this pricing strategy "benefits" Adobe, because at 6 domains Adobe was previously getting $40 for two base accounts with 5 domains in each. BUT if they go with a throttled pricing model those same 10 domains now would mean $45 per month ($10 base + 7 new domains at $5 each for $35) instead of the previous $40 per month for Adobe. Ok, wait a second (I can hear most of you saying it now) why would we now pay Adobe an extra $5 per month for 10 domains? The answer is simple, because previously they would be getting $40 a month for say 6 domains whereas now they would only get (($10 + 3 new domains x $5 each = $15)) = a total of $25 per month for 6 domains. This is very fair because Adobe now takes on a lower rate per month as the domain counts ramp up, but now at the 10 domain mark they would be getting $45 per month instead of $40.
Overall this strategy eliminates the starting risk for the web shop, ensures the web shop's profit right away, and in the long run Adobe profits a little bit more for higher domains counts. Both sides get a much better deal with a throttled pricing model!
And as a last note of "profitable hope" for the web shop readers, you could also base your ICE monthly service price on the size of each client's web site. For example: 20 pages or less = $10 per month, 21- 50 pages = $15 per month and for large web sites above 50 pages you could go with $20 per month. This is actually still fair, because if you think about it you still have to provide ICE code support for each page should something go wrong and provide support for ICE user e-mail questions, training, etc. So the more page support you have to deal with code-wise, e-mail-wise, or even phone-wise the more it should justify a higher monthly cost back to your client for having a larger web site to maintain overall.

CIN-Pricing Procedure for Trading Goods

Hi Gurus
Need yr expertise... Currently we have trading goods process which do not require any excise duties but VAT or CST is required.. Could you pls advise what will be the best pricing procedure to be used as the proposed pricing procedure by SAP (JFACT or JDEPOT) cannot be used as it will propose excise invoice?
If we do not maintain any excise duties in J1ID, system will not prpose any excise duties if we were to use either of the suggested pricing procedure but we will hit a warning message that excise duties are missing in J1ID..
How can we avoid this and what will be the best pricing procedure which do not require excise duties but sales tax is required?
Rgds..Vinz

Hi Vinz,
you can make your won pricing proced.
e.g. ZMKTPRICE
here you can use your regular condition type what you have defined.
e.g PR00-Sale Price
K007-Discount
MWST= 4% or 12.5 (PR00-K007).
I think this will help you.
Best Regards
Sainath

Significance of pricing date and delivery date.

Hello guys,
    Can any one explain the significance of pricing date field in
             1) Sales order
             2)Details screen of Condition type .in v/06 screen
             3) Copy controls.
Regards,
k.Vivek

Dear K.Vivek,
http://sap-img.com/sd013.htm
Pricing date based on delivery date
Used transaction VOV8.
This configuration is by order type.
There is a field called proposal for pricing date.
There you can select pricing date as requested delivery date.
A - Proposed pricing date based on the requested dlv.date (Header)
This control is set at the document level as oppose to the condition type level (PR00).
That means your other condition types such as surcharges and discounts are also determined using the requested delivery date.
If your requirement is for PR00 to alone to be priced at delivery date then this will not work.
How pricing date is determine in the sales order and billing document? Where is the setting?
The pricing date is proposed based on the setting you make in the Sales document configuration. ( T code : VOV8)
You have a field" Prop.f.pricing date " in the Requested delivery date / pricing date / purchase order date segment.
Then you can choose the follwoing options:
Blank - Indicates the current date as the pricing date
A - Indicates the date based on the requested delivery date
B - Indicates the date based on the order validity start from date
And the pricing in the billing document is copied from thte sales order / Delivery document..
It again depends on the setting u have in the copy control from order - billng or delivery - billing.
In the copy control, in the item settings you have two fields relavant for this.
One is pricing source and the other is pricing type.
The pricing sources are generally the order.   But if you want you can change it to other values mentioned in the drop down,
but this values have no effect if the pricing type is B.
Any other value other than B in the pricing type will take the reference document price mentioned in the pricing source field.
but for the pricing type B. The new price is determined in the billing order.
Hope this will help.
Regards,
Naveen.

ERROR ON PRICING DATE

in the sales order pricing date is been taken as the old date.
for example sales order creation date is 28/08/08, and the delivery date is 29/08/08, pricing date has to take same as the delivery date according to the sales document controls, but it is giving the price date as the 25/08/08.

Hi
set the proposed pricing date A in sales document type controls. system should give the pricing date based on delivery date.
There might be some chances, if you are creating sales order with reference to contract, system copies pricing date from contract ( proposed pricing date C)
When you create sales order with reference to quotation, system copies the pricing date from quotation.
Regards,
Chandra
Edited by: chandra sekhar S on Aug 28, 2008 11:00 AM

Pricing Model

Back in mid-February some blog posts said that a pricing
model would be out in a few weeks. Has a candidate pricing model
been posted? If so, where can I find it? If not, when will it be
made available?

Thank you for your patience! Please refer to this blog post
for details. We would very much appreciate your feedback on our
proposed pricing models.
http://blogs.adobe.com/collabmethods/2009/03/chomping_at_the_bit_afcs_prici_1.html

Pricing Profile - Generic Article

Dear Experts,
Whenever i create generic article system by default proposes pricing profile as '2' under basic data screen, however i do not wish to maintain same price for all variants. How can we influence this process that system do not propose '2' as pricing profile, thus the generic article price will not get inherited to all variants.
Look forward to have expert advise.

Hi,
This is controlled by the standard table/field entry settings and it's genearlly not advisable to change the std settings..Also you can always change the pricing profile to 1 or keep it as "Empty" by making this field(MARA-SPROF) a required entry.
However,if you really want,you can give it a try using the following steps.
1.Go to Transaction OMSR(Assign Field to Field selection Groups)
2.Scroll down to find MARA-SPROF - Pricing Profile for variants (Selection Group - 160)
3.Click on Details button
4.Untick the "Propose Field content" under Field attributes
Hope it helps.
Best Regards,
Aram K.

Cannot save document

I am a heavy user of numbers and have repeatedly hit the wall with some of my more advanced spreadsheets. Recently one of my templates would not save as a workable template any longer. I've stopped using it as a template which has worked for a couple months but now when I've tried to make a few more improvements and it is not allowing me to save. This one spreadsheet is the most integral part of every project in my company. I can't emphasize how important it is for me to get this resolved.
Here is the current issue:
In the sheet: "Pricing Backpage" in the table "Proposal Pricing Table" I have tried to enter a new category and it allows me to enter it but as soon as I do the spreadsheet will no longer save. I have a table with 215 rows and "Z" columns and its broken into 5 categories (in the technical table-feature sense of the word). The header row and columns are frozen. I can't think of anything else that would effect it. Almost ever cell in the table has a formula in it. The document size is 6MB.
Error Message:
The document "name" could not be saved.
Another issue I am having is that on occasion numbers will not allow me to copy and paste data. Restarting the application seems to work when that happens but still annoying.
The issue happens on multiple computers within my network. The file is saved on a Xserve Server.
Anyone - PLEASE HELP!
The issue has been reported to apple as a bug.
Thank you.

Jeremy,
We all want our spreadsheets to perform. We are all users, just like you, except perhaps for the fact that you seem to have found a practical limit of Numbers capability to handle large files. We've told Apple via Feedback that the program is slow. I wonder if FileMaker Pro would be a better business solution in your case.
Jerry

PPT on SD process flow

Hi guys am in need of help from u
am not so clear about the SD process flow
can anyone pls send me a PPT on SD process flow
to my email id:- (<REMOVED BY MODERATOR>).
thanking u in advance..
Regards
Jino.

Sales Organization :
Responsible for:
 Distribution of goods and services
 Negotiating Sales Conditions
 Product Liability and rights of recourse
 A sales organization is uniquely assigned to a company code
 Master datas are separately maintained for a sales organization
 All items in the Sales and Distribution document belong to a sales organization
Distribution Channel:
Means through which products and services reach the customer
A distribution channel:
 Defines responsibilities
 Helps in achieve flexible pricing
 Differentiate Sales statistics
Division:
 A division is used to group products and services.
 A division represents a product line.
Sales Area:
A Sales area is a combination of
 Sales organization
 Distribution Channel
 Division
Each Sales and distribution document is assigned exactly to one sales area.
A sales area can belong to only one company code.
 Sales Organization
 Distribution Channel
 Division
 Sales Area
Plant and Storage Location:
 A Plant is a location where stock is maintained
 Plant and storage location are used by all logistic area of R/3 System
 A Plant is uniquely assigned to a company code
Shipping point:
 Shipping point is the highest level of organizational unit in shipping
 Each outbound delivery is processed by one shipping point
 Shipping points are assigned to a plant
 More than one shipping point can be assigned to a plant
Sales and Distribution is SAP begins with establishing customer relationship and ends with invoicing for the delivery of goods or service provided to the customer .
A Standard sales transaction has the following flow:
Inquiry
Quotation
Order
Delivery
Billing
The customer order management cycle begins with pre-sales activities.
A standard order in SAP contains:
 Customer and material info
 Pricing conditions
 Delivery dates and quantities
 Shipping info
 Billing Info
Inventory sourcing in SAP is taken care by
 Availability check
Shipping in SAP supports
 Outbound delivery creation
 Picking
 Packing
 Post Goods Issue
Billing in SAP supports
 Creating invoices for products and services
 Creating credit and debit memo
 Cancel previously posted billing documents
 Automatically transferring billing documents to accounting
When a billing document is created for a sales order we
 Credit the sales revenue account
 Debit the customer receivables account
Sales Document
A sales document is grouped into three structures
 Header
 Item
 Schedule Line
Outbound delivery
A delivery document is grouped into two structures
 Header
 Item
Several orders can be grouped into same outbound delivery if they have same
 Shipping point
 Delivery date
 Ship-to- address
Picking
 A transfer order is created for an outbound delivery
 A transfer order is created for a warehouse number
Post Goods Issue
When PGI is done the system
 Updates the quantity in inventory management and delivery requirements in materials planning
 Generates additional documents for accounting
 Adds the delivery to the billing due list
 Updates status in sales documents
Billing
We can group deliveries into single billing document if the deliveries have same
 Billing date
 Payer
 Destination Country
The effects of billing are
 Debit on the customer receivables account and credit on sales revenue account is created
 Sales information system
 Sales statistics is updated
Master data in SAP
SAP SD has got the following main masters:
 Customer master
 Material master
 Condition master
 Output master
 Customer material information master
Customer master
General Data Sales Area Data Company Code data
Tab pages Tab pages Tab pages
Address Order Accounting
Control data Shipping Payment
Payment terms Billing Correspondence
Marketing Partner functions Insurance
Unloading points
Export data
Contact persons
The chart above shows detail on three main areas of customer master and the tab pages found under each area.
Material Master is maintained in different views and important views of sales and distribution are
 Basic data 1
 Sales Org 1
 Sales Org 2
 Sales : Gen/Plant
 Foreign Trade
 Sales text
Sales document in Sales and distribution mainly controls:
 Number range
 Item No increment
 Reference mandatory
 Item division
 Read info record
 Document pricing procedure
 Incomplete messages
 Alternative sales documents
 Delivery block
 Billing block
 Immediate delivery
 Delivery type
 Billing type
 Proposed delivery date
 Lead time for delivery
 Proposed pricing date
Plant determination in Sales and distribution:
To determine the plant in an order the system checks the master in the following order:
a) Customer material info. record of the sold-to party
b) Customer master record of the ship-to-party
c) Material master record of the material
Shipping point determination
The following rule is used in determining shipping point in a sales order :
Plant + Shipping condition (Sold-to-Party) + Loading group Shipping point
 Maintained in Material master Gen: Plant data
Route determination
Route determined using the following rule in Sales and Distribution (SAP)
Departure Zone of Shipping Point
+
Shipping condition (Sold-to-Party)
+
Transportation Group (Material master)
+
Transportation Zone (Ship-to-Party)
Route
Delivery scheduling:
As name denotes delivery scheduling is scheduling delivery for an order and it carries the following important dates:
 Material availability date
 Transportation planning date
 Loading date
 Goods Issue date
 Delivery date
Availability Check in SAP:
 Availability check is carried out at item level for a plant
 Availability check is done on the material availability date
 If material availability date is in the past the forward scheduling is done, if not backward scheduling is done.
Item category determination in the order:
Item category denotes the category to which the item belongs and the following rule is used for determination of item category. Item category controls the way in which item behaves in a sales document.
Sales document type
+
Item category group (Material master)
+
Item usage
+
Item category of higher level item
Item category of the item
Item category in a sales document mainly controls the following
 Relevance for billing of an item
 Billing block
 Pricing relevance
 Business data relevance item
 Schedule line allowed
 Item relevant for delivery
 Returns
 Determine cost
 Credit active
 Incompletion procedure
 Partner determination procedure
 Structure scope (relevant for bill of material explosion)
 Value contract material
 Contract release control
Schedule line category:
Every item which has a delivery will have a schedule line and the schedule line category is determined with the following rule:
Item category + MRP type(Material Master) Schedule line category
Schedule line category mainly controls:
 Delivery Block
 Movement type
 Item relevant for delivery
 Req/Assembly
 Availability
 Product Allocation
Copy Control:
Copy control is normally set for
 Header
 Item
 Schedule line levels
To control copying procedure we have
 Data transfer routines
 Copying requirements
 Switches
Pricing Procedure determination:
Pricing is an important component in SAP-SD. Once an order is entered taking into consideration some major factors, the pricing procedure for the particular order is determined.
The major factors taken into consideration for pricing procedure determination is:
Sales area
+
Customer Pricing procedure(Customer Master Sales area data)
+
Document Pricing Procedure(Sales Document Type)
Pricing Procedure
What are the components of pricing procedure?
How is that a person should work on Pricing Procedure?
To start with first
Define a Condition table:
What is a condition table?
A table where the key fields are data combinations for which messages are triggered (and offered for processing).
For each data combination, there is a condition record in the table. The data part contains the actual message.
As mentioned above a condition table is a table which carries key fields for picking up the prices.
Define Access Sequences
The access sequence is a search strategy which the SAP System uses to search for condition records valid for a condition type.
For example, you can define for a price that the SAP System first searches for a customer-specific price and then for a price list price.
Recommendation
 If you define your own access sequences, the key should start with the letter Z since SAP reserves this letter for the standard system.
 Do not change access sequences contained in the standard SAP R/3 System.
Actions
1. Check to what extent you can use the access sequences contained in the standard SAP R/3 System.
2. Create new access sequences by copying a similar access sequence and changing it according to your needs. Specify an alphanumeric key which may have up to 4 digits and a textual description.
3. Maintain the accesses for the access sequence by specifying the condition tables in the desired sequence. With the sequence, you define the priority of the accesses. You can display combinations of key fields using possible entries.
4. Generating the accesses is no longer necessary as of 3.0, as this is carried out automatically. You can generate the accesses manually, if required, by choosing "Utilities".
Example
In pricing, you use a customer-material discount. The condition records you create are based on customer data from the document header and material data from each document item. The discount is only valid for 2% of your customers, however. Normally, this would mean that the system would needlessly search through every available item for 98% of your customers. In this case, pre step would improve system performance.
Define Condition Type
A characteristic of a condition. For example, in pricing, different condition types are used to distinguish between a discount that refers to a net price and a discount that refers to a gross price.
Price elements are represented in the SAP system by condition types. Price elements can be, for example, prices, surcharges, discounts, taxes or, freight, and are stored in the system in condition records.
You can, for example, define whether a discount is calculated as a percentage or a fixed amount using the condition type.
You specify an access sequence in every condition type. Thus, you define which fields the SAP system checks when searching for a valid condition record.
Note
 The pricing procedure groups all condition types together which the SAP system is to automatically take into account during pricing for a business transaction (see the section "Define and assign pricing procedures").
Remember that you can only specify manually in a document those condition types which are contained in the pricing procedure.
 You can change the outcome of pricing in the sales document manually. You can limit options for changing a condition type in this IMG step.
Recommendation
 If you define your own condition types, the key should start with the letter Z since SAP reserves these letters for that purpose in the standard system.
 Do not change the condition types which are contained in the standard SAP R/3 System.
Actions
1. Check to what extent you can use the condition types contained in the standard SAP R/3 System.
2. Create new condition types by copying a similar conditions type and changing it according to your requirements. One reason for creating a new condition type is you may require a calculation rule for a discount which is not available in the standard system.
Specify an alphanumeric key which can have up to 4 digits, and a textual description.
Specify an access sequence for the condition types. You do not need to specify an access sequence for header conditions.
3. Maintain the detail screen of the condition type.
You can also assign a reference condition type if the condition types you are working with are similar. Then you will only have to maintain condition records for the reference condition type.
In addition, you can define the upper and lower limits for the value of a condition at condition type level. This way, you limit the amounts or the scale values in the corresponding condition records.
Define Pricing Procedures
The pricing procedure defines the conditions permitted for a document and the sequence in which the system takes these conditions into account during pricing.
A standard pricing procedure is defined in the standard SAP system. It contains conditions most commonly used. These include material prices, discounts, and surcharges, such as freight, or tax.
SAP Recommendation
 Define your own pricing procedures which contain only those condition types which you use. Otherwise, the system makes un neccessary accesses to conditions.
 Do not change the pricing procedures contained in the standard SAP R/3 System.
Actions
1. Create new pricing procedures by copying a similar pricing procedure.
o Specify a key with up to 6 characters and a description.
o For a procedure, specify the condition types in the sequence of their usage.
Maintain the lines of the pricing procedure
2. Afterwards define the customer determination procedures for determining the procedure.
3. Define the document pricing procedures for determining the procedure.
4. Assign the procedure to the sales document types and billing types.
5. To determine the procedure, define the allowed combinations of:
o Sales area
o Customer pricing procedure
o Document pricing procedure
o Pricing procedure
Shipping:
The basis for shipping is delivery.
Delivery document controls the following in deliveries
 Number range
 Item no increment
 Storage location rule
 Route determination
 Text determination
 Delivery split
 Gen. packing material / item
 Order required
Delivery item category controls:
 Check min delivery
 Availability check
 Relevant for picking
 Storage location required
 Determine storage location
 Automatic batch determination
 Text determination procedure
Billing:
Billing is the last phase in the SD process .Billing is the phase where the major integration of SD and FI Module happens.
Billing document has got the following structure:
 Header
 Item
Billing documents mainly control:
 No. range
 Posting block (Controls posting to accounting)
 Relevant for rebate
 Account determination procedure
 Account determination recon account
 Account determination pay.cards
 Output determination procedure
Account Determination in SAP
Account determination in SAP-SD happens with the following rule
Sales Organization
Chart of Accounts
Account assignment group Customer
Account assignment group-Material
Account Key
G/L account on which the postings has to happen.
CHeers!!!

Types Of Reporting.

Hi Experts,
This is Guru. New bie to ABAP. One of my friend said as a fresher in ABAP programming i must first focus on Reporting stuffs. Can anyone say what are the types of reporting in ABAP programming ?
Thanks in advance,
Guru.

Hi,
1. Developed a report to display all purchase order whose goods receipt have been made but not invoiced.
2. Developed a Division wise Sales Analysis report.
3. Developed a report to display unconfirmed Purchase Orders.
4. Created a report to display a list of Sales orders, Ordered by customer who doesnt have credit limit more
5. Developed a Stock Tracking report, which shows stock of various materials in various Storage locations.
6. Developed a report for customer out standings.
7. Developed a report for monthly dispatches.
8. Developed a report for displaying the vendor balances.
9. Created Vendor Performance report, which lists the vendor name, Materials Supplied, planned, Actual delivery items, Payment terms and Prices.
10. Created an Interactive Reports on blocked invoices.
11. Report to display all material rates by using Material number, Sales Organization, and Distribution Channel and condition type.
12. Developed a report which will list out all the purchase order details and the secondary list contains all the information about the supplier.
13. Developed an interactive report which displays the list of purchase requisitions in the basic list according to the users selection screen and which in turn allows the user to modify the purchase requisition in the secondary list.
14. Created an interactive report to list the purchase orders details for a vendor.
15. Created Report to Display the Details of Sales Quantity in the given date. Outputs Material No, Material Disc, Plant, current Month Sales, Previous Month Sales, Last Year same Month and Date (Quantity). Data was extracted from VBRK, VBRP.
16. Developed ABAP List View report program for Material Values to display list of all materials under a plant. Selection screen contains plant, material type.
17. Developed a Report To print report of all the items whose quantity is bellow re-order level.
18. Created a report to display sales order and dispatch details.
19. Developed a report to display the list of Inventory Differences by adding two new fields.
20. Developed AP aging report sort by Invoice date and Receipt date over dues Analysis.
21. Developed a report for mass selecting and printing Material Master Changed History.
22. Developed an interactive report to display sales orders for particular customer, items for particular order.
23. Developed a report that displays list of purchase requisition with details like MRP controller, release date and unit of measure.
24. Developed a report to display unused material numbers.
25. Developed vendor master analysis report, which lists the material including material number and storage location.
26. Developed an Interactive list for purchase requisitions at a given plant.
27. Developed a report to display list of purchase order details.
28. Developed a report, which lists delivery number, delivery quantity, customer number, material number and material description for a given shipping point.
29. Developed a report to display all sub-totals and grand totals for a particular vendor.
30. Developed a report that shows a list of purchase requisition and purchase orders for a selected vendor, by material group listing by material.
31. Developed a report to get list of purchase orders created during a particular month.
32. Developed the outstanding purchase order report based on acknowledgement date.
33. Developed material description report to display list of materials, language key, material description based on material type and plant.
34. Developed a report that lists purchase order entered into SAP, limit the selection to purchase order created during a specific period.
35. Created report, which will print the material stock, which will find out material group for material and find out the material description for each material.
36. Created an interactive report, which lists the customer details in the basic list. If the customer number is selected, the corresponding sales orders and item details will be displayed in the secondary lists. Drill down to transaction MM03 is also provided.
37. Created utility report to copy batch characteristics from one batch to already existing another batch.
38. Created an ALV report to provide detailed information regarding all Materials by taking plant, material and material type as input.
39. Generated a warranty evaluation report.
40. Generated a report, which list out all the customers who have the warranty period for their product.
41. Developed a report to list warranty expired customers.
42. Created Vendor Performance Report that lists Vendor Name, Materials Supplied, Planned & Actual Delivery Times, Payments Terms and Prices.
43. Reports created to list out the sales documents created everyday, for credit approvals.
44. A report to monitor transportation details for delivery schedule.
45. Block for posting and mark for deletion all inactive vendors in all company codes and purchasing organization levels for period of 2 years.
46. Report to generate Material valuation.
47. Generated an interactive report, which will list out all the purchase order details and all the information about suppliers.
48. Generated a report listing stock position for a chosen material for chosen storage location in a given plant.
49. Developed a report on goods issue, which generate the information about how much stock issued to the customer according to the sales order for a particular period.
50. Delivery due list: This report program generates list with details of quantity available, quantity planned, quantity delivered and quantity still to be delivered for sales orders and stock transport orders based on shipping point.
51. Involved as a team member in generating interactive report program to give details on sales orders, vendors, customers for a particular material.
52. Created a report to display item, material, quantity, purchase order number, vendor and goods receipt date based on goods receipt number.
53. Developed an Interactive report that list out all the materials for a given plant. Secondary List contains Vendor who supplies the chosen material
54. Monthly warehouse report.
55. Report on customer payment, items cleared and discounts.
56. Material availability report.
57. Report on Dollar Value of Material, quantity on hand, average monthly quantity used.
 Line item details for financial journal entries.
 Financial gross sales margin.
 Ending inventory balances.
58. Shippable details report.
59. Report for all blocked invoices.
60. Purchase order wise GR document and invoice receipt details line item wise.
61. Open sales order report. VA05
 Created Classical and Interactive report to display all the Purchase Orders for the Purchasing Organization, Purchase groups and display the total, and individual values of all the Purchase Orders.
 Generated an Interactive report that displays vendor wise Purchase Order details.
62. Created an interactive report to display Sales Order data. In the basic list it displays the header data like SO number, created by, customer number etc., At the first level, SO screen and Customer master data is displayed by selecting appropriate item in the basic list. At the second level, report displays selected line item for the Sales order
63. Created a Report to display the pricing conditions in a sales order with standard details.
64. Created an report for purchase variance.
65. Created report to compute and display the list of outstanding orders by ship-to-party or sold-to-party.
66. A report on Sales Register: It lists the details like Invoice No, Date, Customer no, Sales value, Sales tax etc.
67. A Report to display the commissions for the sales department sorted by sales representative.
68. A Report to get the status of a particular delivery items with respect to a customer from specific shipping points over a given period.
69. A Report to show the list of Vendors with Blocked Payments.
70. An Interactive list showing all the Sales Areas, Customers of that sales area, Materials Ordered by them, information regarding materials and their net price.
71. An Interactive List displaying SO, Line Items which need to be delivered by certain Date.
72. An ALV Report for PO history for a particular period. Gives PO details based on specified company code, plant, Invoice receipt date and Vendor number.
73. An Interactive Report showing Vendor Information and his corresponding Bank Details.
74. Developed a report to compare the calculated average selling price for an item to a customer versus the current standard price for that item to that customer.
75. Developed a report to display Outstanding Quantity for Material.
76. Developed a report to drill down the displayed list, displaying the subsequent list of the line items for the selected purchase order.
77. Developed a report to display line item details information for financial journal entries.
78. Developed a report to List the Purchase Orders must allow the user to select the types of Purchase Orders.
79. Developed a report to displays all the Sales Orders processed to one particular customer for a given range of time.
80. Material Master Detail report for a given plant and material type, displaying material and plant depending on material.
81. Sales Journal - which displays sales details for a particular plant in a particular period of time.
82. developed a report to display the stock details.
83. Created a report for list of purchasing group for given plants. this report displays the list of plants, purchasing group, description of purchasing group according to the plant.
84. Created Vendor performance Report that lists vendor related details.
85. Developed a report to display Vendor master information and vendor bank details.
86. Developed a report to display all purchase orders whose goods receipt have been made but not invoiced.
87. Developed Division wise Sales Analysis report.
88. Developed a report to display unconfirmed Purchase Orders.
89. Developed a report to display list of Materials.
90. Created a report to display a list of Sales orders, Ordered by customer who doesnt have credit limit more.
91. Developed a Stock Tracking report, which shows stock of various materials in various Storage locations.
92. Developed a report for customer out standings.
93. Developed a report for monthly dispatches.
94. Developed a report for displaying the vendor balances.
95. Created Vendor Performance report, which lists the vendor name, Materials Supplied, planned, Actual delivery items, Payment terms and Prices.
96. Created report, which will print the material stock, which will find out material group for material and find out the material description for each material.
97. Created an interactive report, which lists the customer details in the basic list. If the customer number is selected, the corresponding sales orders and item details will be displayed in the secondary lists. Drill down to transaction MM03 is also provided.
98. Created utility report to copy batch characteristics from one batch to already existing another batch.
99. Created a Report to display the pricing conditions in a sales order with standard details.
100. Created an report for purchase variance.
100. Created report to compute and display the list of outstanding orders by ship-to- party or sold-to-party.
101. Created Classical and Interactive report to display all the Purchase Orders for the Purchasing Organization, Purchase groups and display the total, and individual values of all the Purchase Orders.
102. Generated an Interactive report that displays vendor wise Purchase Order details.
103. Created an interactive report to display Sales Order data. In the basic list it displays the header data like SO number, created by, customer number etc., At the first level, SO screen and Customer master data is displayed by selecting appropriate item in the basic list. At the second level, report displays selected line item for the Sales order.
104. Contract Compliance Report : This report looks at the actual customer purchases (QTY) by period vs. targeted quantities.
105. The report created will list all the contracts quantity vs. shipped quantity in the period specified for a given customer or material or sales organization or contract number along with details such as material numbers, contract start date, contract end date, etc.
106. Contract Expiration Report : Contracts need to be monitored and quotations sent out for renewal as they approach their expiry date. A report is required to show the contracts expiring.
107. This report will list all the contracts expiring in the period specified for a given customer or material or sales organization or contract number along with details such as equipment numbers, material numbers, contract start date, contract end date, etc.
108. Audit Trial For Pricing Conditions : This report tracks the manual changes made to the Pricing Conditions.
109. Back Order Report by Customer, Material or Product Line : The definition of a back order is an item, which cannot be shipped on the date necessary to meet the customers requested delivery date.
110. This caters the back order by customer, material or product line which is to be used by DS.
111. Match Confirmation Report : This program reports the discrepancies in characteristics between the materials and the machine for a given production version.
112. This report will compare characteristics of the material to the machine characteristics and lists any discrepancies between the characteristics. This will replace the current legacy report (Mismatch report). The program will provide information that will prevent the Company from producing products on the wrong modules that can lead to significant waste, rework and potential product recalls.
113. Invoice Out of Tolerance : This will report against the customer invoices that are below a predefined margin rate. This will be the primary indicator of pricing problem.
114. Here Customer invoices below a specified gross margin value are reported.
115. Pricing Override Report : When there is a legitimate need to override system proposed pricing, it should be documented for use in downstream decision making.
116. On demand report detailing overrides to the proposed system pricing along with override reason. This report will allow for analysis and possible adjustment of pricing conditions.
118. Classical & interactive reporting.
 Production report, Stock Balancing report, Delivery Schedule,
 Material dispatch Updation, Material Freight Updation,
 Material wise serial number for production & dispatch, Valued Stock Report,
 Machine Dispatch of RG1 (Excise Returns)..
 Warranty Reports (Item wise, Dealer wise, Machine wise).
 Warranty expenses of machines with in the warranty period and beyond warranty
 Period.
 List of failures value wise and frequency wise.
119. Delivery Performance Report - The delivery performance report is used to compare the customer delivery schedules with the deliveries created in SAP to determine whether they are early, on-time, or late. This measurement is done by comparing the customer request date against the goods issue date from the delivery.
120. Batch Level Inventory Report - This is a quick method to review all inventory that is in the entire plant or being more selective, in a particular storage location.
121. Sales by Subcontractor - This report presents sales numbers by subcontractor for a given plant or all plants.
122.Generated reports for Customer info and Waiting list.
1. Created an interactive report that displays sales order information like sales order number, order reason, sold to party and delivery status. The detailed list gives item data and delivery status.
2. Maintenance of existing reports. Made changes as per their requirements. Developed new reports related to SD and MM.
3. Another report that takes date and customer ranges as input and gives the invoice details. If the user select any of the invoice, it checks whether it is credit or debit based on that further details of the particular invoice would be displayed as an interactive report.
4. Interactive report which displays all the purchase orders for one particular customer, the items order for that particular order, quantity ordered, goods issue date and contact information about that customer.
5. Created report lists for the gross sales, credit returns, gross weight for the customer for the current year and comparing the same with that of the previous year for the same period. The data is selected from KNVV, BKPF, BSEG and MARA.
6. Report that lists the shipping point, loading point, transport partner name and the shipping date given the sales order number as user input.
7. Created an interactive list displaying sales orders and line items, which needed to be delivered by a certain date. Selection criteria were used to enter the specified delivery dates.
8. Developed a report which displays material wise Suppliers for a given plant.
9. Developed a report that displays Sales Analysis By Customer.
10. Developed a report that tracking down the invoices.
11. Developed Monthly Extract Report for Indirect Sales.
12. Developed a report program for displaying General Material data according to the selection of the material number and batch number by the user provided on the selection screen.
13. Report that displays all the late shipments in a particular period of time.
14. Developed vendor performance report that lists vendor name, material supplied, planned and actual delivery times, payment terms and prices.
15. Developed a report that displays a list of Purchase Requisitions.
16. Developed a report in material master that outputs valuated stock, grouped by material type and plant . Data was extracted from MARA, MARC, MARD, MAKT, EKKO, EKPO, MKPF, MSEG and T001W.
17.

Combination of bills in retro billing...

Hello,
can i combinate bills in retro billing (t.code vfrb)????
is there anybody to answer?

Hi
Refer the link given below for PDF
[http://help.sap.com/printdocu/core/Print46c/en/data/pdf/SDBILRB/SDBILRB.pdf]
Retroactive billing is a special billing function often used in scheduling agreement processing.
Features
With the retroactive billing function, you can:
Call up a list of documents affected by price changes
Trigger the system to create the necessary retroactive billing documents directly from the list
Create credit or debit memos directly
Procedure
In Billing choose Billing document Retro-billing.
Enter a payer, a sales organization, to and from dates, and pricing type B or C .
The system automatically proposes pricing type C . Besides these required entries, you can also enter a currency, sold-to party, or material to narrow your search.
Choose Enter.
The system creates a list, displaying documents and subtotals for each combination of currency, sold-to party and material.
If you are working with this function for the first time you must first set the billing types for credit and debit memos and the order reasons for these documents.
Choose Settings Change, enter your data, and choose Save. Although the system will propose these settings as default in future documents, you can change them at any time.
Select the document or documents that you want to bill retroactively and choose Retro-billing.
Only items with open quantities can be selected. If you cannot select an item, this means that it has already been processed.
To simulate the retroactive billing function, choose Simulate
Review any errors in a log
Simulate the retroactive billing process for any document
Regards

How ro create Retro Billing

Hi all,
Can anybody suggest me the process for retro billing. I knw the Tcode (VFRB) but how to do this process in SAP?
Regards
Kishan

Hi,
Retroactive billing is a special billing function often used in scheduling agreement processing.
Features
With the retroactive billing function, you can:
Call up a list of documents affected by price changes
Trigger the system to create the necessary retroactive billing documents directly from the list
Create credit or debit memos directly
Procedure
In Billing choose Billing document Retro-billing.
Enter a payer, a sales organization, to and from dates, and pricing type B or C .
The system automatically proposes pricing type C . Besides these required entries, you can also enter a currency, sold-to party, or material to narrow your search.
Choose Enter.
The system creates a list, displaying documents and subtotals for each combination of currency, sold-to party and material.
If you are working with this function for the first time you must first set the billing types for credit and debit memos and the order reasons for these documents.
Choose Settings Change, enter your data, and choose Save. Although the system will propose these settings as default in future documents, you can change them at any time.
Select the document or documents that you want to bill retroactively and choose Retro-billing.
Only items with open quantities can be selected. If you cannot select an item, this means that it has already been processed.
To simulate the retroactive billing function, choose Simulate
Review any errors in a log
Simulate the retroactive billing process for any document
Hope it helps. Please reward if useful.
Thanks & Regards
Sadhu Kishore

All about retro billing

hi,
sap gurus,
i am trying to do this and strucked i the middle
plz help me out on this
i am trying to do the scenario of retro billing and I strucked in the middle.
I created a invoice invoice for the date jan 5th with the netvalue of 100/- and riased a credit memo for the amount of 30/- on 15th Jan.
Then I am genrating the retrobilling list, but I am able to see only invoice document in the list. why the credit memo is not appearing in the list.
Order date:- Jan 5th
Invoice date:- Jan 5h (10 pices *10=100)
credit memo:- jan15h. ( 3 pices*10=100)
price change date:- 01.03.2008
my email id is:
[email protected]
regards,
balaji.t
09990019711

Hi
Refer link below
Retroactive Billing
Retroactive billing is a special billing function often used in scheduling agreement processing.
Features
With the retroactive billing function, you can:
Call up a list of documents affected by price changes
Trigger the system to create the necessary retroactive billing documents directly from the list
Create credit or debit memos directly
Procedure
In Billing choose Billing document Retro-billing.
Enter a payer, a sales organization, to and from dates, and pricing type B or C .
The system automatically proposes pricing type C . Besides these required entries, you can also enter a currency, sold-to party, or material to narrow your search.
Choose Enter.
The system creates a list, displaying documents and subtotals for each combination of currency, sold-to party and material.
If you are working with this function for the first time you must first set the billing types for credit and debit memos and the order reasons for these documents.
Choose Settings Change, enter your data, and choose Save. Although the system will propose these settings as default in future documents, you can change them at any time.
Select the document or documents that you want to bill retroactively and choose Retro-billing.
Only items with open quantities can be selected. If you cannot select an item, this means that it has already been processed.
To simulate the retroactive billing function, choose Simulate
Review any errors in a log
Simulate the retroactive billing process for any document
Regards

Multiple Condition Exclusion

The new price procedure I'm configuring has price conditions that need multiple condition exclusion logic.
Example, say my conditions are:
1) ZPR1 - price 1
2) ZPR2 - price 2
3) ZDIS1 - discount 1 %
4) ZDIS2 - discount 2 value
5) ZDIS3 - discount 2 %
Logic are:
A) If ZPR1 is used ZDIS2 and ZDIS3 are excluded.
B) If ZPR2 is used ZDIS1 is excluded.
C) If ZDIS2 is used, ZDIS3 is excluded.
D) If ZDIS3 is used, ZDIS2 is excluded.
A is easy. Just group ZPR1 and ZDIS1 together and ZPR2, ZDIS2 and ZDIS3 together, then make 1 exclusive of 2.
B is easy also.
What about C and D? Can you just put ZDIS2 in another group and ZDIS3 in a different group and create an exclusion rule against each other?
Thanks.

In my opinion you can follow the following link to achieve your requirement:
- [Proposed Pricing Procedure|https://docs.google.com/leaf?id=0B-5wCmYJ-6dlNDIxNTg0YzUtMTE0Yy00M2VmLTliOWItMTNkMWE4YTZkMzY4&hl=en] for the requirement
If you have any other thoughts then you can share you proposed pricing procedure.
I hope this can assist you.
Thanks & Regards
JP

Proposed pricing

Similar Messages

Maybe you are looking for