Browsing Chinese (Simplified) translation

110 of 3695 results
863.
The :guilabel:`Account Type` entry is taken from the list of types that you just created. Although it looks a bit like a text box, it does not behave in quite the same way. A single :kbd:`Del` or :kbd:`Backspace` keystroke is all you need to delete the whole text, and when you type the name (or part of the name), you still need to associate that text with the entry by clicking the :guilabel:`Search More`.
(no translation yet)
Located in ../../source/book/1/1_3_Real_Case/1_3_Real_Case_db_setup.rst:82
910.
In case you had chosen to :guilabel:`Skip Configuration Wizards` when you first created the database, you may configure your company information in the following manner. Start configuring your database by renaming the :guilabel:`Main Company` from its default of \ ``Your Company``\ to the name of your own company or (in this case) another example company. When you print standard documents such as quotations, orders and invoices you will find this configuration information used in the document headers and footers.
(no translation yet)
Located in ../../source/book/1/1_3_Real_Case/1_3_Real_Case_db_setup.rst:170
924.
Figure :ref:`fig-oech03co` shows the effect of this. You can also change various other company-wide parameters for reports and scheduling in the other tabs, and you can upload a company logo of a specific size for the reports. Click :guilabel:`Save` to store this.
(no translation yet)
Located in ../../source/book/1/1_3_Real_Case/1_3_Real_Case_db_setup.rst:213
952.
Unlike partner categories and their assigned partners, product categories do have an effect on the products assigned to them – and a product may belong to only one category. Under the main menu link :menuselection:`Warehouse` or :menuselection:`Sale`, select the menu :menuselection:`Configuration --> Products --> Products Categories` and click :guilabel:`Create` to get an empty form for defining a product category.
(no translation yet)
Located in ../../source/book/1/1_3_Real_Case/1_3_Real_Case_db_setup.rst:309
953.
Enter \ ``Radiators``\ in the :guilabel:`Name` field. You will see that other fields, specifically those in the :guilabel:`Accounting Properties` section, have been automatically filled in with values of accounts and journals. These are the values that will affect products – equivalent fields in a product will take on these values if they, too, are blank when their form is saved. Click :guilabel:`Save`.
(no translation yet)
Located in ../../source/book/1/1_3_Real_Case/1_3_Real_Case_db_setup.rst:315
955.
Properties have a rather unusual behavior. They are defined by parameters in the menus in :menuselection:`Settings --> Technical --> Parameters --> Configuration Parameters`, and they update fields only when a form is saved, and only when the fields are empty at the time the form is saved. You can manually override any of these properties as you need.
(no translation yet)
Located in ../../source/book/1/1_3_Real_Case/1_3_Real_Case_db_setup.rst:323
969.
Click the :guilabel:`Accounting` tab, then click :guilabel:`Save` and observe that :guilabel:`Accounting Properties` here remain empty. When product transactions occur, the Income and Expense accounts that you have just defined in the Product Category are used by the Product unless an account is specified here, directly in the product, to override that.
(no translation yet)
Located in ../../source/book/1/1_3_Real_Case/1_3_Real_Case_db_setup.rst:374
980.
So the :guilabel:`Location Input` can be placed as a child of the :guilabel:`Location Stock`, which means that when :guilabel:`Location Stock` is interrogated for product quantities, it also takes account of the contents of the :guilabel:`Location Input`. :guilabel:`Location Input` could be used as a goods-in QC location. The :guilabel:`Location Output` must never be placed as a child of :guilabel:`Location Stock`, since items in :guilabel:`Location Output`, which can be considered to be packed ready for customer shipment, should not be thought of as available for sale elsewhere.
(no translation yet)
Located in ../../source/book/1/1_3_Real_Case/1_3_Real_Case_db_setup.rst:429
983.
A number of account charts have been predefined for OpenERP, some of which meet the needs of national authorities (the number of those created for OpenERP is growing as various contributors create and freely publish them). You can take one of those without changing it if it is suitable, or you can take anything as your starting point and design a complete chart of accounts to meet your exact needs, including accounts for inventory, asset depreciation, equity and taxation.
(no translation yet)
Located in ../../source/book/1/1_3_Real_Case/1_3_Real_Case_db_setup.rst:447
1001.
Or you can just continue working with the \ ``openerp_ch03``\ database to get through this chapter. You can recreate \ ``openerp_ch03``\ quite quickly if something goes wrong and you cannot recover from it but, again, you would need to know your super-administrator password for that.
(no translation yet)
Located in ../../source/book/1/1_3_Real_Case/1_3_Real_Case_db_setup.rst:512
110 of 3695 results

This translation is managed by OpenERP Chinese Translation Team, assigned by Odoo Translators (MOVED TO TRANSIFEX).

You are not logged in. Please log in to work on translations.

Contributors to this translation: AllanWong, Baich-info, CID, DWXXX, David ma, James Yu, Jerry, Jon Chow, Joshua Jan(SHINEIT), PeterGao, Talent, Tom, Tommy.Yu, Victor Yu, Williams-Lu, Wonrence, Xavier (Open ERP), anzhlzjj, buke, caosen, carygrant, chaochen, ginozhang, hao_1_2_3, jun, leangjia, liAnGjiA, mrshelly, stone, sunk, tomcay, tp, wenzioooo, xday2000, yijingchang, yourday, youring, 卓忆科技, 广州-卡桑, 开阖软件 Jeff Wang, 木头, 盈通 ccdos, 若水.