OracleUG http://oracleug.com/rss.xml en Pricing Security http://oracleug.com/node/2558 <span class="field field-node--title field-name-title field-type-string field-label-hidden">Pricing Security</span> <span class="field field-node--uid field-name-uid field-type-entity-reference field-label-hidden"><span>Anonymous (not verified)</span></span> <span class="field field-node--created field-name-created field-type-created field-label-hidden">Wed, 07/25/2012 - 14:42</span> <div class="layout layout--onecol"> <div class="layout__region layout__region--content"> <section class="clearfix block block-layout-builder"> <div class="clearfix field field-node--body field-name-body field-type-text-with-summary field-label-hidden"> <div class="field-items"> <div class="field-item"><p><img class="left framed" alt="" width="600" height="358" src="/sites/default/files/users/oracleug/advp_001_0.png" /><br /> In addition to the functional security, Oracle Advanced Pricing provides an additional level of security <br /> called pricing security. Pricing security provides an additional security which can be used to restrict pricing activities such as updating and viewing pricing entities to users who are granted specific access privileges.</p> <p>Oracle Pricing Administrator responsibility can be used for pricing security set up and maintenance.  This responsibility provides an HTML user interface and provides the authorization to access &amp; update all pricing entities. The features provide by pricing security are:</p> <p><span style="color: #993300"><b>1. Restricting pricing entities to operating units: <br /></b></span>Pricing entities (Price list &amp; Modifiers) are not part of the multi-org structure provided by oracle EBS but pricing security can be used to assign a pricing entity to a specific operating unit.</p> <p>You can restrict usage to one operating unit or allow usage by all operating units by making it Global.<br /><b>Global Usage: </b>A pricing entity can be used across all operating units when making a pricing request. A pricing entity is originally owned by the creating organization. At creation checking the 'Global' flag allows usage across operating units; unchecking it restricts usage to the owner organization. Ownership/Usage may be updated on this page.</p> <p><span style="color: #993300"><b>2. Restricting pricing entities to grantee (Global, Operating Unit, Responsibility, or User level) :<br /></b></span>You can grant view-only or maintain access privileges to functional users at the Global, Operating Unit, Responsibility, or User level.</p> <p><span style="color: #993300"><u><b>Pricing Security Terms (as in Oracle user guide)</b></u></span></p> <p><span style="color: #993300"><u><b><img class="left framed" alt="" width="365" height="279" src="/sites/default/files/users/oracleug/advp_002.png" /><br /></b></u></span>The following terms are used in Oracle pricing security:</p> <p><span style="color: #003366"><b>1.1 Pricing Entity:</b></span> A pricing entity can be a price list, modifier list, or pricing agreement.</p> <p><span style="color: #003366"><b>1.2 Entity Set:</b></span> A set of pricing entities that can be used as an Entity Type to which you<br /> can grant privileges with Maintain or View-Only access levels.</p> <p><span style="color: #003366"><b>1.3 Entity Type: </b></span>A term used to describe one of the following pricing entities: Standard Price list, Modifier List, Pricing Agreement, and Entity Set.</p> <p><span style="color: #003366"><b>1.4 Entity Usage:</b></span> Grants the usage of the entity to one or all operating units so that it can be used during pricing engine calls.</p> <p><span style="color: #003366"><b>1.5 Global Usage:</b></span> When Global Usage is set to Yes for a pricing entity, it can be used across all operating units for processing orders. If No is selected, the usage of the entity is restricted to the operating unit that created or owns it.<br /> When security is turned on, a Global box indicating Global Status is dynamically added to the header region of all price lists and modifiers. A user with Maintain access privileges can update the Global box.</p> <p><span style="color: #003366"><b>2.1 Grantee: </b></span>The specific user or users for a Grantee Type who are given permission to view or maintain a pricing entity. Used in combination with a Grantee Type. </p> <p><span style="color: #003366"><b>2.2  Grantee Type:</b></span> The level to which privileges are granted:</p> <ul><li>Global: Includes all users with access to pricing menus.</li> <li>Operating Unit: Includes users who have the named operating unit as the default operating unit (as specified in MO: Default Operating Unit profile).</li> <li>Responsibility: Includes users within the named responsibility.</li> <li>User: Specifies a named user.</li> </ul><p><span style="color: #003366"><b>2.3  Access Level: </b></span>Provides Maintain or View-Only access to a pricing entity:</p> <ul><li>View-Only: Enables the user to view but not update the pricing entity.</li> <li>Maintain: Enables the user to view and update pricing entities. Not all of the entities support delete capabilities.</li> </ul><p><span style="color: #993300"><u><b>Advanced Pricing Responsibilities:<br /></b></u></span>Advanced Pricing comes with three seeded responsibilities. These responsibilities have different purposes as explained below.</p> <p><b><span style="color: #003366">Oracle Pricing Administrator<br /></span></b>The user who is assigned the Oracle Pricing Administrator responsibility has complete access to all pricing entities without restriction and is responsible for the global setup and administration of pricing security.<br /> The administrator is responsible for Privileges, Entity Sets &amp; Entity Usage setups.</p> <p><span style="color: #003366"><b>Oracle Pricing Manager<br /></b></span>The user who is assigned the Oracle Pricing Manager responsibility can access all features for setting up, using, and maintaining pricing features and functions (except pricing security) such as price lists, pricing formulas, modifiers, attribute management, and item and category management.</p> <p><span style="color: #003366"><b>Oracle Pricing User<br /></b></span>This responsibility provides access to the HTML user interface where you can create price lists and modifiers (Deal, Discount, Promotion, Surcharge), access the price list maintenance feature, and attach qualifiers and qualifier groups to modifiers and price lists.<br />  </p> </div> </div> </div> </section> <section class="clearfix block block-layout-builder"> </section> <section class="clearfix block block-layout-builder"> <section class="field field-node--comment-node-book field-name-comment-node-book field-type-comment field-label-hidden comment-wrapper"> </section> </section> </div> </div> Wed, 25 Jul 2012 09:12:47 +0000 Anonymous 2558 at http://oracleug.com http://oracleug.com/node/2558#comments Capacity Setup http://oracleug.com/node/2452 <span class="field field-node--title field-name-title field-type-string field-label-hidden">Capacity Setup</span> <span class="field field-node--uid field-name-uid field-type-entity-reference field-label-hidden"><span>Anonymous (not verified)</span></span> <span class="field field-node--created field-name-created field-type-created field-label-hidden">Wed, 04/18/2012 - 17:37</span> <div class="layout layout--onecol"> <div class="layout__region layout__region--content"> <section class="clearfix block block-layout-builder"> <div class="clearfix field field-node--body field-name-body field-type-text-with-summary field-label-hidden"> <div class="field-items"> <div class="field-item"><p><img class="left framed" alt="" width="539" height="320" src="/sites/default/files/users/oracleug/cp_002.png" /><br /> Make sure you set up oracle Inventory, BOM, MRP/ASCP correctly before starting the setups for Oracle Capacity.<br /> The steps shown in the above pic are the set up steps just for the Capacity product. All these setup steps are optional.</p> <p><span style="color: #993300"><u><b>Resource Group</b></u></span><span style="color: #993300"><u><b><img class="left framed" alt="" src="/sites/default/files/users/oracleug/cp_003_0.png" /><br /></b></u></span></p> <p>Resource groups are used to group key/critical/similar resources. <br /> Resource group is a user level lookup, so you can define as many resource groups as per the business requirement.  Once defined, you can assign selected resources to a resource group in Oracle Bills of Material.</p> <p>You can choose a specific resource group when using the bill of resources load to generate a bill of resources. You can then use the bill of resources to generate a RCCP plan that only considers the resources contained in your resource group.</p> <p>You can define a maximum of 250 resource groups, and you cannot change the values in this field after you commit a resource group. To remove an obsolete resource group you can either disable the code, enter an end date, or change the meaning and description to match a replacement code<br />  </p> </div> </div> </div> </section> <section class="clearfix block block-layout-builder"> </section> <section class="clearfix block block-layout-builder"> <section class="field field-node--comment-node-book field-name-comment-node-book field-type-comment field-label-hidden comment-wrapper"> </section> </section> </div> </div> Wed, 18 Apr 2012 12:07:30 +0000 Anonymous 2452 at http://oracleug.com http://oracleug.com/node/2452#comments Capacity Planning http://oracleug.com/node/2451 <span class="field field-node--title field-name-title field-type-string field-label-hidden">Capacity Planning</span> <span class="field field-node--uid field-name-uid field-type-entity-reference field-label-hidden"><span>Anonymous (not verified)</span></span> <span class="field field-node--created field-name-created field-type-created field-label-hidden">Wed, 04/18/2012 - 16:46</span> <div class="layout layout--onecol"> <div class="layout__region layout__region--content"> <section class="clearfix block block-layout-builder"> <div class="clearfix field field-node--body field-name-body field-type-text-with-summary field-label-hidden"> <div class="field-items"> <div class="field-item"><p><img class="left framed" width="465" height="442" alt="" src="/sites/default/files/users/oracleug/cp_001.png" /><br /> Capacity planning is the process of determining the production capacity needed by an organization to meet changing demands for its products. In the context of capacity planning, "capacity" is the maximum amount of work that an organization is capable of completing in a given period of time.</p> <!--break--><p>Capacity is defined as the capability of a worker, machine, work center, plan or organization to produce output per period of time. Capacity is a rate of doing work, not the quantity of work done.<br /> (Source : <a href="http://www.apicsforum.com/ebook/5b._capacity_management">http://www.apicsforum.com/ebook/5b._capacity_management</a>)</p> <p><span style="color: #993300"><b>Capacity available </b></span>is the capacity of a system or resource to produce a quantity of output in a given time period.</p> <p><span style="color: #993300"><b>Load </b></span>is the amount of released and planned work assigned to a facility for a particular time period. It is the sum of all the required capacities.</p> <p><span style="color: #3366ff">Oracle Capacity lets you calculate your capacity load ratio by resource or production line</span>. It ensures that you have sufficient capacity to meet your production requirements.</p> <p>Oracle Capacity provides you with two levels of capacity planning:<br /><span style="color: #993300"><b>Rough cut capacity planning (RCCP)</b></span> to validate your master schedules<br /> Detailed <span style="color: #993300"><b>capacity requirements planning</b></span> (CRP) to validate your MRP plans</p> <p> </p> </div> </div> </div> </section> <section class="clearfix block block-layout-builder"> </section> <section class="clearfix block block-layout-builder"> <section class="field field-node--comment-node-book field-name-comment-node-book field-type-comment field-label-hidden comment-wrapper"> </section> </section> </div> </div> Wed, 18 Apr 2012 11:16:06 +0000 Anonymous 2451 at http://oracleug.com http://oracleug.com/node/2451#comments Transactions http://oracleug.com/node/2448 <span class="field field-node--title field-name-title field-type-string field-label-hidden">Transactions</span> <span class="field field-node--uid field-name-uid field-type-entity-reference field-label-hidden"><span>Anonymous (not verified)</span></span> <span class="field field-node--created field-name-created field-type-created field-label-hidden">Mon, 04/16/2012 - 17:15</span> <div class="layout layout--onecol"> <div class="layout__region layout__region--content"> <section class="clearfix block block-layout-builder"> <div class="clearfix field field-node--body field-name-body field-type-text-with-summary field-label-hidden"> <div class="field-items"> <div class="field-item"><p><a href="/sites/default/files/users/oracleug/AR_002_0.png"><img class="left framed" width="600" height="324" alt="" src="/sites/default/files/users/oracleug/AR_002_0_0.png" /></a></p> <p>Similar to 11i &amp; R12, You can create below transactions in fusion receivables<br /> • Invoices and Debit Memos<br /> • Credit Memos<br /> • On-Account Credit Memos<br /> • Chargebacks<br /> • Adjustments</p> <p>All the new fields in fusion application transaction form are outlined in the above pic.</p> <p>Business unit: Similar to operating unit in 11/R12<br /> Accounting Date: GL date in 11i<br /> Attachment Note</p> <p>Question : Where is the legal entity information ?</p> <p>Click on more and navigate to miscellaneous tab to verify the other details<br />  <br /><img alt="" width="931" height="254" src="/sites/default/files/users/oracleug/AR_003.png" /><br />  <br /> The <span style="color: #993300"><b>RA_CUSTOMER_TRX</b></span> table stores invoice, debit memo and credit memo header information. Each of these transactions is stored as a unique record, based on the primary key customer_trx_id. The transaction number, transaction date and billing customer are stored in the trx_number, trx_date and bill_to_customer_id columns respectively.</p> <p>The <span style="color: #993300"><b>RA_CUSTOMER_TRX_LINES </b></span>table stores invoice, debit memo and credit memo line level information. Each transaction line is stored as a unique record, based on the primary key customer_trx_line_id column. The customer_trx_id column is a foreign key to the RA_CUSTOMER_TRX table.</p> <p>The <span style="color: #993300"><b>AR_PAYMENT_SCHEDULES </b></span>table stores customer balance information at the transaction level. Each transaction balance is stored as a unique record, based on the primary key payment_schedule_id. The class column identifies the transaction type and determines which columns Receivables updates when a transaction is stored.</p> </div> </div> </div> </section> <section class="clearfix block block-layout-builder"> </section> <section class="clearfix block block-layout-builder"> <section class="field field-node--comment-node-book field-name-comment-node-book field-type-comment field-label-hidden comment-wrapper"> </section> </section> </div> </div> Mon, 16 Apr 2012 11:45:03 +0000 Anonymous 2448 at http://oracleug.com http://oracleug.com/node/2448#comments Oracle Fusion Receivables http://oracleug.com/node/2447 <span class="field field-node--title field-name-title field-type-string field-label-hidden">Oracle Fusion Receivables</span> <span class="field field-node--uid field-name-uid field-type-entity-reference field-label-hidden"><span>Anonymous (not verified)</span></span> <span class="field field-node--created field-name-created field-type-created field-label-hidden">Mon, 04/16/2012 - 16:48</span> <div class="layout layout--onecol"> <div class="layout__region layout__region--content"> <section class="clearfix block block-layout-builder"> <div class="clearfix field field-node--body field-name-body field-type-text-with-summary field-label-hidden"> <div class="field-items"> <div class="field-item"><p><img class="left framed" width="600" height="288" alt="" src="/sites/default/files/users/oracleug/AR_001_1_0.png" /><br /> Oracle Fusion Receivables provides most of the functionalities available in Oracle EBS 11i/R12. All the mandatory setups are also similiar to the setups available in 11i/R12.</p> <p>OFR allows you to perform most of your day-to-day accounts receivable operations. Receivables lets you manage customer billing activities, process customer payments, manage accounts receivable balances, and perform tasks that are related to revenue recognition and revenue adjustments.</p> </div> </div> </div> </section> <section class="clearfix block block-layout-builder"> </section> <section class="clearfix block block-layout-builder"> <section class="field field-node--comment-node-book field-name-comment-node-book field-type-comment field-label-hidden comment-wrapper"> </section> </section> </div> </div> Mon, 16 Apr 2012 11:18:54 +0000 Anonymous 2447 at http://oracleug.com http://oracleug.com/node/2447#comments Tree & Tree Structure http://oracleug.com/node/2437 <span class="field field-node--title field-name-title field-type-string field-label-hidden">Tree &amp; Tree Structure</span> <span class="field field-node--uid field-name-uid field-type-entity-reference field-label-hidden"><span>Anonymous (not verified)</span></span> <span class="field field-node--created field-name-created field-type-created field-label-hidden">Tue, 04/10/2012 - 13:24</span> <div class="layout layout--onecol"> <div class="layout__region layout__region--content"> <section class="clearfix block block-layout-builder"> <div class="clearfix field field-node--body field-name-body field-type-text-with-summary field-label-hidden"> <div class="field-items"> <div class="field-item"><p><img class="left framed" alt="" width="600" height="327" src="/sites/default/files/users/oracleug/fab_002_0.png" /> </p> <p><span style="color: #993300"><u><b>What is a tree?<br /></b></u></span>A tree is hierarchical structures that enable several data management functions such as better access control, application of business rules at various levels of hierarchies, improved query performance, and so on.</p> <p>This concept is similar to the organization hierarchy in 11i &amp; R12.<br /> For example, MI Corporation has two departments: Marketing and Finance.<br /> The Finance department has two functional divisions: Receivables and Payables.<br /> Defining a tree for the MI Corporation establishes a hierarchy between the organization and its departments, and between the departments and their respective functional divisions as shown in above pic.</p> <p><span style="color: #993300"><u><b>What is a tree Structure?<br /></b></u></span>A tree structure is configuration on the basis of which trees are created. It defines and restricts the tree. A tree is an instance of the hierarchy as defined in the tree structure. Tree structures enable you to enforce business rules to which the data must adhere.<br /> The root node is the topmost node of a tree. Child nodes report to the root node. Child nodes at the same level, which report to a common parent node, are called siblings. Leaves are details branching off from a node but not extending further down the tree hierarchy.</p> <p><span style="color: #993300"><b>Important Points<br /></b></span></p> <ul><li>You can associate multiple data sources with a tree structure.</li> <li>Every tree structure can contain one or more trees.</li> <li>You can create tree structures specific to an application but you can share tree structures across applications.</li> <li>If you apply version control to the tree structure, it is carried over to the trees that are based on the tree structure.</li> <li>Each tree version contains at least one root node. Occasionally, a tree version may have more than one root node.</li> <li>An administrator controls the access to tree structures through a set of rules that are periodically audited for validity.</li> </ul><p><span style="color: #993300"><u><b>What is a tree version<br /></b></u></span>A tree is created having only one version. However, users can create more than one tree version depending on the need, and they can make changes to those versions. Depending on varying requirements, users can create one or more tree versions and publish all of them or some of them by making the versions active at the same time. Similar to any other version control system, versions of trees are maintained to keep track of all the changes that a tree undergoes in its life cycle.</p> <p><span style="color: #993300"><u><b>What are tree labels<br /></b></u></span>Tree labels are short names associated with trees and tree structures and point directly to the data source. Tree labels are automatically assigned to the tree nodes. You can store labels in any table and register the label data source with the tree structure.</p> </div> </div> </div> </section> <section class="clearfix block block-layout-builder"> </section> <section class="clearfix block block-layout-builder"> <section class="field field-node--comment-node-book field-name-comment-node-book field-type-comment field-label-hidden comment-wrapper"> </section> </section> </div> </div> Tue, 10 Apr 2012 07:54:38 +0000 Anonymous 2437 at http://oracleug.com http://oracleug.com/node/2437#comments Reference Data Sharing http://oracleug.com/node/2434 <span class="field field-node--title field-name-title field-type-string field-label-hidden">Reference Data Sharing</span> <span class="field field-node--uid field-name-uid field-type-entity-reference field-label-hidden"><span>Anonymous (not verified)</span></span> <span class="field field-node--created field-name-created field-type-created field-label-hidden">Mon, 04/09/2012 - 19:46</span> <div class="layout layout--onecol"> <div class="layout__region layout__region--content"> <section class="clearfix block block-layout-builder"> <div class="clearfix field field-node--body field-name-body field-type-text-with-summary field-label-hidden"> <div class="field-items"> <div class="field-item"><p><img class="left framed" width="541" height="358" alt="" src="/sites/default/files/users/oracleug/fab_001.png" /><br /> In 11i/R12 there are many configuration data which ‘er shared across all the OUs. Ex: Payment term. It's good because you are required to define the data only once but the biggest disadvantage is that there is no method to restrict the access. In fusion application a new concept of data sharing is added, where you define reference data set(s) and determine how the data is shared or partitioned.</p> <p>Reference data sharing facilitates sharing of configuration data such as jobs and payment terms, across organizational divisions (another new organization concept in FA) or business units. Depending on the requirement (specific or common), each business unit can maintain its data at a central location, using a set of values either specific to it or shared by other business units.<br /> This new feature reduces duplication as well as provides the facility to restrict data as required.</p> <p>From Oracle Guide</p> <blockquote><p>Reference data sets are logical groups of reference data that can be accessed by various transactional entities depending on the business context. Oracle Fusion Applications contains a common reference data set as well as an enterprise set that may be used as a default set. Depending on your business requirement you can create and maintain additional reference data sets, while continuing to use the common reference data set.</p> </blockquote> <p>Ex: The senior management can decide to use a single AP payment method data set throughout the enterprise &amp; let business unit’s managers define their own payment formats.</p> <p><span style="color: #993300"><u><b>Partitioning<br /></b></u></span>The partitioning of reference data and creation of data sets enable you to create reference entities across tables or lookup types, and share modular information and data processing options among business units. With the help of partitioning, you can choose to create separate sets and subsets for each business unit depending upon its business requirement, or create common sets or subsets to enable sharing reference data between several business units, without the need for duplicating the reference data. Partitioning provides you the flexibility to handle the reference data in a way appropriate to your business needs.</p> <p>The figure illustrates the reference data sharing method (assignment to one set only, with common values) where the user can access the data assigned to a specific set in a particular business unit, as well as access the data assigned to the common set.<br />  </p> </div> </div> </div> </section> <section class="clearfix block block-layout-builder"> </section> <section class="clearfix block block-layout-builder"> <section class="field field-node--comment-node-book field-name-comment-node-book field-type-comment field-label-hidden comment-wrapper"> </section> </section> </div> </div> Mon, 09 Apr 2012 14:16:34 +0000 Anonymous 2434 at http://oracleug.com http://oracleug.com/node/2434#comments Supplier Capacity http://oracleug.com/node/2192 <span class="field field-node--title field-name-title field-type-string field-label-hidden">Supplier Capacity</span> <span class="field field-node--uid field-name-uid field-type-entity-reference field-label-hidden"><span>Anonymous (not verified)</span></span> <span class="field field-node--created field-name-created field-type-created field-label-hidden">Sun, 12/18/2011 - 01:29</span> <div class="layout layout--onecol"> <div class="layout__region layout__region--content"> <section class="clearfix block block-layout-builder"> <div class="clearfix field field-node--body field-name-body field-type-text-with-summary field-label-hidden"> <div class="field-items"> <div class="field-item"><p><img class="left framed" width="600" height="561" alt="" src="/sites/default/files/users/oracleug/ascp_101_0.png" /><br /> Traditional planning systems like MRP uses item attribute lead time offsets to align supply order due dates with demand dates of need. The ASL providers greater accuracy in making lead time offset calculations during the planning process. You can specify supplier &amp; item specific lead times. This ensures that your orders are placed early enough to provide the selected supplier adequate time to react to your demand for each item. </p> <!--break--><p>You can use delivery calendar to specify valid delivery dates for your supplier and item combinations. The calendar defines valid dates that an organization can receive an item from each supplier. This allows planning to adjust planned order release dates so that deliveries occur on valid delivery dates. </p> <p><span style="color: #993300"><u><b>Constraints</b></u></span><br /> Oracle ASCP considers the following supplier capacity constraints.<br /><img width="600" height="470" alt="" src="/sites/default/files/users/oracleug/ascp_102_0.png" /></p> <p><span style="color: #333300"><b>Allocation of Demand Based on Historical Allocations<br /></b></span>You can allocate planned orders to sources taking historical allocations into account. Planning uses history to determine the allocations necessary to achieve your targeted allocations.</p> <p><span style="color: #333300"><b>Allocate Planned Orders With Capacity Constraints<br /></b></span>You can specify the capacity of individual suppliers to supply specific items. You can allocate planned orders taking capacity constraints of the suppliers into account. Planning uses the ranking information you specify and first attempts to source the planned orders with the primary sources. If the primary source does not have the capacity to fulfill the demand, planning suggests sourcing with the alternative sources you have specified, in the priority you have specified</p> <p><span style="color: #333300"><b>Delivery/Reception Frequency Calendars<br /></b></span>You can specify the valid delivery dates for each of your suppliers or supplier/item combinations. The reception schedule defines the dates an organization is able to receive an item from each vendor. Planning adjusts planned orders so that deliveries are planned for valid dates.</p> <p><span style="color: #333300"><b>Supplier-Specific Order Modifiers</b></span><br /> You can specify supplier-specific order modifiers at an item/supplier site level. Planning respects the order modifier quantities defined for the sources of the item. This enables you to specify more precisely the conditions related to each source.</p> <p><span style="color: #333300"><b>Supplier-Specific Lead Times</b></span><br /> You can specify supplier-specific lead times for items. This ensures orders are placed early enough to provide the supplier time to react to your needs.</p> <p><span style="color: #993300"><i><b>Notes :<br /></b></i></span>1. The ASL entry needs to be global for ASCP to recognize it. The constraint tab is enabled only for global ASLs.  Global ASLs are applicable to all teh inv organizations in the OU.</p> <p><span style="color: #993300"><u><b>Purchase Order Consumption of Supplier Capacity<br /></b></u></span>The planning engine does not consume supplier capacity with purchase orders unless you specify. In general, purchase order deliveries that consume supplier capacity can result in unnecessary reschedule out exception messages. They have consumed supplier capacity in the past; since the planning engine does not track past supplier capacity, it sees not enough supplier capacity between the plan start date and the purchase order delivery dock date.<br /> You can configure purchase order consumption of supplier capacity in several ways depending on the amount of feedback that you receive from your suppliers:</p> <ol><li>Constrain new orders only</li> <li>Constrain new orders only, purchase order placed early</li> <li>Integrate with Oracle Collaborative Planning</li> </ol><p><span style="color: #993300"><b>Profile Options</b></span><br /> To configure purchase order consumption of supplier capacity, set the following profile options:</p> <p><span style="color: #333300"><b>MSC: Purchase Order Dock Date Calculation Preference:</b></span> Specifies the purchase order date that the planning engine uses as the Dock Date—the scheduled date of purchase order receipt. If you select Promise Date, the Dock Date is Promise Date. If you select Promise Date and the delivery has not been acknowledged (Promise Date is blank), Dock Date is Need By Date. If you select Need By Date, Dock Date is Need By Date.<br /> It also specifies whether purchase orders without promise dates consume supplier capacity. If you select Promise Date, the planning engine consumes supplier capacity with purchase order deliveries that have not been acknowledged (Promise Date is blank). If you select Need By Date, it does not. </p> <p><span style="color: #333300"><b> MSC: Supplier Capacity Accumulation (multiplier):</b></span> Specifies the date that the planning engine begins supplier capacity accumulation. You enter it as a multiplier of the Approved Supplier List Processing Lead Time.<br /> To begin accumulation at the Approved Supplier List Processing Lead Time, enter 1 (the default). To begin accumulation at the plan start date, enter 0. To begin accumulation at a multiple of the Approved Supplier List Processing Lead Time, enter another whole number.<br />  </p> </div> </div> </div> </section> <section class="clearfix block block-layout-builder"> </section> <section class="clearfix block block-layout-builder"> <section class="field field-node--comment-node-book field-name-comment-node-book field-type-comment field-label-hidden comment-wrapper"> </section> </section> </div> </div> Sat, 17 Dec 2011 19:59:21 +0000 Anonymous 2192 at http://oracleug.com http://oracleug.com/node/2192#comments Methods of Invoicing http://oracleug.com/node/2180 <span class="field field-node--title field-name-title field-type-string field-label-hidden">Methods of Invoicing</span> <span class="field field-node--uid field-name-uid field-type-entity-reference field-label-hidden"><span>Anonymous (not verified)</span></span> <span class="field field-node--created field-name-created field-type-created field-label-hidden">Sat, 12/10/2011 - 02:55</span> <div class="layout layout--onecol"> <div class="layout__region layout__region--content"> <section class="clearfix block block-layout-builder"> <div class="clearfix field field-node--body field-name-body field-type-text-with-summary field-label-hidden"> <div class="field-items"> <div class="field-item"><p> <img class="left framed" width="600" height="319" alt="" src="/sites/default/files/users/oracleug/pa007_0.png" /><br /> You specify the invoicing method based on the distribution rule that you select for the contract<br /> project. Oracle Projects supports three methods of invoicing:</p> <p><span style="color: #993300"><b>As-work-occurs<br /></b></span>• Based on bill rates or markups applied to detail transactions:<br /> - Time and Materials (T&amp;M) when using bill rates, or<br /> - Cost plus when using burden schedules</p> <p><span style="color: #993300"><b>Cost-to-cost<br /></b></span>• Based on the ratio of the actual costs to budgeted costs and revenue (referred to as percent spent)<br /> Event-based<br /> • Based on the Oracle Projects client extensions calculations or direct user input from externally calculated amounts; for example:<br /> - Automated milestone creation<br /> - Percent progress complete calculations</p> <p><span style="color: #993300"><b>Percent Complete<br /></b></span>You can enter the percent complete for a project or task. Percent completion information is used for<br /> revenue accrual and billing, and for reporting purposes. Oracle Projects does not calculate project<br /> or task percent completion, but uses the percent complete amounts that you enter.</p> <p>Each percent complete has an As Of Date. When you use percent complete as the basis for generation of draft invoices, the As Of Date is used to determine the current percent complete.<br /> You can enter the percent complete values manually or interface them from the project management system.</p> <p><span style="color: #993300"><b>Processing Percent Complete Invoice<br /></b></span>To calculate the physical percent complete invoice, you submit the PRC: Generate Draft Invoices process. To submit the process for only one project, submit PRC: Generate Draft Invoice for a Single Project. The invoice process performs the following steps:</p> <p>1. The process calls the billing extension for each project or top task (depending on whether<br /> the project is funded at the project or top task level). The calling procedure specifies<br /> whether it is an invoice calling process and whether the call is made at the project or task<br /> level.</p> <p>2. The billing extension determines the budget amounts, event amount, existing revenue mounts, funding balance, and percent complete.</p> <p>3. If the percent complete cannot be determined, then the percent complete used by the<br /> process is zero, the draft invoice amount is zero, and no event is created.</p> <p>4. The following formulas show how the process calculates the draft invoice amount:<br /> Accrued Revenue = The lesser of A or B<br /> A = Remaining funding balance if agreement has a hard limit<br /> B = ((Budgeted Revenue - Event Revenue) * Percent Complete at Funding Level/100)<br /> - Existing Revenue<br /> Event Revenue = Total event revenue accrued other than revenue amount accrued by<br /> percent complete events<br /> Existing Revenue = Total revenue accrued previously by percent complete events</p> <p>5. The billing extension creates an event. The description of the event includes the event<br /> type and the formula that was used to calculate the draft invoice amount</p> </div> </div> </div> </section> <section class="clearfix block block-layout-builder"> </section> <section class="clearfix block block-layout-builder"> <section class="field field-node--comment-node-book field-name-comment-node-book field-type-comment field-label-hidden comment-wrapper"> </section> </section> </div> </div> Fri, 09 Dec 2011 21:25:51 +0000 Anonymous 2180 at http://oracleug.com http://oracleug.com/node/2180#comments Invoicing http://oracleug.com/node/2178 <span class="field field-node--title field-name-title field-type-string field-label-hidden">Invoicing</span> <span class="field field-node--uid field-name-uid field-type-entity-reference field-label-hidden"><span>Anonymous (not verified)</span></span> <span class="field field-node--created field-name-created field-type-created field-label-hidden">Tue, 12/06/2011 - 21:32</span> <div class="layout layout--onecol"> <div class="layout__region layout__region--content"> <section class="clearfix block block-layout-builder"> <div class="clearfix field field-node--body field-name-body field-type-text-with-summary field-label-hidden"> <div class="field-items"> <div class="field-item"><p> <img class="left framed" height="303" width="600" alt="" src="/sites/default/files/users/oracleug/pc003_1.png" /><br /> Using Oracle Projects features, you can manage and control your invoices, review and adjust them online, and review the detailed information that backs up your invoice amounts. When you generate invoices, Oracle Projects calculates bill amounts, creates formatted invoices for printing and posting, and maintains funding balances</p> <!--break--><p> Oracle Projects provides controls as to which projects are ready for invoice generation.<br /> You must complete the following steps before generating invoices for a contract project in Oracle Projects:</p> <p>1. Enter an agreement and fund the project, using the Enter Agreements window. </p> <p>2. If you want to generate revenue or invoices for the project based on percent complete, enter percent complete information either at the project or the funding level (project or top task). </p> <p>3. If you want the project customer to be billed in a currency other than the project functional currency, enter currency attributes for the project customer.<br /> Note: To enter currency attributes, you must enable the multi–currency billing functionality.</p> <p>4. If you are using multi–currency billing, enter project level currency conversion attributes.</p> <p>5. Enter budgets.<br /> Note: If your project uses the cost–to–cost invoice generation method, you must include burdened costs in your cost budget and revenue amounts in your revenue budget. Without these<br /> amounts, Oracle Projects cannot successfully generate invoices for your project.</p> <p>6. <span style="color: #3366ff">Baseline </span>the project budget and funding. <br /> Note: You must fund the budget before you can baseline it.</p> <p>7. For projects using as–work–occurs billing, <span style="color: #3366ff">generate revenue for expenditure items using the Generate Draft Revenue process.</span></p> <p>8. For projects using event billing, enter billing events using the<span style="color: #3366ff"> Event option in the Project or Task window.<br /></span>Note: If you do not want to generate an invoice for a specific top task on your project, uncheck the Ready to Bill check box in the Control Billing by Top Task window. Oracle Projects<br /> assumes you want to invoice all billable top tasks on contract projects.<br />  <br /><span style="color: #993300"><b>Hard Limit Processing for Invoices<br /></b></span>In Oracle Projects, an invoice is created with all items and events that can be fully billed with<br /> available funding under the hard limit.<br /> • Any items and events that would cause the limit to be exceeded remain unbilled.<br /> • Bill amounts for items are not prorated.</p> <p>A hard limit prevents invoice generation beyond the amount allocated to a project or task by an<br /> agreement.<br /> For projects funded by hard limit agreements, the total invoiced amount cannot exceed the total<br /> funded amount.  A hard limit prevents invoice generation beyond the amount allocated to a project or task by this agreement</p> <p><span style="color: #993300"><b>Bill Through Date</b></span> The date through which Oracle Projects picks up events and expenditure items to be billed on an invoice.</p> <p><span style="color: #993300"><b>Salesperson</b></span> If you define project managers as salespeople, then this is the project manager of the<br /> invoice’s project. If you do not define project managers as salespeople, this value is blank</p> <p><span style="color: #993300"><b>Invoice Transaction Type</b></span> If you choose decentralized invoice processing during implementation, this is the name of the organization that is the invoice processing organization for the project<br /> owning organization. Otherwise, this is the default transaction type of Projects Invoice or Projects Credit Memo based on the PROJECTS INVOICES batch source. You can override the transaction type of an invoice using the transaction type billing extension.</p> <p>You can also use the AR transaction type extension to determine the AR transaction type when you interface invoices to Oracle Receivables.<br /> An invoice transaction type determines if it is an invoice or a credit memo.</p> <p><span style="color: #993300"><b>Invoice Number (AR)</b></span> The number of an invoice that is printed on an invoice, and the number that can be tracked in Oracle Receivables. This number can be system generated, or a number that you<br /> enter which uniquely identifies the invoice in Oracle Receivables, depending on how you<br /> implemented your invoice numbering system in Oracle Projects. The invoice number is<br /> determined when you release an invoice.</p> </div> </div> </div> </section> <section class="clearfix block block-layout-builder"> </section> <section class="clearfix block block-layout-builder"> <section class="field field-node--comment-node-book field-name-comment-node-book field-type-comment field-label-hidden comment-wrapper"> </section> </section> </div> </div> Tue, 06 Dec 2011 16:02:19 +0000 Anonymous 2178 at http://oracleug.com http://oracleug.com/node/2178#comments