Visio stencils for adf faces

https://blogs.oracle.com/jdeveloperpm/entry/adf_faces_stencils_for_visio_available_on_samplecode

Found this link pretty useful to create mockup screens for ADF screens.

You can convert them in to xml and use in ConcepDraw also

PO Unexpected error occurred during Tax Calculation

   Check value populated value tax_attribute_update_code in po_headers_all, po_lines_all and Po_line_locations_all

Can’t see Move Orders Created by other users

ref Metalink : 280131.1

A. Define the INV_INVTOMAI_CREATOR function if is does not already exist:

Navigate: System Administrator > Application > Function
Enter Function Name: INV_INVTOMAI_CREATOR
Enter User Function Name: ‘Move Orders Creator’
Under the Properties tab, enter Type: Subfunction
Enter Maintenance Mode support: None
Enter Context Dependence: Responsibility
Save

B. Assign the function to the Menu you are using:

Navigate System Administrator > Application > Menu
Query for menu ‘INV_MOVE_ORDER’
Add a new line to the menu:
Prompt: ‘Move Order Creator’
Function: select ‘Move Orders Creator’ from the LOV
Description: ‘Move Orders Creator’
Save

Create Adhoc roles in WF Process

you need to create roles if you are using WF to send emails that are not assigned to any application users. following script will help to create them.

PROCEDURE create_adhoc_role (
P_role_email varchar2 )
IS
v_role_email VARCHAR2 (1000);
n_ctr INTEGER := 0;
BEGIN

v_role_email := p_role_email;
SELECT COUNT (1)
INTO n_ctr
FROM wf_local_roles
WHERE NAME = v_role_email;

IF n_ctr = 0
THEN
wf_directory.createadhocrole (role_name => v_role_email,
role_display_name => v_role_email,
role_description => v_role_email,
notification_preference => ‘MAILHTML’,
email_address => v_role_email,
status => ‘ACTIVE’,
expiration_date => NULL
);
END IF;

END create_adhoc_role;

LPN Controlled vs Non LPN Controlled subinventory

LPN Controlled vs Non LPN Controlled

If a subinventory has the LPN Controlled flag

• Subinventory can hold packed and unpacked material
• It can strore LPN’s packed.
• Miscellaneous receipts into this subinventory is not necessarily packed
• Material in this subinventory can be packed

Advantage are huge as you can transact LPN instead of conformation on single item specially items are serial controlled.

If a subinventory has the LPN Controlled flag disabled,
• it cannot store LPNs ( it doesn’t mean that you can’t generate LPN during receiving or select existing LPN)
• LPNs moved into this subinventory are automatically unpacked.
• Miscellaneous receipts into this subinventory must be for loose material
• Material in this subinventory cannot be packed.

Non-LPN controlled subinventories can be used for several different reasons, but two
common scenarios are forward picking areas [retail sales, material is always picked in small quantities ] and backflush subinventories [WIP process, material is automatically pulled for jobs, either as assembly pull or operation pull on the bill of materia ]

APP-AR-11017: Recreation of Payment Schedules failed because the transaction has activity against it

APP-AR-11017: Recreation of Payment Schedules failed because the transaction has activity against it

one of the cause for this error in AR will be different Payment terms id in AR_PAYMENT_SCHEDULES and RA_CUSTOMER_TRX

check term_id  in both table if they are not the same update accordingly

R12: maintain your secondary ledgers

You can maintain secondary ledgers at four levels of details:

• The balance level secondary ledger maintains primary ledger account balances in another accounting representation. This type of secondary ledger requires Oracle General Ledger Consolidation to transfer primary ledger balances to this secondary ledger.

• The journal level secondary ledger maintains journal entries and balances in an additional accounting representation.

This type of secondary ledger is maintained using the General Ledger Posting program. Every time you post a journal in the primary ledger, the same journal can be automatically replicated and maintained in the secondary ledger for those journal sources and categories that are set up for this behavior.

The subledger level secondary ledger uses both Subledger Accounting and the General Ledger Posting program to create the necessary journals in both the primary and secondary ledgers simultaneously. Subledger Accounting creates the journal entries from subledger transactions that integrate with Subledger Accounting.General Ledger Posting creates the journal entries for all other transactions that dono integrate with Subledger Accounting, including manual journal entries.

The adjustments only secondary ledger level is an incomplete accounting representation that holds only adjustments.

The adjustments can be manual adjustments or automated adjustments from Subledger Accounting. This type of ledger must share the same chart of accounts, accounting calendar/period type combination, and currency as the associated primary ledger. To obtain a complete secondary accounting representation that includes both the transactional data and the adjustments, use ledger sets to combine the adjustments-only secondary ledger with the primary ledger when running reports.

Oracle Sales Online Vs Field Sales vs Sales Offline vs Telesales

Oracle Sales Online is the name of an application designed for Field Sales up to and including versions 11.5.10 of the eBusiness Suite.

Oracle Sales Online was designed to work on the pre-OAF tech stack. Oracle Field Sales was designed to take advantage of OAF (Oracle Applications Framework) that becomes more and more prevalent for Oracle applications from version 11.5.10 forward. Other than the OAF uplift, Oracle Sales Online and Oracle Field Sales are very similar in functionality.

Oracle Sales Offline is a subset of Oracle Sales Online (or Oracle Sales) functionality. It is an application designed for Field Sales Reps and can be used without being connected to a server for data; the data is stored on one’s computer.

Oracle Telesales is the name of an application designed for in-house Sales Reps; telemarketing, call center, sales help desks, etc. You must connected to a server for data; the data is not stored on one’s computer. It is also fully CTI (screen pops, IVR, etc.) enabled.

Data Conversion Strategy

The first step you must take when considering your data conversion strategy is deciding what data is important to your business, and how many years of data must be transferred from the old implementation to the new one. For instance, if you would like to take advantage of such features as volume discounting, supplier performance analysis, and creating financial reports spanning multiple fiscal years, you will need to convert some historical data from the existing legacy accounting system. The data may or may not be easy to obtain from the legacy system, and it may or may not be “clean” enough (complete, free from errors) to import into the new implementation without requiring some data cleansing first.

The following is a list of data elements that are typically considered for data conversion when Oracle Applications is replacing an existing implementation:

Oracle Applications Module	Data Elements
Oracle General Ledger	Chart of Accounts Journal entries Actual balances Budgets
Oracle Assets	Assets
Oracle Order Entry	Sales orders Agreements
Oracle Receivables	Customers Invoices Receipts On account Salesperson Territory
Oracle Purchasing	Purchasing items Suppliers Purchase requisitions Purchase orders Receipts
Oracle Payables	Invoices Payments

Implementation Considerations for Enterprise Management Applications

 Every installation of Enterprise Management Applications will entail a different set of considerations. In the following section, you will learn about the most common considerations and what to do about them. These implementation considerations include: 

• Organization structure
• Centralization vs. decentralization
• Rollout strategy
• Data conversion strategy
• Naming conventions 
• ISO certification or other audit requirements
• Identifying critical success factors and areas of improvement ·
• Technical architecture
• Security
• Master files
• Language support
• Reporting needs

The implementation considerations for your particular installation will define the scope of the project. Therefore, the earlier you identify the implementation considerations that are relevant to your project, the more focused your project will be—and the more likely it will be to succeed. The biggest enemy of a successful implementation is scope creep, a phrase that refers to expansions in a project’s scope that occur after the project is underway. Working in a situation that has scope creep is a lot like trying to hit a moving target. The best defense is to define the scope of the project in writing, before work starts, and get the scope document signed by the same people who will sign off on the project once it is finished