Oracle Apps Different types of LPN Status

Hi Folks,


Different types of LPN (licence plate number) Status in WMS module


1 - Resides in Inventory
2 - Resides in WIP
3 - Resides in Receiving
4 - Issued out of Stores
5 - Defined but not used
6 - Intransit
7 - At Vendor
8 - Packing context
9 - Loaded to Dock
10 - Prepack for WIP
11 - Picked
12 - Loaded in Staging

Oracle Apps Different Types of Purchase Order

A Standard Purchase Order is one time purchasing to buy goods or services.You can create PO when you know the Item, Price, Delivery schedule and Payment terms

A Blanket Purchase Agreement it’s a long time agreement where you don’t know about Quantity, Price and required Delivery schedule. The Quantity and Price fields will be disabled when you make Blanket Purchase Agreement. You have to enter a Price. The required Quantity, Delivery Schedule and final Price will be informed to the Supplier by creating Blanket Releases against the Blanket Purchase Agreement.

A Planned Purchase Order it’s a long time agreement where you are not sure about the required delivery schedules. You know the details like Item, Price, Delivery Schedule and Payment Terms. In the Planned purchase order you have to enter a Need-By date, but this date that you enter will be treated only as a tentative date. The exact date on which the shipments are to be delivered is informed to the Supplier by creating Schedule Releases against the Planned purchase order.

A  Contract Purchase Agreement is document which gives standard term and conditions created. You do not know even the item that is to be purchased. The only information that you provide in a Contract Purchase Agreement is Supplier, Supplier Site, Payment Terms and Agreement Control details. Standard Purchase Orders are created by referring to the Contract Purchase Agreement when something is to be purchased against this Contract Purchase Agreement.

Oracle Apps Diffrence Between PTO , ATO and CTO

Difference between PTO, ATO and CTO

PTO - Pick to Order environment where the goods are manufactured based on forecasted demand. It’s a fixed configuration of product available which can be order and no changes can be done in this configuration.

ATO: - Assemble to order environment is one in which the product or service is "assembled on receipt of the sales order". The parts are kept in stock but not manufactured until the actual order is created.  Receipt of the order initiates assembly of the customized product. Assemble-to-order is useful where a large number of finished products can be assembled from common components.

CTO: - Configure to Order is a method which allows you to configure your final product by select base product. Based on these selections, configurable items on each quote or order typically generates the "unique product" configuration and manufacturing routing and/or bill of materials based on various features and options. Vendor receiving company subsequently builds that configuration dynamically upon receipt of the order.

Oracle Apps :- You are not allowed to create Order lines

User will get an Error while try to create Order line.

 "You are not allowed to create Order lines"

Solution:-

This is might be because of Processing Constraint which don't have Validation template.

To Fix the issue Navigate to Order Management Super User responsibility

Setups>Rules>Security>Processing Constraints

Query the Application by F11

Enter Application: - Order Management

Enter Entity: - Order Lines

Once the result come query for Create Operation.

There would be one record which don.t have validation Template attached to it.

User Action = Not Allowed and Enabled Check box was ON and the system check box is OFF

The Condition was "ANY" but there were no Validation Template and in Applicable to Tab "All Responsibility" Tab was enabled.

Delete that record and save.

This will eliminate the issue.

Oracle Apps How to Find the Concurrent Request

Hi Folks

Below is the query to find out the Concurrent Name.

select a.user_concurrent_queue_name

from fnd_concurrent_queues_vl a,

FND_CONCURRENT_QUEUE_CONTENT b,

fnd_concurrent_programs_vl c

where a.concurrent_queue_id=b.concurrent_queue_id

and b.type_id = c.concurrent_program_id

and c.user_concurrent_program_name=:RequestName

How do get user level Profile option

Hi Folks,

Below is the query to get User Profile Option.

/* How do get user level Profile option  */

 SELECT   p.user_profile_option_name, '3 - User', u.user_name, v.level_value,

         v.profile_option_value

    FROM fnd_profile_option_values v, fnd_profile_options_vl p, fnd_user u

   WHERE v.profile_option_id = p.profile_option_id

     AND (v.level_id = 10004 AND u.user_id = v.level_value)

     AND u.user_name = :User_ID

ORDER BY 1, 2, 3

To get the PR Action History Details

Hi Floks

How to get PR action history from the back-end?

Below is the query.

select hr.name ORG_NAME,prh.segment1 Requisition_Number,prh.AUTHORIZATION_STATUS,pah.LAST_UPDATE_DATE,pah.CREATION_DATE,pah.OBJECT_ID,

       NVL2(pah.ACTION_CODE,'COMPLETE','PENDING')Action_Status ,pah.ACTION_CODE,papf.full_name,pah.ACTION_DATE,pah.NOTE

from po_requisition_headers_all prh,po_action_history pah, per_all_people_f papf,hr_all_organization_units hr

where papf.person_id = pah.employee_id 

and pah.object_id = prh.REQUISITION_HEADER_ID

and prh.org_id = hr.organization_id

and prh.AUTHORIZATION_STATUS = 'IN PROCESS'

and prh.segment1 = :'PR_Number'

order by pah.LAST_UPDATE_DATE desc

Order To Cash Cycle:-

In this Article We will see the Tables involved in O2C and Functional Flow cycle

·         Enter the Sales Order

The header information is stored in OE_ORDER_HEADERS_ALL and the line information in OE_ORDER_LINES_ALL when the order is entered.

The column called FLOW_STATUS_CODE is available in both the headers and lines tables which tell us the status of the order at each stage.

·         Book the Sales Order

The Flow_Status_Code in the table OE_Order_Headers_All would be Booked

And the Flow_Status_Code in the table OE_Order_Headers_All would be Awaiting Shipping

Data will be created in WSH_DELIVERY_DETAILS with the Released_Status = ‘R’

The Concurrent request will fire in Background and insert demand into MTL_DEMAND

·         Launch Pick Release

·         Ship Confirm

·         Create Invoice

·         Create the Receipts either manually or using Auto Lockbox ( In this article we will concentrate on Manual creation)

·         Transfer to General Ledger

·         Journal Import

·         Posting

Let’s get into the details of each step mentioned above.

Enter the Sales Order:

Navigation:

Order Management Super User Operations (USA)>Orders Returns >Sales Orders

Enter the Customer details (Ship to and Bill to address), Order type.

Click on Lines Tab. Enter the Item to be ordered and the quantity required.

Line is scheduled automatically when the Line Item is saved.

Scheduling/unscheduling can be done manually by selecting Schedule/Un schedule from the Actions Menu.

You can check if the item to be ordered is available in the Inventory by clicking on Availability Button.

Save the work.

Underlying Tables affected:

In Oracle, Order information is maintained at the header and line level.

The header information is stored in OE_ORDER_HEADERS_ALL and the line information in OE_ORDER_LINES_ALL when the order is entered. The column called FLOW_STATUS_CODE is available in both the headers and lines tables which tell us the status of the order at each stage.

At this stage, the FLOW_STATUS_CODE in OE_ORDER_HEADERS_ALL is ‘Entered’

Book the Sales Order:

Book the Order by clicking on the Book Order button.

Now that the Order is BOOKED, the status on the header is change accordingly.

Underlying tables affected:

At this stage:

The FLOW_STATUS_CODE in the table OE_ORDER_HEADERS_ALL would be

‘BOOKED’

The FLOW_STATUS_CODE in OE_ORDER_LINES_ALL will be

‘AWAITING_SHIPPING’.

Record(s) will be created in the table WSH_DELIVERY_DETAILS with

RELEASED_STATUS=’R’ (Ready to Release)

Also Record(s) will be inserted into WSH_DELIVERY_ASSIGNMENTS.

At the same time DEMAND INTERFACE PROGRAM runs in the background and inserts

into MTL_DEMAND

Launch Pick Release:

Navigation:

Shipping > Release Sales Order > Release Sales Orders.

Key in Based on Rule and Order Number

In the Shipping Tab key in the below:

Auto Create Delivery: Yes

Auto Pick Confirm: Yes

Auto Pack Delivery: Yes

In the Inventory Tab:

Auto Allocate: Yes

Enter the Warehouse

Click on Execute Now Button.

On successful completion, the below message would pop up as shown below.

Pick Release process in turn will kick off several other requests like Pick Slip Report,

Shipping Exception Report and Auto Pack Report

Underlying Tables affected:

If Autocreate Delivery is set to ‘Yes’ then a new record is created in the table WSH_NEW_DELIVERIES.

DELIVERY_ID is populated in the table WSH_DELIVERY_ASSIGNMENTS.

The RELEASED_STATUS in WSH_DELIVERY_DETAILS would be now set to ‘Y’ (Pick Confirmed) if Auto Pick Confirm is set to Yes otherwise RELEASED_STATUS is ‘S’ (Release to Warehouse).

Pick Confirm the Order:

IF Auto Pick Confirm in the above step is set to NO, then the following should be done.

Navigation:

Inventory Super User > Move Order> Transact Move Order

In the HEADER tab, enter the BATCH NUMBER (from the above step) of the order. Click FIND. Click on VIEW/UPDATE Allocation, then Click TRANSACT button. Then Transact button will be deactivated then just close it and go to next step.

Ship Confirm the Order:

Navigation:

Order Management Super User>Shipping >Transactions.

Query with the Order Number.

Click On Delivery Tab

Click on Ship Confirm.

The Status in Shipping Transaction screen will now be closed.

This will kick off concurrent programs like.INTERFACE TRIP Stop, Commercial Invoice, Packing Slip Report, Bill of Lading

Underlying tables affected:

RELEASED_STATUS in WSH_DELIVERY_DETAILS would be ‘C’ (Ship Confirmed)

FLOW_STATUS_CODE in OE_ORDER_HEADERS_ALL would be “BOOKED“

FLOW_STATUS_CODE in OE_ORDER_LINES_ALL would be “SHIPPED“

Create Invoice:

Run workflow background Process.

Navigation:

Order Management >view >Requests

Workflow Background Process inserts the records RA_INTERFACE_LINES_ALL with

INTERFACE_LINE_CONTEXT     =     ’ORDER ENTRY’

INTERFACE_LINE_ATTRIBUTE1=     Order_number

INTERFACE_LINE_ATTRIBUTE3=     Delivery_id

and spawns Auto invoice Master Program and Auto invoice import program which creates Invoice for that particular Order.

The Invoice created can be seen using the Receivables responsibility

Navigation:

Receivables Super User> Transactions> Transactions

Query with the Order Number as Reference.

Underlying tables:

RA_CUSTOMER_TRX_ALL will have the Invoice header information. The column INTERFACE_HEADER_ATTRIBUTE1 will have the Order Number.

RA_CUSTOMER_TRX_LINES_ALL will have the Invoice lines information. The column INTERFACE_LINE_ATTRIBUTE1 will have the Order Number.

Create receipt:

Navigation:

Receivables> Receipts> Receipts

Enter the information.

Click on Apply Button to apply it to the Invoice.

Underlying tables:

AR_CASH_RECEIPTS_ALL

Transfer to General Ledger:

To transfer the Receivables accounting information to general ledger, run General Ledger Transfer Program.

Navigation:

Receivables> View Requests

Parameters:

·         Give in the Start date and Post through date to specify the date range of the transactions to be transferred.

·         Specify the GL Posted Date, defaults to SYSDATE.

·         Post in summary: This controls how Receivables creates journal entries for your transactions in the interface table. If you select ‘No’, then the General Ledger Interface program creates at least one journal entry in the interface table for each transaction in your posting submission. If you select ‘Yes’, then the program creates one journal entry for each general ledger account.

·         If the Parameter Run Journal Import is set to ‘Yes’, the journal import program is kicked off automatically which transfers journal entries from the interface table to General Ledger, otherwise follow the topic Journal Import to import the journals to General Ledger manually.

Underlying tables:

This transfers data about your adjustments, chargeback, credit memos, commitments, debit memos, invoices, and receipts to the GL_INTERFACE table.

Journal Import:

To transfer the data from General Ledger Interface table to General Ledger, run the Journal Import program from Oracle General Ledger.

Navigation:

General Ledger > Journal> Import> Run

Parameters:

·         Select the appropriate Source.

·         Enter one of the following Selection Criteria:

No Group ID: To import all data for that source that has no group ID. Use this option if you specified a NULL group ID for this source.

All Group IDs: To import all data for that source that has a group ID. Use this option to import multiple journal batches for the same source with varying group IDs.

Specific Group ID: To import data for a specific source/group ID combination. Choose a specific group ID from the List of Values for the Specific Value field.

If you do not specify a Group ID, General Ledger imports all data from the specified journal entry source, where the Group_ID is null.

·         Define the Journal Import Run Options (optional)

Choose Post Errors to Suspense if you have suspense posting enabled for your set of books to post the difference resulting from any unbalanced journals to your suspense account.

Choose Create Summary Journals to have journal import create the following:

• one journal line for all transactions that share the same account, period, and currency and that has a debit balance

• one journal line for all transactions that share the same account, period, and currency and that has a credit balance.

·         Enter a Date Range to have General Ledger import only journals with accounting dates in that range. If you do not specify a date range, General Ledger imports all journals data.

·         Choose whether to Import Descriptive Flexfields, and whether to import them with validation.

Click on Import button.

Underlying tables:

GL_JE_BATCHES, GL_JE_HEADERS, GL_JE_LINES

Posting:

We have to Post journal batches that we have imported previously to update the account balances in General Ledger.

Navigation:

General Ledger> Journals > Enter

Query for the unposted journals for a specific period as shown below.

From the list of unposted journals displayed, select one journal at a time and click on Post button to post the journal.

If you know the batch name to be posted you can directly post using the Post window

Navigation:

General Ledger> Journals> Post