Blogger Buzz: Blogger: now in even more languages

Blogger Buzz: Blogger: now in even more languages

Purchasing Options

Navigation: Setup > Organizations > Purchasing Options
Screen: Purchasing Options

Requisition Import Group - By
This value determines how the system should group all those Requisitions lines generated by Oracle Inventory based upon the Planning Mechanism. Group requisition lines for each item on a separate requisition
Rate Type
The default rate type is used when the Purchasing Document is in Foreign Currency. The user rate type will ask the user to enter the conversion rate vis-à-vis the foreign currency.
Minimum Release Amount
Minimum Release Amount will determine the minimum amount for which a release can be entered against an Agreement.
Taxable
No.
Price Break Type
Price Break indicates if the Vendor is offering any quantity discount. The Price Break Type will determine the mechanism by which the system should sum up the total Quantity so that the correct Price defaults from the Price Break.
Price Type
This value is used only for referential purpose. Fixed Price Type will indicate that the Price reflected on the Purchase Order is a Fixed Price after negotiating the same with the vendor.
Quote Warning Delay
Quote Warning Delay will determine the number of Days in Advance the system should warn the user before the Quotation expiry date.
RFQ Required
RFQ Required indicates the Buyer that an RFQ was Required for this Requisition before the same was converted into a Purchase Order.
Receipt Close Tolerance
PO Closes for receiving when 95% of the good is received.
Invoice Close Tolerance
No over Invoice Quantity Allowed i.e. the Invoice Quantity and the PO quantity should always match.
Line Type
The default line type in all the Purchasing Documents.
Invoice Matching
Determines the type of Matching the system will subject the Invoice against the source Purchase document.
Accrual
Accrue Expense Items
Determines when the Expense Items/Services will be Accrued.
Accrue Inventory Items
Inventory Accrual will be done Perpetually i.e. The system will accrue the liability on receipt of Goods which are Stockable (Current Assets) in nature.
Expense AP Accrual Account
The default Expense AP Accrual Account.
Control
Price Tolerance
The Price Tolerance allowed when the Purchase Order Price differs from the Item List Price as entered in the Item Master.
Enforce Price Tolerance
Determines whether the Price Tolerance should be enforced or not.
Enforce Full Lot Quantity
Not Applicable
Display Disposition Messages
Not Applicable
Receipt Close Point
This option determines when the system should close the Purchase Order close for receiving.
Notify if Blanket PO Exists
The option determines whether the system should Notify you, In case you are buying an Item on Standard Purchase Order though a Blanket Agreement exists for that Item.
Cancel Requisitions
In case of a Purchasing Document being cancelled, how the system should treat the associated Requisition. Should it cancel the Requisition optionally or overtime?
Allow Item Description Update
This control Attribute will determine whether the Item description can be updated or not at the time of raising a Purchasing document.
Security Hierarchy
The Security Hierarchy determines the various positions, which will have access to the various documents.
Enforce Buyer Name
This option will restrict the other buyer from accessing the documents belonging to another Buyer.
Enforce Vendor Hold
If a Vendor has been put on hold in the Vendor Master, should the system stop you from entering any Purchasing documents against that vendor?
Numbering
RFQ Number – Entry
Numbering options determines the way the system should number the various purchasing documents.
RFQ Number – Type
-do-
RFQ Number – Next Number
-do-
Quotation Number – Entry
-do-
Quotation Number – Type
-do-
Quotation Number – Next Number
-do-
PO Number – Entry
-do-
PO Number – Type
-do-
PO Number – Next Number
-do-
Requisition Number – Entry
-do-
Requisition Number – Type
-do-
Requisition Number – Next Number
-do-

OM Flow and table level Information

Steps in Order Cycle:


1) Order Entry
2) Booking
3) Pick release :
For this we have to go to
Shipping Responsibilty Release sales order
Here In this form , In the ORDER tab, we have to enter ORDER Number
And delete the Scheduled shipped Dates To & Requested Dates To.
In SHIPPING tab, set AUTO CREATE DELIVERY to YES. In INVENTORY tab enter WAREHOUSE, set AUTO ALLOCATE to YES and AUTO PICK CONFIRM to YES. IF we set AUTO PICK CONFIRM to NO, then We have to go for the following steps

1. go to Inventory Resp
Move order à Transact Move Order then it will ask for
warehouse information. Give the same name as before [M2]
In this form, In the HEADER tab, enter the BATCH
NUMBER of the order that is picked .Then Click FIND
Button. Click on VIEW/UPDATE Allocation, then
Click TRANSACT button. Then Transact button will be
deactivated then just close it and go to next step.

4) Shipping :
For this we need to go to Shipping Transaction Give the order Number, and click find
Then we can see the order status.
Then we have to click DELIVERY Tab Button, in the Action LOV
We have to choose, SHIP CONFIRM.
Then four concurrent program will run in the background.
Such As::
1.) INTERFACE TRIP Stop
2.) Commercial Invoice
3.) Packing Slip Report
4.) Bill of Lading

After this concurrent program will complete successfully, we have to run
One more WORKFLOW BACKGROUND PROGRAM.
· If we don’t want to ship all the items, that are PICKED, then we have to click LINE/LPN tab , then click DETAIL button .
Now, in that form , in the SHIPPING field, we have to enter how Much quantity of items, we want to ship . The rest remain quantity, that are Ordered will become backorder quantity .

5) Interfacing with AR :

After WORKFLOW BACKGROUND PROGRAM
Concurrent program will complete successfully, we have to run
AUTO INVOICE MASTER PROGRAM from
RECEIVABLE RESPONSIBILTY. After this program
will complete successfully , we can the invoice details in
RECEIVALE à TRANSACTIONS à TRANSACTIONS. Here in
This Form, we have to give our order number in reference field
And query for the invoice details .Then we can see the invoice details.




Table Level Information:
==========================
Order Entry
• At the header level a record gets inserted into the header table
OE_ORDER_HEADERS_ALL.
• At the line level, record(s) get inserted into the Line table
OE_ORDER_LINES_ALL.

Order Booking
• This will update FLOW_STATUS_CODE value in the table
OE_ORDER_HEADERS_ALL to “BOOKED”
• The FLOW_STATUS_CODE in OE_ORDER_LINES_ALL will change to
AWAITING_SHIPPING.
• Record(s) will be created into the table WSH_DELIVERY_DETAILS with
RELEASED_STATUS=’R’ (Ready to Release)
OE_INTERFACED_FLAG=’N’ (Not interfaced to OM)
INV_INTERFACED_FLAG=’N’ (Not interfaced to Inv)
• Record(s) will be created into WSH_DELIVERY_ASSIGNMENTS but with
DELIVERY_ID null.

Pick Release
------------------
IF “Autocreate Delivery” option = “Yes” THEN
• ) Create a record into the table WSH_NEW_DELIVERIES
• ) Update WSH_DELIVERY_ASSIGNMENTS with DELIVERY_ID, thus
• ) Update WSH_DELIVERY_DETAILS with RELEASED_STATUS=’Y

Auto Invoicing
----------------------
Before running “Autoinvoice Program”, record(s) will exist into the table
RA_INTERFACE_LINES_ALL with

INTERFACE_LINE_CONTEXT = ’ORDER ENTRY’
INTERFACE_LINE_ATTRIBUTE1 = &Order_number
INTERFACE_LINE_ATTRIBUTE3 = &Delivery_id
SALES_ORDER = &Order_number

After running the “Auto invoice Program” for the order:
Records will be deleted from the table RA_INTERFACE_LINES_ALL and new details will be created into the following RA transaction tables.
>RA_CUSTOMER_TRX_ALL with
INTERFACE_HEADER_ATTRIBUTE1=&Order_number
RA_CUSTOMER_TRX_LINES_ALL with
INTERFACE_LINE_ATTRIBUTE1 = &Order_number
SALES_ORDER = &Order_number

Know Current APPS Current Versions.

1)select product_version,patch_level from fnd_product_installations
Get current version ana Patch level information.
2)select * FROM V$VERSION
Database Version infomation.
3)select * from v$instance
Instance details
4)select WF_EVENT_XML.XMLVersion() XML_VERSION from sys.dual;
Current XML Parser Version info.
5)select TEXT from WF_RESOURCES where TYPE = 'WFTKN' and NAME = 'WF_VERSION'
Workflow version Number.
6)select home_url from icx_parameters
Oracle applications front end URL
7)SELECT VALUE FROM V$PARAMETER WHERE NAME=’USER_DUMP_DEST’
Get the Trace file location.
8) XML Publisher Vesion info.
$OA_JAVA/oracle/apps/xdo/common/MetaInfo.class.

Another way to find the Jdev Path and DBC file Location.

Log on to Sysadmin-> profiles->
Personalize Self-Service Defn Yes
2)Bounce the Apache and click on about This page.
3)Click on Java System Properties
System Property
DBCLocation :
-> /u02/app/apntstv2/ntstv2appl/fnd/11.5.0/secure/ntstv2_nacdell03/

Then Click on Technology Components
Product/Component
1)OA Framework -> 11.5.10 2CU
2)Oracle Applications Extension -> 9.0.3.8.12 (build 1271)
3)Business Components->9.0.3.13.51
4)MDS->9.0.5.4.81_481

Forward Declaration

PL/SQL allows for a special subprogram declaration called a forward declaration. It consists of the subprogram
specification in the package body terminated by a semicolon. You can use forward declarations to do the
following:
• Define subprograms in logical or alphabetical order.
• Define mutually recursive subprograms.(both calling each other).
• Group subprograms in a package
Example of forward Declaration:
CREATE OR REPLACE PACKAGE BODY forward_pack
IS
PROCEDURE calc_rating(. . .); -- forward declaration
PROCEDURE award_bonus(. . .)
IS -- subprograms defined
BEGIN -- in alphabetical order
calc_rating(. . .);
. . .
END;
PROCEDURE calc_rating(. . .)
IS
BEGIN
. . .
END;
END forward_pack;

BIND Vs LEXICAL

BIND VARIABLE :
-- are used to replace a single value in sql, pl/sql
-- bind variable may be used to replace expressions in select, where, group, order
by, having, connect by, start with cause of queries.
-- bind reference may not be referenced in FROM clause (or) in place of
reserved words or clauses.
LEXICAL REFERENCE:
-- you can use lexical reference to replace the clauses appearing AFTER select,
from, group by, having, connect by, start with.
-- you can’t make lexical reference in a pl/sql statmetns.

Flex mode and Confine mode

Confine mode
On: child objects cannot be moved outside their enclosing parent objects.
Off: child objects can be moved outside their enclosing parent objects.

Flex mode:
On: parent borders "stretch" when child objects are moved against them.
Off: parent borders remain fixed when child objects are moved against
them.


Diff Between Implicit and Explicit Cursors
1) Implicit: declared for all DML and pl/sql statements.
By default it selects one row only.

2) Explicit: Declared and named by the programmer.Use explicit cursor to individually process each row returned by a Multiple statements, is called ACTIVE SET. Allows the programmer to manually control explicit cursor in the
Pl/sql block

Execution Sequences of sql clauses.
a)Select…..
b)Group by…
c)Having…
d)Orderby..

performance problem in a Report

Tune the Report Main Query
Create indexes on columns used in where condition (eliminate full table scan)
set trace on in before report and set trace off in after report

Before Report:
srw.do_sql('alter session set sql_trace=true');
After Report:
srw.do_sql('alter session set sql_trace=false');

Trace file will be generated at location:

select value from v$parameter
where name = 'user_dump_dest';

Get the trace file location path

see execution plans in a trace file, you need to format the
generated trace file with tkprof statement.

Store Code statics in local drive.

APPS Key Concepts
a) None of GL module table contain "ORG_ID" Column.
b) FND ->Oracle application foundations
c)ICX: Discoverer Launcher
Get the discover Launcher URL

Account Receivables

Account Receivables
1)Payment Tables in AR
The following tables stores cash and misc information
a)AR_CASH_RECEIPTS_ALL(CASH_RECEIPT_ID)
Stores 1 record for each receipt Entry
b)AR_CASH_RECEIPTS_HISTORY_ALL(CASH_RECEIPT_HISTORY_ID)
Stores all activities that is life cycle of receipt
c)AR_RECEIVABLES_APPLICATIONS_ALL(RECEIVABLES_APPLICATION_ID)
Stores Accounting information
D)AR_PAYMENT_SCHEDULES_ALL
F)AR_DISTRIBUTIONS_ALL(SOURCE_ID)
Stroes Account Distribution information
Setup Tables
a)AR_RECEIPTS_CLASSES(RECEIPT_CLASS_ID)
Contains Receipt class information.
b)AR_RECEIPTS_METHODS(RECEIPT_METHOD_ID)
Stores Receipt information ,Automatic and manually created receipts
c)AR_RECEIPTS_METHOD_ACCOUNTS

HRMS Date Track

Date Tracking

Date Tracking is a special feature in HRMS.important dynamic information in IS HRMS is date-tracked, including information about people, assignments, payrolls, compensation, and benefits.

When you log on to IS HRMS, your effective date is always today’s date.
To view information from another date or to make future-dated changes you must change your effective date.

The two DateTrack command icons on your window toolbar are:
• Alter Effective Date
• View DateTrack History

When you update date-tracked information, you are prompted to choose between Update and Correction options. If you select Update, IS HRMS changes the record as of your effective date but preserves the previous information.

If you select Correction, IS HRMS overrides the previous information with your new changes. You cannot create a record and then update it on the same day. If you try to do this, IS HRMS warns you that the old record will be overridden, and then changes Update to Correction. This occurs because DateTrack maintains records for a minimum of a day at a time.

View DateTrack History
To see all the changes made to a datetracked record over time, use DateTrack History. Click on [Full History] if you want to open a DateTrack History folder showing the value of each field between the from and to dates.

Account Paybles Tables

Account Paybles Tables

1)Invoice Details.
a)Ap_invoices_all(INVOICE_ID)
You can see the approved Invoices.
b)Ap_invoice_Distributions_all(INVOICE_ID)
To get Distributed Invoices information.
2)Invoice Transactions
a)ap_ae_headers_all(AE_HEADER_ID)
b)ap_ae_lines_all
Stores Distributed Accounting information.
3)Payment Schedule Information
a)ap_payment_schedules_all(INVOICE_ID)
Stores Amount remaing information and schedule payments for an invoice.
b)ap_invoice_payments_all(INVOICE_ID,CHECK_ID)
After compleing invoice payment information stores here.
4) Check Information.
a)ap_checks_all(CHECK_ID)
if you done the payment via check this information stores here.
b)AP_CHECK_FORMATS(Check_format_id)
When you create the invoice ie assciated with accouting infomation that information stores in this table.
c)AP_MC_INVOICES(invoice_id,set_of_book_id)
Contains Multiple invoice Currency information as well as Exchange Information.
d)AP_HOLDS_ALL
Holds invoice information you places
f)AP_CHRG_ALLOCATIONS_ALL
Used for AP links with the appropriate invoice distributins.
5)Approval information
a)AP_INV_APRVL_HIST_ALL(Approval history id,invoice_id)
Invoice approval information
b)AP_HISTORY_INVOICES_ALL(Invoice_id,VENDOR_iD)
All invoice history information stores here
c)AP_INVOICE_TRANSMISSIONS(JE_BATCH_ID)
When you post the invoice to GL This table will effected.
6)Terms
a)AP_TERMS_TL(TERMS_ID)
Contains Term information.
b)AP_INTERFACE_REJECTIONS
which could not be processed by Payables Open Interface Import
c)AP_BANK_ACCOUNTS_ALL
information about bank accounts