SAP Enterprise One - Sales Commission And Buyer Statement Reports
As within the majority of mid-market ERP and accounting functions SAP B1 has customizable fee and bill forms. Nevertheless being versatile within the sense of creating consumer defined fields and tables likelihood is high that your imaginative and prescient and formulation are based on these objects. It's natural to decide design work to be completed in CR as SAP owns this device and recommends for managerial reporting. We are going to attempt to come by means of customization and design pitfalls and recommendations to avoid them. This paper is not intended to be a technical information for programmer as it's slightly FAQ style collection of recommendations:

1. Commission formulas. Real life is rich in case studies and we now have seen clients where formulas have a number of tiers and so they have efficient date from and to just to open the list of doable scenarios. When you acknowledge your case then good idea is to create few consumer outlined tables and use them for calculations

2. Statement. In varied industries you may need parallel items that should be present on the printed form. For example it might be billed and actual minutes in advertising

3. Person defined fields and tables. There isn't a have to do software development so as to create these objects. They could be created in consumer interface: Instruments -> Customization Instruments -> Person defined tables and fields administration and from here use your intuition or read person manual. The nice thing right here is the truth that these objects are created in SQL tables in metadata and they're neutral to version upgrade. So feel free to deploy this technique. Typically you might be sending buyer invoices or sales orders from external database or application. In this case it is good idea to send them first to consumer defined tables and then deploy Software Development Kit C or VB programming in Microsoft Visible Studio to rework the rows into real Invoices and Orders

4. Design. Now let's talk concerning the design itself. It is paradoxical however our advice is start this process in SQL Server Management Studio queries. Crystal is perfect software but if formulas change in the future it is perhaps troublesome to comply with these adjustments in Designer tool. Much simpler is to create SQL View or even stored process the place all the arithmetic is completed and base report on these SQL units. If you're designing something complicated with formulation then you could be disenchanted with design results getting rows duplications and other annoying bugs. SQL is better positioned to do math. Normal concept is the following - try your query in SQL until you're satisfied with result and only after open CR Designer tool to finish structure and such cosmetics as firm logo and other graphical elements

5. Now fields and tables structures. There are two methods to discover these. First is to print it out from SDK within the form of complete and really complicated diagram. And the second option is to change in menu View System Information. Then open the shape with the table and area in query and place cursor over. Take a look at backside left nook where you ought to be able to read names. Attempt it by yourself and see should you obtained the identical results. Sales Order header is hosted in ORDR and lines in RDR1 tables respectively.