Difference between downpayment and Milestone billing

Dear Guru's
can anyone tell me what is the difference between downpayment and milestone billing. And also tell me anyother things are there in this process.
regards,
Reshmi

hi
Milestone billing is typically used for billing projects, such as plant engineering and construction projects. Such projects often include a series of milestones that mark the completion of different stages of the work. In the SAP R/3 System, milestones are defined in a network along with planned and actual dates for the completion of work. The milestones are also assigned to the billing dates in the billing plan. Each milestone-related billing date is blocked for processing until the Project System confirms that the milestone is completed.
Delivery-relevant order items for which a milestone billing plan applies are billed on the basis of the requested delivery quantity and not on the total of the confirmed quantities.
<a href="http://help.sap.com/saphelp_470/helpdata/en/59/ac922bcb0411d2acbe0000e8a5bd28/frameset.htm">http://help.sap.com/saphelp_470/helpdata/en/59/ac922bcb0411d2acbe0000e8a5bd28/frameset.htm</a>

Similar Messages

Difference between Downpayment and normal invoice in updating BSEG table

Hi,
I created 2 different documents, 1 invoice via FB60 and 1 downpayment request between F-47.
After which i perform a payment run via F110 on both documents and i realised that the bank account id for the document created via F-47 is not updated in the field HBKID for the BSEG table. However, HBKID is updated for the invoice created via FB60.
I would like to if this is correct or if there is any config i need to perform for the HBKID field to be updated for document created via F-47.
Thanks in advance.

Hi,
Please, look at the following note 524942. It should solve your problem...
Regards,
Eli

Difference between invoice and billing document

Hi ,
As an ABAPer , I am finding it very difficult to find the difference between the billing and invoice.
If both are different, then how these documents are configured.
thanks
Devi Reddy

Hi,
No difference between invoice and billing document.
But If we want to inform the payable to the customer we use the terminalogy invoice.
Example Credit meomo, debit memo. etc ...
As there is no difference , both have the same document types.
thanks
Kuntla

Credit Management: Difference Between Static and Dynamic Credit Check

Hi,
Could anyone tell the difference Between Static and Dynamic Credit Check?
According to website: http://www.sap-basis-abap.com/sd/difference-between-static-and-dynamic-credit-check.htm ... this is the answer:
====================
Simple Credit Check : Tr.Code - FD32
It Considers the Doc.Value + Open Items.
Doc.Value : Sales Order Has been saved but not delivered
Open Item : Sales Order has been saved , Delivered, Billed & Transfered to FI, but not received the payment from the customer.
Static Credit Check it checks all these doc value & check with the credit limit
1) Open Doc.Value / Sales Order Value : Which is save but not delievered
2) Open Delivery Doc.Value : Which is delivered but not billed
3) Open Billing Doc.Value : Which is billed but not posted to FI
4) Open Item : Which is transfered to FI but not received from the customer.
Dynamic Credit Check         1) Open Doc
                                            2) Open Delivery
                                            3) Open Billing
                                            4) Open Items
                                            5) Horizon Period = Eg.3Months
Here the System will not consider the above 1, 2, 3 & 4 values for the lost 3 months.
====================
Question 1: Could you further explain the above information, if there is any?
Question 2:: What is the Tcode to customize settings of:
a) Simple Credit Check (isn't this same with b) below?)
b) Static Credit Check
c) Dynamic Credit Check

Hi Tanish,
Diff between Static and Dynamic Filters.
Example One at report Level.
Create a variable for a Infoobject say ,Material .
1)In the Query Designer and if u restrict it to some 10 materials at query level, the report will display for only those 10 materials only.This is Static Filter.UR AHrdcoding it to those materials.You cant change them at Query Run time.i.e not changeable by user.
2)If u give the variable as input ,and when u run the query ,u can can choose the material,may 10 may be 1 or may 20 .It is dynamic.Changeable by user at run time
Example Two at DTP and Start Routine Level,say Document Type.
1)If u give filters in Start routine it is Static as u cannot change it in Production,not changeable by user.
2)f u give filters in DTP it is Dyanamic as u can change it in Production.U can give any doc type,Changeable by user at run time.
Hope it is Understood.
Rgds
SVU

What's the Difference Between OLAP and OLTP?

HI,
What's the difference between OLAP and OLTP ? and which one is Best?
-Arun.M.D

Hi,
The big difference when designing for OLAP versus OLTP is rooted in the basics of how the tables are going to be used. I'll discuss OLTP versus OLAP in context to the design of dimensional data warehouses. However, keep in mind there are more architectural components that make up a mature, best practices data warehouse than just the dimensional data warehouse.
Corporate Information Factory, 2nd Edition by W. H. Inmon, Claudia Imhoff, Ryan Sousa
Building the Data Warehouse, 2nd Edition by W. H. Inmon
With OLTP, the tables are designed to facilitate fast inserting, updating and deleting rows of information with each logical unit of work. The database design is highly normalized. Usually and at least to 3NF. Each logical unit of work in an online application will have a relatively small scope with regard to the number of tables that are referenced and/or updated. Also the online application itself handles the majority of the work for joining data to facilitate the screen functions. This means the user doesn't have to worry about traversing across large data relationship paths. A heavy dose of lookup/reference tables and much focus on referential integrity between foreign keys. The physical design of the database needs to take into considerations the need for inserting rows when deciding on physical space settings. A good book for getting a solid base understanding of modeling for OLTP is The Data Modeling Handbook: A Best-Practice Approach to Building Quality Data Models by Michael C. Reingruber, William W. Gregory.
Example: Let's say we have a purchase oder management system. We need to be able to take orders for our customers, and we need to be able to sell many items on each order. We need to capture the store that sold the item, the customer that bought the item (and where we need to ship things and where to bill) and we need to make sure that we pull from the valid store_items to get the correct item number, description and price. Our OLTP data model will contain a CUSTOMER_MASTER, A CUSTOMER_ADDRESS_MASTER, A STORE_MASTER, AN ITEM_MASTER, AN ITEM_PRICE_MASTER, A PURCHASE_ORDER_MASTER AND A PURCHASE_ORDER_LINE_ITEM table. Then we might have a series of M:M relationships for example. An ITEM might have a different price for specific time periods for specific stores.
With OLAP, the tables are designed to facilitate easy access to information. Today's OLAP tools make the job of developing a query very easy. However, you still want to minimize the extensiveness of the relational model in an OLAP application. Users don't have the wills and means to learn how to work through a complex maze of table relationships. So you'll design your tables with a high degree of denormalization. The most prevalent design scheme for OLAP is the Star-Schema, popularized by Ralph Kimball. The star schema has a FACT table that contains the elements of data that are used arithmatically (counting, summing, averaging, etc.) The FACT Table is surrounded by lookup tables called Dimensions. Each Dimension table provides a reference to those things that you want to analyze by. A good book to understand how to design OLAP solutions is The Data Warehouse Toolkit: Practical Techniques for Building Dimensional Data Warehouses by Ralph Kimball.
Example: let's say we want to see some key measures about purchases. We want to know how many items and the sales amount that are purchased by what kind of customer across which stores. The FACT table will contain a column for Qty-purchased and Purchase Amount. The DIMENSION tables will include the ITEM_DESC (contains the item_id & Description), the CUSTOMER_TYPE, the STORE (Store_id & store name), and TIME (contains calendar information such as the date, the month_end_date, quarter_end_date, day_of_week, etc).
Database Fundamentals > Data Warehousing and Business Intelligence with Mike Lampa
Search Advice from more than 250 TechTarget Experts
Your question may have already been answered! Browse or search more than 25,000 question and answer pairs from more than 250 TechTarget industry experts.

Differnce between periodic and Resourse billing.

Differnce between periodic and Resourse billing, and how to do it in sap?..
Can anyone suggest me step wise
Thanks in advance

Periodic billing is used when you want to bill the customer at different points of time based on the periodicity or progress of the work. Milestone billing can be used for this type of billing purposes when you want to have billing control from the project.
Resource billing is based on the resource consumption for the particular activities. Dynamic Item Processor (DIP) profile is used for the resource related billing.
Further information acn be had from the link
[http://help.sap.com/saphelp_47x200/helpdata/en/aa/96853478616434e10000009b38f83b/frameset.htm]
Hope this is of some help
Venu

Activity System status: differences between u0093Openu0094 and u0093In processu0094 status

Dear Experts,
Whats the difference between Open and In process system status? In help.sap.com it: There are four system statuses that represent the life cycle of the business transaction:
Open: has been recently created and not yet processed (for example, contract from the Internet)
In process: administrator is clearing up questions
But, how does the system assumes the In Process status ?? Ive tested business activities creation with different employees assigned and, when editing and saving the business activities with these BPs the system status does not change.
However, in other unknown situations the status system is changed to in Process.
Any ideas about the meaning of the In Process status? And when the business activity switches to that?
Thanks in advance,
Joao

Hi,
These four system statuses that represent the life cycle of the business transaction:
·        Open: has been recently created and not yet processed (for example, contract from the Internet)
·        In process: administrator is clearing up questions
·        Released: contract is complete and legal. Follow-up processes can be started (printing, billing, distribution, releases and so on)
·        Completed: All actions directly linked to contract are completed
·        Closed: all actions indirectly linked to the contract are closed (for example, from R/3: batch run to actual costs)
Each status having its own control at the configuration level. If you observe the following process you may understand the importance of various statuses.
For example in any transaction by default status would be Open. Once the transaction opened by the respective responsible person he will change the status as In Process, Once the assigned task is completed he will change the status as Completed.
Please notice the configuration settings in the following navigation path:
SPRO->IMG->CRM->Transactions->Basic Functions->Status Management-> Change Status Profile for User Status->Select Quotation->Double click on the different status. You can observe the difference.
Hope I convinced.
Best Regards,
Johnny.
Reward if it helps.

Can any one tell me the difference between VK11 and MR21

Hi Folks,
I have changed price of a material using VK12.
When I go to the transaction MR21, it is still showing the old price.
Can any one help what is the difference between VK11 and MR21.
And i which scenarios these two were used?
Thanks in Advance
Gopi Krishna

Hii,
VK11: This is price master record to determine the sale price or discounts or freight or taxes which we going to charge to the final customer. Through this transaction we will determine the price automatically either in sales or billing document. These transaction is only applicable for sales & distribution module for determining the pricing for customers.
The price determined through this we use in revenue realisation.
MR21: Through this trnsaction Finance or Cost users upload the cost of the material. The cost is
Standard Cost or Moving average cost.
Cost= Raw Material CostProcessing Cost(product process cost )Overheads(employee salaries)
This cost is maintained at each material master in accounting view either standard cost or moving average cost.
These cost is determined for every material movement within the company.
Example: Production, transfer posting, goods issue- system post the quantity and at the same time system create an inventory entry i.e accounting entry for the transaction. In this accounting entries, system consider the values from material master for generating accounting entry.
If you upload production for 10 MT of material A and in material master if kept the cost of the material as 1000 then the accounting entry in production time as
Finish Goods Dr 10000
To Cost of Production Cr 10000
These cost also determined sales transaction through VPRS condition type.
Rewards if it helps
Regards
Goutham

Difference between soa and esoa

Hi,
What is the difference between SOA AND ESOA.
Regards
Abhay

Hi
In a nutshell, ESOA are simply Web services that provide enterprise-level business functionality.They may range from very simple lookup services (like finding a companys location or product offerings) to more complex and composite services but what they have in common is that theyre highly integrated into your process or application.Typically ESOA are high-level components that take more granular Web services and aggregate them into reusable elements with business value. For example, take the service Cancel Purchase Order. An elementary Web service like Delete Purchase Order would simply lead to the deletion of a purchase order in the corresponding database. However, if the stated goal is cancel purchase order, the service has to become a more far-reaching enterprise service that handles this process end-to-end, and therefore has to trigger a number of follow-up actions, including:
=> Check against production orders
=> Check against a corresponding billing process
=> Update of inventory/warehouse information Or consider the Credit Limit Check
service, which at first glance seems to be quite simple. Normally, this service is one ingredient of the Order Creation service. But typically, credit checking is
really a more elaborate composite service.
5 Key Principles of ESOA
1. Abstraction hiding confusing details
2. Modularity breaking down complexity, resulting in reusable pieces
3. Standardized connectivity enabling flexible composition of services to
create bigger processes and scenarios
4. Loose coupling allowing for separate evolution of the various components
without breaking any points of integration
5. Incremental design enabling changes to composition and configuration
without affecting the interior of components, and vice versa
Regards,
Satyendra

Report - quantity and value difference between delivery and invoice?

Hello experts,
My client use u201EProof of deliveryu201D t-code: VLPOD. There is always quantity and value difference between delivery and invoice.
Do you know any report which will show this differences between delivery and invoice?
Best regards,
Maciej

Hi,
Note 867678 - Proof of delivery (POD), delivery and billing document will help you to understand POD flow.
You have the tcode VLPODF/VLPODL/VLPODA, but perhaps they will not help you. So, as the before note suggests you, you can use the tables VBFA, LIKP, LIPS, VBRK, VBRP, TVPOD and TVPODG to do your own report.
I hope this helps you
Regard,
Eduardo

Difference between LIS and Lo extraction

Hi,
Wat is the Difference between LIS and LO extraction.
Thanks,
Sanu

HI
One good difference between lis and los is
lis uses transparent tables where as los use cluster tables
ust some infos about LIS flows....
with Plug-In 2001.2 S2xx-Structures have been replaced by Logistics Extraction Cockpit. However, R/3 releases 4.x support S2xx-Structures and Logistics Extraction Cockpit in parallel.
With new LBWE extractors there are a lot of benefits:
- Detailed Extraction: extraction can be deactivated (e.g. Schedule Line Data) leads to leaner extractors with less volume.
- Document Changes: only BW-relevant data changes will be updated (less upload volume).
- LIS-Tables are not updated reduced data volume due to avoided redundancy.
- Update with Batch-Process (V3) -> no load on daily business (but now there are available different delta methods as the direct delta...)
- No LIS-Know How necessary.
- Functional Enhancements easy to be done.
- Central, uniform maintenance tool for logistics applications (LBWE)
- No Delta-Tables (SnnnBIW1/-2) no double update, no double Data-Storage
- A lot of flows are covered: Purchasing,Inventory Controlling, Shop Floor Control, Quality Management, Shipment, Sales, Shipping, Billing, Plant Maintenance, Customer Service,
hope this helps

Performance difference between page and scroll

Hi experts:
What is the technical difference between paging and scrolling, especially as pertains to database access and performance? The scenario would be a table result in a view where 200 results exist for a query. A scrollable table would show all results, while the paging table would show 10/20 per page. Is the database selection the same for both approaches? Or is the paging approach going to make more trips? If there are trips - how does the UI know how many pages should be presented? Is one or the other a better approach for data which is not existing in CRM system?
regards,
bill.

If you look at the servlet translated from a JSP, you'll see these lines:
Object page = this;
pageContext = _jspxFactory.getPageContext(this, request, response,
null, true, 8192, true);
_jspx_page_context = pageContext;
application = pageContext.getServletContext();So page is simply an alias for this.
And PageContext is analogous to ServletContext but please notice, it's not the same or a replacement; application is the implicit reference to ServletContext and not pageContext. There is no equivalent of pageContext in servlets.
Please note that the page scope doesn't refer to the page object but to the pageContext. Therefore, what Manivel said above
page is used as a scope with in one jspisn't correct.
Edited by: nogoodatcoding on Sep 24, 2007 1:30 PM

What is the difference between lap and oltp

HI experts, I want to know the difference between OLAP and OLTP and why OLTP cannot be used in bw instead of OLAP? Need realtime anwsers please!!!!!!!!!!

hi navin...
Online transactional processing (OLTP) is designed to efficiently process high volumes of transactions, instantly recording business events (such as a sales invoice payment) and reflecting changes as they occur.
Online analytical processing (OLAP) is designed for analysis and decision support, allowing exploration of often hidden relationships in large amounts of data by providing unlimited views of multiple relationships at any cross-section of defined business dimensions.
OLTP databases are typically input sources for data warehouses or data marts. The data warehouse in turn is the typical source of data for an OLAP database. The value in an OLAP database is that many complex calculations and predefined queries are preprocessed and results are stored and are available via an OLAP exploitation application allowing quick access to cross-sections of business data. Rapid access to the aggregate information across defined business dimensions allows quick navigation and understanding of relationships.
The challenge is to find a solution that will both supply the necessary functionality while addressing the technical considerations of your organization. Some other important considerations include choosing technologies that can leverage existing investments in both hardware and software, and are open and integrated so that your applications are adaptable. This ensures flexibility and agility to meet future business demands.
There are several different modeling techniques. Snowflake and star schemas are just two of many choices. Deciding the best approach for your situation will depend on several factors, most importantly understanding the business issue, the users and their information needs. There is a wealth of information available, including courses, texts and guidelines on this subject alone
OLAP systems organize data in a multidimensional model that is suitable for decision support. OLAP is the analytical counterpart of OLTP, or Online Transactional Processing. SAP's BW is an OLAP system
The Impact of the OLAP/OLTP Cultural Conflict on Data Warehousing....check this link....
http://www.georgetown.edu/users/allanr/Impact.pdf
also check...
http://expertanswercenter.techtarget.com/eac/knowledgebaseAnswer/0,295199,sid63_gci977813,00.html
The big difference when designing for OLAP versus OLTP is rooted in the basics of how the tables are going to be used. I'll discuss OLTP versus OLAP in context to the design of dimensional data warehouses. However, keep in mind there are more architectural components that make up a mature, best practices data warehouse than just the dimensional data warehouse.
Corporate Information Factory, 2nd Edition by W. H. Inmon, Claudia Imhoff, Ryan Sousa
Building the Data Warehouse, 2nd Edition by W. H. Inmon
With OLTP, the tables are designed to facilitate fast inserting, updating and deleting rows of information with each logical unit of work. The database design is highly normalized. Usually and at least to 3NF. Each logical unit of work in an online application will have a relatively small scope with regard to the number of tables that are referenced and/or updated. Also the online application itself handles the majority of the work for joining data to facilitate the screen functions. This means the user doesn't have to worry about traversing across large data relationship paths. A heavy dose of lookup/reference tables and much focus on referential integrity between foreign keys. The physical design of the database needs to take into considerations the need for inserting rows when deciding on physical space settings. A good book for getting a solid base understanding of modeling for OLTP is The Data Modeling Handbook: A Best-Practice Approach to Building Quality Data Models by Michael C. Reingruber, William W. Gregory.
Example: Let's say we have a purchase oder management system. We need to be able to take orders for our customers, and we need to be able to sell many items on each order. We need to capture the store that sold the item, the customer that bought the item (and where we need to ship things and where to bill) and we need to make sure that we pull from the valid store_items to get the correct item number, description and price. Our OLTP data model will contain a CUSTOMER_MASTER, A CUSTOMER_ADDRESS_MASTER, A STORE_MASTER, AN ITEM_MASTER, AN ITEM_PRICE_MASTER, A PURCHASE_ORDER_MASTER AND A PURCHASE_ORDER_LINE_ITEM table. Then we might have a series of M:M relationships for example. An ITEM might have a different price for specific time periods for specific stores.
With OLAP, the tables are designed to facilitate easy access to information. Today's OLAP tools make the job of developing a query very easy. However, you still want to minimize the extensiveness of the relational model in an OLAP application. Users don't have the wills and means to learn how to work through a complex maze of table relationships. So you'll design your tables with a high degree of denormalization. The most prevalent design scheme for OLAP is the Star-Schema, popularized by Ralph Kimball. The star schema has a FACT table that contains the elements of data that are used arithmatically (counting, summing, averaging, etc.) The FACT Table is surrounded by lookup tables called Dimensions. Each Dimension table provides a reference to those things that you want to analyze by. A good book to understand how to design OLAP solutions is The Data Warehouse Toolkit: Practical Techniques for Building Dimensional Data Warehouses by Ralph Kimball.
Example: let's say we want to see some key measures about purchases. We want to know how many items and the sales amount that are purchased by what kind of customer across which stores. The FACT table will contain a column for Qty-purchased and Purchase Amount. The DIMENSION tables will include the ITEM_DESC (contains the item_id & Description), the CUSTOMER_TYPE, the STORE (Store_id & store name), and TIME (contains calendar information such as the date, the month_end_date, quarter_end_date, day_of_week, etc).
Database Fundamentals > Data Warehousing and Business Intelligence with Mike Lampa
Search Advice from more than 250 TechTarget Experts
Your question may have already been answered! Browse or search more than 25,000 question and answer pairs from more than 250 TechTarget industry experts.
hope it helps...

Periodic billing and Milestone billing

Dear SD gurus,
Can anybody explain what is Periodic billing and Milestone billing?
If you have the configuration guide for the above, please send the same to my email id : [email protected]
Thanks in advance
Regards
Manivannan R

Hi,
Milestone billing means distributing the total amount to be billed over multiple billing
dates in the billing plan.
As each milestone is successfully reached, the customer is billed either a percentage of
the entire project cost or simply a pre-defined amount.
During sales order processing, the system determines from the item category whether a
billing plan is required and, if so, which type of plan
The type of billing plan that is determined at this point is set up in Customizing and
cannot be changed in the sales document.
Billing plans for periodic billing and milestone billing plans for project-related milestone
billing have different overview screens so that you can enter data relevant to your
processing.
For example, for milestone billing, you must be able to enter data to identify the
individual milestones.
IMG configuration requires :-
1. Maintain billing plan types for milestone billing in OVBO.
2. Define date description in SM30 - V_TVTB.
3. Maintain Date Category for Billing Plan Type IN OVBJ.
4. Allocate date category in SM30 - V_TFPLA_TY.
5. Maintain date proposal for Billing Plan Type in OVBM.
6. Assign Billing Plan Type to Sales Documents Type in OVBP.
7. Assign Billing Plan Type to Item Categories in OVBR.
8. Define rules for determining the date in OVBS.
Milestone billing is typically used for billing projects, such as plant engineering and
construction projects. Such projects often include a series of milestones that mark the
completion of different stages of the work. In the SAP R/3 System, milestones are defined
in a network along with planned and actual dates for the completion of work. The milestones
are also assigned to the billing dates in the billing plan.
Each milestone-related billing date is blocked for processing until the Project System
confirms that the milestone is completed.
Delivery-relevant order items for which a milestone billing plan applies are billed on the
basis of the requested delivery quantity and not on the total of the confirmed quantities.
The connection between the project and the sales document item is made in the individual
schedule lines of the item. Each schedule item can be assigned to a network in a project.
To display the project-related data for a schedule line, proceed as follows:
In one of the overview screens of the sales document, select
1. Item -> Schedule lines.
2. Mark the schedule line and select Procurement details.
The following figure shows an example of milestone billing where only the Contract have
been billed :
Order Item Turbine 100,000
Billing Plan
Billing date Description % Value Billing Block Milestone Billing Status
01-10-94 Contract 10 10,000 - x x
01-03-95 Assembly 30 30,000 x x
01-04-95 Maintenance 30 30,000 x x
01-05-95 Acceptance 30 30,000 x x
01-06-95 Final invoice .. .. x
Network/Activities
Milestone Estimate Actual
Assembly 01-03-95 01-03-95
Maintenance 01-04-95
Acceptance 01-05-95
For each billing date in a milestone billing plan, you can specify whether the billing
date is:
1. fixed
2. always updated with the actual date of the milestone
3. updated with the actual date of the milestone, if the date is earlier than the
planned billing date for the date
reward points if it helps
Regards
Govind.

Difference between Null and null?

What is the difference between null and NULL?
When is each used?
Thanks,

veryConfused wrote:
There is a null in java, but no NULL. null means no value. However, when assigning value, the following is different:Although the empty String has no special role. Null means, the referential type is not assigned (doesn't refer) to a specific object. The empty String is just another object though, so seeing it or pointing it out as something special when it actually isn't at all (no more special than new Integer(0) or new Object[0]) just adds to the confusion.

Difference between downpayment and Milestone billing

Similar Messages

Maybe you are looking for