Capacity SetupSubmitted by Anonymous on Wed, 04/18/2012 - 17:37 Tag:

Oracle Capacity

/

Make sure you set up oracle Inventory, BOM, MRP/ASCP correctly before starting the setups for Oracle Capacity.The steps shown in the above pic are the set up steps just for the Capacity product. All these setup steps are optional.

Resource Group

Resource groups are used to group key/critical/similar resources. 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.

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.

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 

ForecastingSubmitted by Anonymous on Fri, 02/20/2009 - 12:11

Tag:

Master Scheduling/MRP

/

You can estimate future demand for items using any combination of historical, statistical, and intuitive forecasting techniques. You can create multiple forecasts and group complimenting forecasts into forecast sets.

Forecasts are done in inventory organization level. Forecasts are consumed each time your customers place sales order demand for a

forecasted product. You can load forecasts, together with sales orders, into master demand and production

schedules, and use the master schedules to drive material requirements planning.

Forecast SetBefore you define a forecast, you first define a set. Forecast sets: • Group complimenting forecasts that sum together to a meaningful whole• Group forecasts that represent different scenarios

Forecast Set ExamplesForecasts by RegionYou have three forecasts named FCA, FCB, and FCC within a forecast set. Salesperson A, responsible for the Eastern region, maintains FCA. Salesperson B maintains FCB for the Midwest. Salesperson C maintains FCC for the Western region. In this situation, FCA, FCB, and FCC each represent a part of the whole forecast. Together, their sum represents the total forecast.Forecast ScenariosYou have three forecast sets named SETA, SETB, and SETC. These forecast sets  represent different scenarios. SETA is the forecast for the bestcase scenario year of sales, while SETB is the planned scenario year of sales. SETC shows the worst-case scenario year of sales. You may want to maintain all three forecast sets simultaneously, so you can compare and contrast the effect each has on your material plan.

Define a forecast set

 

1. Enter a unique name.

2. Select a bucket type to group forecast entries by days, weeks, or accounting periods.

3. Select the level that determines how forecasts in the set are defined and consumed.In addition to designating the minimum level of detail for which the forecast is defined, the forecast level also serves as a consumption level. You can define the forecast level with or without the demand class that also controls the consumption of forecasts. You can define the following consumption levels for a forecast set:

Ship - To: Item, customer, and shipping identifier Bill - To: Item, customer, and billing identifier Customer: Item and customer ; When you define a forecast for the forecast set with level

at customer, you need to mention the customer Name in the forecast and consumption 'll happen only when a SO is created for the customer item cumbination.

Item: This is the only option available if you are not using Oracle Order Management or Oracle Receivables.

While attempting to consume a forecast, the consumption process looks for a forecast containing an item that corresponds to the sales order information. When it finds an entry, it checks the forecast using the criteria you defined for the forecast level. For example, if you define the forecast level to be ship to, the forecast consumption process searches the forecasts for the customer/ship–to address associated with the sales order.

4. Select consumption options.If you turn consumption on, sales orders you create consume forecast entries in this set. The outlier update is the maximum percentage of a forecast entry that a single sales order can consume.Forward and backward days describe the number of work dates from the sales order schedule date that forecast consumption looks backward or forward for a forecast entry to consume. Non - workdays are not counted in these calculations.

Forecast

Defining a Forecast

A forecast shows predicted future demand for items over time.You can assign any number of items to a forecast, and use the same item in multiple forecasts. For each item you enter the days, weeks, or periods and the quantities that you expect to ship.A forecast entry with a forecast end date specifies the same quantity scheduled for each day, week, or period until the forecast end date. A forecast entry without a forecast end date is valid only for the date and time bucket specified.

Defining Forecast DetailsYou can also review and update forecast information in the Items Forecast Entries window. This window displays the same information as the Forecast Entries window – with the difference that it contains a listing of the all the items in a forecast set. From here you can access bucketed and consumption details.

When you create a SO for a forecasted item consumption happens when you book the sales order and current quantity in forecast detail form is reduced by the sales order line quantity.

If you create a forecast after entering the sales order then click on the consume button on forecast set to run the concurrent program Consume Forecast Set which 'll check the forecast and existing sales order dates and initiate the consumption process.

The consumption information can be seen in consumptions form.

 

More on consumptionSubmitted by Anonymous on Fri, 02/20/2009 - 22:58 Tag:

Master Scheduling/MRP

/

Consumption with Daily Buckets

Consumption with Weekly Buckets

Consuming New ForecastsAutomatic forecast consumption, as controlled by the Planning Manager, consumes existing forecasts with each sales order created. New forecasts you create are consumed only by the sales orders created after forecast creation. You can, however, apply sales orders already consumed by other forecasts to the new one.

Outlier Update PercentThis controls the effects of abnormal demand with a maximum percent of the original quantity forecast that a single sales order can consume.ExampleYou have several customers. Each typically orders 100 units in a given period. One of the customers is having a special promotion that could increase demand significantly. Use the outlier update percentage to ensure that these "one time" sales orders do not overconsume the forecast. Select a number of sales orders within the demand time fence to include. Including only sales orders from today forward is useful if your forecast begins today, and/or if the forecast begins on the first day of a period, rather than in the middle of a period.

In the above example, daily forecast exists for 20 on the 2nd and the 9th with an outlier update percent of 50 on each forecast. When you place sales order demand for 50 on the 9th, the forecast consumption process attempts to consume on the sales order line schedule date only, since the forecast is stated in daily buckets and no backward consumption days exist. Because an outlier update percent of 50 exists on the forecast, the consumption process consumes only 50% of the forecast. The outlier update percent applies to how much of the original forecast quantity, not the sales order, theconsumption process can consume. In this example, the consumption process consumes 50% of the forecast(10) and the rest of the sales order quantity (40) is overconsumed. If there were a backward consumption days of 5, 50% of the forecast on the 2nd would also be consumed, and the overconsumed quantity would be 30. Using the same example, if another sales order for 50 is placed on the 9th, it consumes 50% of the original forecast quantity (10) and the current forecast quantity on the 9th becomes zero. Overconsumption is increased by an additional 40 to a new total on the 9th (80).

 

InvoicingSubmitted by Anonymous on Tue, 12/06/2011 - 21:32 Tag:

Project Billing

/

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

Oracle Projects provides controls as to which projects are ready for invoice generation.You must complete the following steps before generating invoices for a contract project in Oracle Projects:

1. Enter an agreement and fund the project, using the Enter Agreements window.

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).

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.Note: To enter currency attributes, you must enable the multi–currency billing functionality.

4. If you are using multi–currency billing, enter project level currency conversion attributes.

5. Enter budgets.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 theseamounts, Oracle Projects cannot successfully generate invoices for your project.

6. Baseline the project budget and funding. Note: You must fund the budget before you can baseline it.

7. For projects using as–work–occurs billing, generate revenue for expenditure items using the Generate Draft Revenue process.

8. For projects using event billing, enter billing events using the Event option in the Project or Task window.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 Projectsassumes you want to invoice all billable top tasks on contract projects. Hard Limit Processing for InvoicesIn Oracle Projects, an invoice is created with all items and events that can be fully billed withavailable funding under the hard limit.• Any items and events that would cause the limit to be exceeded remain unbilled.• Bill amounts for items are not prorated.

A hard limit prevents invoice generation beyond the amount allocated to a project or task by anagreement.For projects funded by hard limit agreements, the total invoiced amount cannot exceed the totalfunded amount.  A hard limit prevents invoice generation beyond the amount allocated to a project or task by this agreement

Bill Through Date The date through which Oracle Projects picks up events and expenditure items to be billed on an invoice.

Salesperson If you define project managers as salespeople, then this is the project manager of theinvoice’s project. If you do not define project managers as salespeople, this value is blank

Invoice Transaction Type If you choose decentralized invoice processing during implementation, this is the name of the organization that is the invoice processing organization for the projectowning 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.

You can also use the AR transaction type extension to determine the AR transaction type when you interface invoices to Oracle Receivables.An invoice transaction type determines if it is an invoice or a credit memo.

Invoice Number (AR) 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 youenter which uniquely identifies the invoice in Oracle Receivables, depending on how youimplemented your invoice numbering system in Oracle Projects. The invoice number isdetermined when you release an invoice.

Methods of Invoicing

Submitted by Anonymous on Sat, 12/10/2011 - 02:55 Tag:

Project Billing

/

You specify the invoicing method based on the distribution rule that you select for the contractproject. Oracle Projects supports three methods of invoicing:

As-work-occurs• Based on bill rates or markups applied to detail transactions:- Time and Materials (T&M) when using bill rates, or- Cost plus when using burden schedules

Cost-to-cost• Based on the ratio of the actual costs to budgeted costs and revenue (referred to as percent spent)Event-based• Based on the Oracle Projects client extensions calculations or direct user input from externally calculated amounts; for example:- Automated milestone creation- Percent progress complete calculations

Percent CompleteYou can enter the percent complete for a project or task. Percent completion information is used forrevenue accrual and billing, and for reporting purposes. Oracle Projects does not calculate

projector task percent completion, but uses the percent complete amounts that you enter.

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.You can enter the percent complete values manually or interface them from the project management system.

Processing Percent Complete InvoiceTo 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:

1. The process calls the billing extension for each project or top task (depending on whetherthe project is funded at the project or top task level). The calling procedure specifieswhether it is an invoice calling process and whether the call is made at the project or tasklevel.

2. The billing extension determines the budget amounts, event amount, existing revenue mounts, funding balance, and percent complete.

3. If the percent complete cannot be determined, then the percent complete used by theprocess is zero, the draft invoice amount is zero, and no event is created.

4. The following formulas show how the process calculates the draft invoice amount:Accrued Revenue = The lesser of A or BA = Remaining funding balance if agreement has a hard limitB = ((Budgeted Revenue - Event Revenue) * Percent Complete at Funding Level/100)- Existing RevenueEvent Revenue = Total event revenue accrued other than revenue amount accrued bypercent complete eventsExisting Revenue = Total revenue accrued previously by percent complete events

5. The billing extension creates an event. The description of the event includes the eventtype and the formula that was used to calculate the draft invoice amount

Supplier CapacitySubmitted by Anonymous on Sun, 12/18/2011 - 01:29 Tag:

ASCP

/

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 & 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.

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.

ConstraintsOracle ASCP considers the following supplier capacity constraints.

Allocation of Demand Based on Historical AllocationsYou can allocate planned orders to sources taking historical allocations into account. Planning uses history to determine the allocations necessary to achieve your targeted allocations.

Allocate Planned Orders With Capacity ConstraintsYou 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

Delivery/Reception Frequency CalendarsYou 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.

Supplier-Specific Order ModifiersYou 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.

Supplier-Specific Lead TimesYou 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.

Notes :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.

Purchase Order Consumption of Supplier CapacityThe 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.You can configure purchase order consumption of supplier capacity in several ways depending on the amount of feedback that you receive from your suppliers:

1. Constrain new orders only2. Constrain new orders only, purchase order placed early3. Integrate with Oracle Collaborative Planning

Profile OptionsTo configure purchase order consumption of supplier capacity, set the following profile options:

MSC: Purchase Order Dock Date Calculation Preference: 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.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. 

MSC: Supplier Capacity Accumulation (multiplier): 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.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.

Methods of InvoicingSubmitted by Anonymous on Sat, 12/10/2011 - 02:55 Tag:

Project Billing

/

You specify the invoicing method based on the distribution rule that you select for the contractproject. Oracle Projects supports three methods of invoicing:

As-work-occurs• Based on bill rates or markups applied to detail transactions:- Time and Materials (T&M) when using bill rates, or- Cost plus when using burden schedules

Cost-to-cost• Based on the ratio of the actual costs to budgeted costs and revenue (referred to as percent spent)Event-based• Based on the Oracle Projects client extensions calculations or direct user input from externally calculated amounts; for example:- Automated milestone creation- Percent progress complete calculations

Percent CompleteYou can enter the percent complete for a project or task. Percent completion information is used

forrevenue accrual and billing, and for reporting purposes. Oracle Projects does not calculate projector task percent completion, but uses the percent complete amounts that you enter.

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.You can enter the percent complete values manually or interface them from the project management system.

Processing Percent Complete InvoiceTo 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:

1. The process calls the billing extension for each project or top task (depending on whetherthe project is funded at the project or top task level). The calling procedure specifieswhether it is an invoice calling process and whether the call is made at the project or tasklevel.

2. The billing extension determines the budget amounts, event amount, existing revenue mounts, funding balance, and percent complete.

3. If the percent complete cannot be determined, then the percent complete used by theprocess is zero, the draft invoice amount is zero, and no event is created.

4. The following formulas show how the process calculates the draft invoice amount:Accrued Revenue = The lesser of A or BA = Remaining funding balance if agreement has a hard limitB = ((Budgeted Revenue - Event Revenue) * Percent Complete at Funding Level/100)- Existing RevenueEvent Revenue = Total event revenue accrued other than revenue amount accrued bypercent complete eventsExisting Revenue = Total revenue accrued previously by percent complete events

5. The billing extension creates an event. The description of the event includes the eventtype and the formula that was used to calculate the draft invoice amount

Setup Steps for the Source & DestinationSubmitted by Anonymous on Mon, 11/08/2010 - 14:06 Tag:

ASCP

/

Setup Steps for the Source

1. Install the source instance patchBefore beginning the functional setup of the source instance(s), a patch must be applied that will create several new concurrent programs, flexfields, profile options, and database objects on the source database. The patch that is required is determined by the versions of the application and database on the source instance.When successfully applied, the patch should create the Create Planning Flexfields, Create Global ATP Flexfields, and Refresh Snapshot programs under the All SCP Reports Request group.

2. Create a database link pointing to the planning server.Note: Before beginning the installation of the source patch, count all (if any) invalid database objects. If after the patch is installed there are more invalid objects than before, there was a problem with the patch application.

A database link must be established on the source instance that points to the destination (planning) instance. This database link will be referenced in a newly created profile option, MRP: ATP Database Link.

3. Create an Advanced Supply Chain Planner responsibility. You must create a responsibility in the source instance with the name 'Advanced Supply Chain Planner'. The responsibility name must match Advanced Supply Chain Planner exactly. During the data collection process which runs on the destination server, the Refresh Snapshot program is launched automatically in the source from this responsibility. The refresh snapshot process will not complete properly if the responsibility name is not correct.

The Create Planning Flexfields concurrent program creates new segment definitions in existing descriptive flexfields to hold data that may be required for constrained and/or optimized planning. The program also populates profile values with the value corresponding to the descriptive flexfield attribute number for each attribute (planning parameter) created.

4. Launch the Create Planning Flexfields report from the newly created Advanced Supply Chain Planner responsibility. The parameters that must be set for the report are the attributes that you wish to utilize for the new flexfield definitions. The list of values for each parameter lists only the available attributes in the subject descriptive flexfield.

After submitting the program, eleven additional processes should be spawned. These jobs are compiling the descriptive flexfield views. Check that the profile values corresponding to each flexfield attribute were populated with the correct attribute number. Some profile values may retain the value of unassigned after the Create Planning Flexfield program completed. You must change any unassigned profiles to the attribute number corresponding to the flexfield attribute where the new segment was defined.

5. Create the Global Order Promising flexfields.The Create Global ATP Flexfields is very similar to the Create Planning Flexfields program. It creates new flexfield segments to hold global ATP data at the item, BOM, routing, and resource levels. The same process, including warnings and suggestions, applies for the Create Global ATP Flexfield program.

6. Set up source data with BOMs, resources, routings, supplier data, flexfields, purchasing information, item masters, Oracle BIS targets, and any other data required by your plans.

7. Set profile values.If Global Order Promising is going to be utilized, the following two additional profile options must be set.The MRP: ATP Database Link profile option must be set with the database link. The profile value is the name of the database link that resides on the source and points to the destination. There is no validation on this profile value. If Global Order Promising is not utilized, this need not be set.The INV: External ATP profile must be set to Global ATP. This is a choice from the list of values. If Global ATP is not utilized, this need not be set.

8. Execute the Refresh Snapshot concurrent program.The Refresh Snapshot process must be run on the source. This concurrent program is available in the Advanced Supply Chain Planner responsibility created earlier. The process has no parameters to be set at run time. Verify that the process completes without error.

Setup Steps for the Destination

1. Install the destination instance patches.

2. Create a database link pointing to each source. These links will be needed when defining instances later on in this setup procedure.

3. Define the source instances to be collected from.The define instances setup establishes the means of communication between the source and destination instances. It also specifies the organizations in the source database for which data will be pulled.

4. From the Navigator, choose Setup > Instances. Do not access this form while the collections process is running; it locks a table that the collections process needs to complete successfully. The Application Instances window appears.

Enter each of the Application instances for which you would like the Planning Server to plan.

Complete the fields and flags in the Application Instances window as shown in the table below.

Enter the organizations on each of the instances from which to collect the Planning data and plan for on the Planning Server by clicking Organizations.The Organizations window appears.

Select the organizations for a particular instance. Be sure to select the master organization

Supplier CapacitySubmitted by Anonymous on Sun, 12/18/2011 - 01:29 Tag:

ASCP

/

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 & 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.

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.

ConstraintsOracle ASCP considers the following supplier capacity constraints.

Allocation of Demand Based on Historical AllocationsYou can allocate planned orders to sources taking historical allocations into account. Planning uses history to determine the allocations necessary to achieve your targeted allocations.

Allocate Planned Orders With Capacity ConstraintsYou 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

Delivery/Reception Frequency CalendarsYou 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.

Supplier-Specific Order ModifiersYou 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.

Supplier-Specific Lead TimesYou 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.

Notes :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.

Purchase Order Consumption of Supplier CapacityThe 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.You can configure purchase order consumption of supplier capacity in several ways depending on the amount of feedback that you receive from your suppliers:

1. Constrain new orders only2. Constrain new orders only, purchase order placed early3. Integrate with Oracle Collaborative Planning

Profile OptionsTo configure purchase order consumption of supplier capacity, set the following profile options:

MSC: Purchase Order Dock Date Calculation Preference: 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.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. 

MSC: Supplier Capacity Accumulation (multiplier): 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.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

TransactionsSubmitted by Anonymous on Mon, 04/16/2012 - 17:15 Tag:

Account Receivables

/

Similar to 11i & R12, You can create below transactions in fusion receivables• Invoices and Debit Memos• Credit Memos• On-Account Credit Memos• Chargebacks• Adjustments

All the new fields in fusion application transaction form are outlined in the above pic.

Business unit: Similar to operating unit in 11/R12Accounting Date: GL date in 11iAttachment Note

Question : Where is the legal entity information ?

Click on more and navigate to miscellaneous tab to verify the other details 

 The RA_CUSTOMER_TRX 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.

The RA_CUSTOMER_TRX_LINES 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.

The AR_PAYMENT_SCHEDULES 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