PO Life cycle

Purchasing: PO Life Cycle                      

			Online (Manual) PO: Purchase Order  Created in the Purchasing Module Status: “Open”
	PO Closed and Reconciled: Closing a PO sets the status of the PO to “Complete” and signals that the PO is completely processed. Reconciling a PO releases any unused encumbrances associated with the PO. Agencies should perform this weekly: Status: “Complete”				PO Submitted for Approval: Initial Status: “Pending Approval” Resulting Status: “Approved” Amount:                     ChartField: Amt 1 (All POs)          PO Budget Approver Amt 2 (>$10,000)

 

                                                                        

                                                                            

                                                                             

                                                                           

                                                                         

                                                                                                                    

                                                                                                                                                                                                 

PO Budget Checked: Validates sufficient funds are available for the proposed purchase by coding string. If sufficient funds exist, an encumbrance is created for the PO. Batch Frequency: 10am, 12pm, 2pm and once overnight. Budget Status: “Valid”

                                                                                                                                                  

	Start

 

End

                                                                                                                                                                                        

	Invoice Processed by AP and Payment Issued to the Vendor: The vouchers are created, approved and “Matched”. Additionally, the Pay Cycle Runs and payments are issued to the vendor.

 

Return to Vendor: Optional – If items delivered by the vendor do not meet State expectations, the items can be returned to the vendor.

Order delivered by vendor and received in Core-CT: Both Goods and Services are received and keyed into Core-CT. Resulting Status: “Receiv  ed”

PO Dispatched to the Vendor: PO delivered to the vendor by fax, email, EDX, phone, or print method. Status: “Dispatched” Batch Frequency: 10am, 12pm, 2pm and once overnight.

                                                                                                                                                

·        Purchase Order Types:-

1.       Standard Purchase Orders

2.       Blanket Purchase Agreements

3.       Planned Purchase Orders

4.       Contract Purchase Agreements

·        There are 4 main tables associated with PO:-

1.       PO_HEADERS_ALL

2.       PO_LINES_ALL

3.       PO_LINE_LOCATIONS_ALL

4.       PO_DISTRIBUTIONS_ALL

·         PO_HEADERS_ALL:

1.       It contains information for your purchasing documents.

2.       Oracle Purchasing uses this information to record information related to a complete document. The primary key is PO-HEADER_ID.

There are six types of documents that use PO_HEADERS_ALL

1.       RFQs

2.       Quotations

3.       Standard purchase orders

4.       Planned purchase orders

5.       Blanket purchase orders

6.       Contracts

Important data that are populated in this table are=>

· Buyer Information

· Supplier Information

· Brief Notes

· Terms and Conditions

· Status of the document

·        PO_LINES_ALL:

1.       Is a detail of headers table.

2.       This table contain information of line number, the item number and category, unit, price, tax information, matching information, and quantity ordered for the line.

·        PO_LINE_LOCATIONS_ALL:

1.       This table contains information about purchase order shipment schedules and blanket agreement price breaks.

2.       Important data that are populated in this table are=>

- Destination Type

- Requestor Id

- Quantity Ordered and Delivered to Destination.

·        PO_DISTRIBUTIONS_ALL:

1.      It contains accounting information for a purchase order shipment line.

2.      Oracle Purchasing uses this information to record accounting and requisition information for purchase orders and releases

3.      The primary key is PO_DISTRIBUTION_ID.

IMPORTANT COLUMNS OF PURCHASING TABLES

PO_HEADERS_ALL	PO_LINES_ALL	PO_LINE_LOCATIONS_ALL	PO_DISTRIBUTIONS_ALL
-PO_HEADER_ID -SEGMENT1 (PO NUMBER) -VENDOR_ID -VENDOR_SITE_ID -SHIP_TO_LOCATION_ID -CURRENCY_CODE -CLOSED CODE 1. OPEN 2. CLOSED 3. FINALLY 4. HOLD 5. FREEZE	-PO_LINE_ID -CATEGORY_ID -ITEM_ID -PO_HEADER_ID -QUANTITY -CLOSED_CODE 1. OPEN 2. CLOSED	-LINE_LOCATION_ID -SHIP­_TO_LOCATION_ID -PO_HEADER_ID -PO_LINE_ID -QUANTITY_RECEIVED -QUANTITY_ACCEPTED -QUANTITY_REJECTED -CLOSED_CODE 1. OPEN 2. CLOSED FOR INVOICE 3. CLOSED FOR RECEIVING 4. FINALLY CLOSED	-PO_DISTRIBUTION_ID   -PO_HEADER_ID   -PO_LINE_ID   -LINE_LOCATION_ID   -PO_RELEASE_ID   -DISTRIBUTION_NUM

·         Interface Tables Used IN PO and importent columns:-

PO_HEADERS_INTERFACE	PO_LINES_INTERFACE	PO_LINE_LOCATIONS_INTERFACE	PO_DISTRIBUTIONS_INTERFACE
-INTERFACE_HEADER_ID -BATCH_ID -INTERFACE_SOURCE_CODE -PROCESS_CODE -ACTION -GROUP_CODE -ORG_ID -DOCUMENT_TYPE_CODE -DOCUMENT_NUM	-INTERFACE_LINE_ID -INTERFACE_HEADER_ID -ACTION	-INTERFACE_LINE_LOCATION_ID -INTERFACE_HEADER_ID -INTERFACE_LINE_ID -PROCESSING_ID	- INTERFACE_HEADER_ID - INTERFACE_LINE_ID -INTERFACE_DISTRIBUTI ON_ID

·        Another Tables Used In PO:-

1.       PO_VENDORS
-This table stores information about your suppliers.

-Oracle Purchasing uses this information to determine active suppliers.

-The primary key is VENDOR_ID.

2.       PO_VENDOR_SITES_ALL
-This table stores information about supplier sites.

-Oracle Purchasing uses this information to store supplier address information.

- The primary key is VENDOR_SITE_ID.

3.       PO_VENDOR_CONTACTS
-This table stores information about supplier site contacts.

-The primary key is VENDOR_CONTACT_ID

4.       PO_REQUISITION_HEADERS_ALL
-This table stores information about requisition headers.

-Each row contains the requisition number, preparer status, and description.

-The primary key is REQUISITION_HEADER_ID.

5.       PO_REQUISITION_LINES_ALL
-This table stores information about requisition lines.

-Each row contains the line number, item number, item category, item description, need-by  date, deliver-to location, item quantities, units, prices, requestor, notes, and suggested supplier information for the requisition line.

-The primary key is REQUISITION_LINE_ID.

6.       PO_REQ_DISTRIBUTIONS_ALL
-This Table stores information about the accounting distributions associated with each  requisition line.

- Each requisition line must have at least one accounting distribution.

- Each row includes the Accounting Flex field ID and requisition line quantity.

- The primary key is DISTRIBUTION_ID.

How to download /upload WorkFlow

WorkFlow Commands and Instructions:

WorkFlow Commands and Instructions:
------------
The workflow definitions are stored into the database. The standard workflow files (wft) files are in
the $PA_TOP/patch/115/import/US/ and $PO_TOP/patch/115/import/US. The custom files are located in
$PA_TOP/patch/115/import and $PO_TOP/patch/115/import respectively.

When ever any patch is applied that impacts the workflow customizations, follow the below steps to
reapply the customizations.

1) Log on to the environment on which the customizations need to be applied.
2) Set the environment.
Ex: ./oracle/devl/app/prodappl/APPSDEVL_mmpsodevl.env
3) Fire the workflow definition download command to download the workflow definition from the database

How to Download Workflow from Oracle Applications?

DOWNLOAD WORKFLOW:

WFLOAD apps/apps 0 Y DOWNLOAD $HOME/PAAPINVW.wft PAAPINVW

WFLOAD apps/apps 0 Y DOWNLOAD $HOME/poxwfpag.wft POWFPOAG

The above commands creates the workflow definition files (wft) in the local directory $HOME/

4) Verify whether the workflow changes are intact.

5) If the workflow definitions are overwritten then apply the custom workflow definitions from the
mentioned directory.


How to Download Workflow from Oracle Applications?
UPLOAD WORKFLOW:

WFLOAD apps/apps 0 Y UPLOAD $PA_TOP/patch/115/import/PAAPINVW.wft

WFLOAD apps/apps 0 Y UPLOAD $PO_TOP/patch/115/import/poxwfpag.wft

verify the log and output file for any errors.

Note: If the customizations needed to be appended to the standard workflow then, modify the standard
workflow and add the customizations on top of it.

HOW TO load raw data in table using SQL LOADER (SQLLDR)

AIM--->>
"we have need to load data into TABLE from ".CSV" file using "sql loader".
Basically this kind of operation is need when client want to load "RAW Data" in his databse manually,
that time this technic is used.
Actually there are lots of s/w which is used for this operation but use of this method is  a sign of
standard programming.
------------------------------------------------------------------------------------------------------
TASK--->>
load the data of "abc.csv" file into table "abc" using "abc.ctl"
---------------------------------------------------
create table "abc" in databse.
ex-
create table abc(
id number,
name varchar2(25)
);

----------------abc.ctl----------------------------
OPTIONS ( SKIP=1)
LOAD DATA
INFILE '/u02/dev/abc.csv'
APPEND
INTO TABLE abc
fields terminated by ';' TRAILING NULLCOLS
( id,
  name
)
--------------------------------------------------
--------abc.csv contain following data------------
ID;NAME
1;aaa
2;rohit
3;rat
4;rani
---------------------------------------------------------------

How to execute--->
1-go on Putty.
2-type following command
SQLLDR apps/apps abc.ctl

syntax--> Sqlldr username/password(of database) ".ctl_file_name"

Here my database username=apps
                            password=apps


After executing this command see the table "ABC" you will find all data of "abc.csv "file in that table.
ex    --select * from abc
o/p
id name

1  aaa
2  rohit
3  rat
4  rani
------------------------------------------------------------
in above all exmple i usesame name for each file..means..abc.ctl,,abc.csv, table name is abc....
so it is not necessory to use same name u can use diff names......

----------------------------------------------------------------