Hide Process Table in Oracle Screen

Please follow this way to safely hidden the processes table.
(Have to do this responsibility by responsibility)

Example for Payable

1) Navigate to Sysadmin> Security> Responsibility> Define

2) Query the responsibility that has the processes tab which is to be

removed.

3) In the lower part of the Responsibilities form you will see 3 tabs :

>> Menu exclusions

>> Excluded Items and

>> Securing attributes.

4) Select the Menu Exclusions Tab and in the type field select Function
--Note: the processes tab is actually a function of the type "process"
5) In the name field select the processes you want to be excluded from this

responsibility.

After put all of three list , the "PROCESSES" table will be removed from

Payable Navigator.

Type Name Description
Function 1099 Reporting Process Navigator Definition for 1099

Reporting Process
Function Procure to Pay Process Navigator Definition for Procure to

Pay Process
Function Close Payables Accounting Period Process Navigator

Definition for Close Payables accounting Period Process

The all of pages under this PROCESSES TAB is only the procedure guide which

is created by Oracle, this is only reference document (just like user

guide) and without any impact for current actual procedure in system.

That means, If we hidden PROCESSES TAB, end-user can not see this PROCESSES

TAB page and no any impact for other daily / monthly business, like month-

end closing / transaction booking etc.

10. Save changes 

Sub Ledger Accounting Oracle

Subledger Accounting (SLA) plays a central role in standardizing and implementing accounting policies, leveraging the R12 ledger architecture and legal entity enhancements.

As organizations continue to evolve, merge, acquire and divest, having ERP Applications that can easily and quickly adapt to structure changes is essential to their needs.

The R12 architecture ensures that legal compliance issues are isolated at the Legal Entity level, and the operation and security issues can be setup at the Operating Unit level. This, along with Multiple Organizations Access Control (MOAC), enables multiple legal entities and multiple lines of business—operating as a single operating unit with a single subledger and place—to implement standard processes and policies.

SLA is the repository of policies that control the accounting convention (one of the 4C`s) that’s tied to a ledger and ensures reconciliation of all the journals before they hit the ledger balances.

SLA features ease the pain of implementing accounting policies by taking away the need for customizations with certain setups (e.g. multiple liability accounts for different supplier types, matching entries for cost recognition and revenue within a single legal entity, multiple ledgers for regional reporting needs, etc.).

These are the SLA components that enable policy implementations:

Journal Line Type (JLT):

Defined for particular event class such as Accounting of an Invoice, JLT controls basic attributes of a journal line—balance types, the side, etc.—that determine the nature and treatment of that journal line.

Seeded JLTs may need extensions for implementing accounting policies. JLTs are defined for a seeded list of events, restricting them to modules within EBS. A separate, licensable product, Financials Accounting Hub (FAH), leverages the same structure but allows a definition of events to import accounting information from third-party applications.

Journal Entry Descriptions (JED):

JEDs determine the description of a journal line. We can add more information to a seeded journal line so that journal-based reports have richer information and ease reconciliation and other processes. Using the conditions and priorities, JEDs can carry attributes or different descriptions for the same journal entry.

Note: It’s best practice to leave one as default that uses a seeded description if none of the conditions are met.

Mapping Sets:

Similar to lookups and lookup sets, mapping sets store mapping of a transaction attribute to accounting segment values/flex field. The mapping sets are Key elements when we are mapping a particular segment (i.e. natural account to multiple supplier types.)

Account Derivation Rules (ADR):

ADRs are the rules which help implement accounting policies. They link source values in order to fetch target values. Setting up the extensions to Seeded SLA involves creating custom sources and using mapping sets to map them to target segment values.

Oracle provides a list of seeded sources which can be leveraged (using PLSQL code) to derive custom sources or be mapped to segment values using mapping in the account derivation rules.

It’s good practice to refer to the definition of the sources (sources are extracted in seeded views by Oracle and may have a different meaning than what its name might indicate).XLA_EVENT_SOURCES and XLA_AAD_SOURCES are the tables to use for identifying the view and the exact column name for your source. (To see it in the tables, you must assign a source on some ADR under AAD).

Journal Line Definition (JLD):

JLD brings all the elements together. It ties the JLT, descriptions and accounting rules to an event class. Any extensions done to SLA involves creating a custom JLD, copying the seeded one, and laying the changes on top.

Application Accounting Definition (AAD):

The AAD is a collection of JLD for a Module. SLA patches bring over new versions of these AADs (implemented as packages). Thus, the best practice is to copy over the seeded ones and make extensions on them. This means that, each time Oracle enhances the AAD, you need to analyze any subsequent patches to ensure the extensions are overlaid on a new copy. 

Sub ledger Accounting Method (SLAM):

The SLAM is collection of all the modules combined. It links the AAD collectively to a ledger.

For a detailed guide on how to implement SLA for your organization, refer to the Oracle Sub – Ledger Accounting Implementation Guide.

Difference in MRP and ASCP Oracle

The main difference between Material Requirement Planning and ASCP is that MRP doesn’t look at the constraints (material or resource) when planning the material supply. It assumes infinite capacity and plans the supply on the same day as the shipment date of the assembly. To prepare an achievable production schedule, planners have to do Capacity Requirement Planning (CRP). CRP presents the load chart of the machines including available hours and required hours, but the production schedule is still far from complete. So now a third tool is required to realign the planned production jobs on each machine and finally come up with an achievable production schedule.

The challenge does not end here. Although we have an achievable production schedule, but is it going to be cost effective? Are we building the product in the right sequence so we do not have to carry excess inventory? Are we minimizing the change-overs? Do we have means to decide which supplier to source the material from so as to have least impact on the production/shipping schedule still keeping the cost low? How do I tell MRP that every vendor has a different work schedule and our calendar does not match with theirs? The list goes on. MRP does not have answers to these questions.

ASCP comes with answers to all the above questions and more. Sounds too good to be true. So the clients begin lining up to buy the product. They invite consulting firms to implement the product and wait for the grand returns. Since they are eager to get the results, they implement ASCP with its functionality enabled, enforce capacity constraints (ECC), Optimization turned on, vendor constraints enabled, dynamic safety stock calculation, and automatic release of supply orders from the planning workbench, online planner and so on.

Oracle GOP Functionality

REQUIREMENTS

1. Why is the Expected Available Quantity set to 10 even though the

availability cannot be met for the requested date ?
2. How is the Expected Arrival Date calculated ?

SOLUTION

1. The Expected Available Quantity is not related to how much is available

on the requested date. There is no field in Order Promising that shows you

the quantity available on the requested date.

2. To check if there is Available Quantity on the requested date you should

compare the Expected Date and Requested Date to infer that there is no

quantity available on the Requested Date. I.e if these dates do not match

this implies there is no availability on the requested date.

3. The Expected Availability On Requested Date is a redundant field and GOP

does not have logic currently to derive the value in this field (RUP1 --

January 2012).

In the Examples provided The ATP Rule is not Lead Time based, it is a

regular ATP rule but with a Infinite time fence corresponding to the Total

Lead Time. The results are correct, and as expected for the Supply Chain

Search enabled ATP mode with an Infinite Time Fence.

TEST CASE 1.

1. Why is the Expected Available Quantity set to 10 even though the

availability cannot be met for the requested date ?

The Expected Available Quantity is not related to how much is available on

the requested date. It just shows the quantity of the promise, and this is

showing up as 10 since the requested quantity is 10. There is no field in

OP that shows you the quantity available on the requested date.

2. How is the Expected Arrival Date calculated ?

First the ship date is calculated. Since no supply is found until the

Infinite Time Fence, which is on 14-Dec (based on sysdate + Total Lead

Time) the Expected Ship Date is set to 14-Dec. Expected Arrival Date =

Expected Ship Date + Lead time (since no transfer lead times seem to be

setup) which is again 14-Dec.
TEST CASE 2.

3. How is the Expected Arrival Date calculated --- The date was calculated as

request date + lead time. Should the Arrival date be calculated as being

the same as the requested date if the lead time can be met ?

This is not 'Lead time based' promising mode. In this scenario, the request

date is beyond the Infinite time fence. Hence, availability is assumed to

be infinite on this date, and the Ship and Arrival Dates equal the

requested date.



Org has 5 day shipping calendar. (Monday to Friday are working days,

Saturday and Sunday are non shipping days).
Customer has requested to ship the materials on Sunday (20th Nov-2011).
Received order 8-Nov-2011 and Item lead time is 3 days.

System will suggest schedule ship date = 18th Nov 2011
(this is less than the non shipping day the customer requested)


SOLUTION

GOP uses calendar days(7 days) for lead time calculations.
For a 5 day shipping calendar GOP will back up to the previous working day

as long as item as item can be manufactured on or before that date.