API to partially Backorder a Pick Released Order Line
Use Shipping API to backorder items on an order which has been pick released
This is achieved using the WSH_DELIVERY_DETAILS_PUB.Update_Shipping_Attributes API. This API should be called with the following input variables.
- source_code := 'OE'; -- The only source code that should be used by the API
- changed_attributes(1).delivery_detail_id := &delivery_detail_id -- Delivery Detail ID
- changed_attributes(1).shipped_quantity := &shipped_quantity -- Quantity to be shipped, remainder will be backordered.
The following test case has been executed:
1. Created an Order with three Lines
Line 1 -- PC Mousepad -- Ordered Qty = 15
Line 2 -- PC Mousepad -- Ordered Qty = 10
Line 3 -- PC01200097 -- Ordered Qty = 20
2. Navigate to Shipping Transaction Form
3. Search for the order created.
4. Select all three lines and then Launch Pick Release.
5. The status of the lines should change to show that the lines can now be pick confirmed - status should be "Staged/Pick Confirmed". A single delivery should have been created.
6. Obtain the value stored in DELIVERY_DETAIL_ID - this is shown on the Shipping transaction form in the Detail column.
7. Call the WSH_DELIVERY_DETAILS_PUB.Update_Shipping_Attributes API to change the shipped quantity to 7 (3 items will be backordered)
8. After calling the code, examine the Shipping Transactions Form, lines/lpns tab for the order to see that the Delivery Line will be changed so that the shipped quantity is 7 and the backordered quantity is 3.
9. Ship Confirm the Delivery, The outcome of doing this will be that:
9.1. Ship confirmed 15 of line 1 on the order
9.2. Ship confirmed 7 of line 3 on the order
9.3. BACKORDERED 3 of line 2 on the order
9.4. Ship Confirmed 10 of line 3 on the order
OE Header or OE Lines Table Column Links Back To A Purchase REQ for Back To Back Orders
Unable to link a purchase order and sale order?. There isn't a table column that links from the OE lines to the req lines.
The following sql query can be used to retrieve the data.
SELECT oh.Order_Number,
oh.Header_Id,
ol.Line_Id,
prh.Requisition_Header_Id,
prh.Segment1 req_Number,
prl.Requisition_Line_Id,
Pl.po_Line_Id,
poh.po_Header_Id,
poh.Segment1 po_Number
FROM oe_Order_Headers_All oh,
oe_Order_Lines_All ol,
po_Requisition_Headers_All prh,
po_Requisition_Lines_All prl,
po_Line_Locations_All pol,
po_Headers_All poh,
po_Lines_All Pl
WHERE ol.Header_Id = oh.Header_Id
AND prh.InterFace_Source_Line_Id = ol.Line_Id
AND prh.InterFace_Source_Code = 'CTO'
AND prh.Requisition_Header_Id = prl.Requisition_Header_Id
AND prl.Line_Location_Id = pol.Line_Location_Id
AND pol.po_Header_Id = poh.po_Header_Id
AND pol.po_Line_Id = Pl.po_Line_Id
AND ol.Line_Id = &sales_order_line_id;
Set Defaulting Shipping Document at the time of ship confirm based on the customers
To default a specific ship confirm document set for a specific customer,
The default ship confirm document set can be set only for a specific organization, it cannot be set for specific customers. Therefore, there is no functionality available to create a default document set for a specific customer. You can, however, define a different document set for each customer and instruct your users to use the correct document set for each delivery that is ship confirmed.
1. Define a different document set for each customer that requires a unique document set
1.1 As the Order Management super user, navigate to shipping->setup->documents->document sets.
1.2 Define a custom document set and give it a name which will identify the customer or customers for which it should be used.
1.3 Add to the document set all of the documents required by the specific customer(s) for which it is created.
2. Define ship confirm rules to use the document sets defined in step 1.
2.1 Navigate to shipping->setup->ship confirm rules
2.2 Create a new ship confirm rule, giving it a name indicating when it is to be used (similar to the document set created in step 1.2)
2.3 Set whatever other parameters are appropriate to this ship confirm rule (for example, ship all or ship entered quantities, specify a default shipping method, etc.)
2.4 At the bottom of the form, in the Document Set field, specify the Document Set you created in step 1.2
2.5 Instruct your users to always used the document set which corresponds to the customer to which it applies
If you pick release and ship confirm in one step, then you can also create a pick release rule unique to each customer.
3. Define pick release rules to use the ship confirm rules created in step 2:
3.1 Navigate to shipping->setup->picking->Define Release Rules Form
3.2 Give the new rule a name similar to the names of the document set and ship confirm rule from steps 1.2 and 2.2
3.3 Complete all fields in the Order tab as appropriate for your business
3.4 In the Shipping tab, Autocreate Deliveries and auto Pick Confirm should be set to Yes
3.5 In the Ship Confirm Rule field, select the ship confirm rule you defined in step 2 (Whenever a ship confirm rule is specified here, the system will automatically ship confirm the delivery created by pick release.)
3.6 In the Inventory tab, set Auto Allocate to Yes.
3.7 Instruct your users to always use the correct pick release rule when picking orders for these unique customers.
Now when you pick release an order specifying the pick release rule created in step 3, the system will automatically ship confirm the order after it is picked using the ship confirm rule created in step 2, which uses the Document Set defined in Step 1.
Sql queries to validate the data that is part of the approval processing
For purchase order status
select segment1 po#, revision_num r#,
substr(type_lookup_code,1,4) type, authorization_status auth_status,
closed_code, wf_item_type, wf_item_key, org_id
from po_headers_all
where segment1 = '&PO_NUMBER'
For Requisition Status:
select segment1 req#,authorization_status auth_status,
closed_code, wf_item_type, wf_item_key, org_id
from po_requisition_headers_all
where segment1 = '&REQ_NUM'
Release Status:
select po.segment1 po#, rel.release_num rel#, po.revision_num po_r#,
po.authorization_status po_status, po.closed_code close_po,
po.wf_item_type po_type, po.wf_item_key po_key, po.org_id org,
rel.wf_item_type rel_type, rel.wf_item_key rel_key,
rel.po_release_id rel_id, rel.authorization_status rel_status, rel.hold_flag hold
from po_headers_all po, po_releases_all rel
where po.po_header_id = rel.po_header_id
and po.segment1 = '&PO_NUM'
and rel.release_num = 'REL_NUM'
order by 1,2
Purchase Order Action History:
select poah.sequence_num seq#, poah.action_date, poah.action_code,
poah.employee_id emp_id, fnd.user_name, substr(poah.object_type_code,1,3) type, poah.object_sub_type_code sub_type,
poah.object_revision_num rev, pohead.org_id
from po_action_history poah, fnd_user fnd, po_headers_all pohead
where poah.object_id = pohead.po_header_id
and pohead.segment1 = '&PO_NUMBER'
and pohead.org_id = '&ORG_ID'
and substr(poah.object_type_code,1,3) = 'PO'
and poah.employee_id = fnd.employee_id
and fnd.session_number != 0
order by 2,1
Requisition Action History:
select poah.sequence_num seq#, poah.action_date, poah.action_code,
poah.employee_id emp_id, fnd.user_name, substr (poah.object_type_code,1,3) type, poah.object_sub_type_code sub_type,
poah.object_revision_num rev, pohead.org_id, poah.note
from po_action_history poah, fnd_user fnd, po_requisition_headers_all pohead
where poah.object_id = pohead.requisition_header_id
and pohead.segment1 = '&REQ_NUMBER'
and substr(poah.object_type_code,1,3) = 'REQ'
and pohead.org_id = '&ORG_ID'
and poah.employee_id = fnd.employee_id
and fnd.session_number != 0
order by 9,2,1
Position Attached to Username:
SELECT pos.name position_name, pa.position_id,fnd.user_name
FROM PER_ALL_ASSIGNMENTS_F pa, per_positions pos,per_jobs job, fnd_user fnd
WHERE pa.POSITION_ID = pos.POSITION_ID
and pa.job_ID = job.job_id
and sysdate between pa.EFFECTIVE_START_DATE
and pa.EFFECTIVE_END_DATE
and pa.primary_flag = 'Y'
and pa.assignment_type = 'E'
and pa.person_id = fnd.employee_id
and pa.PERSON_ID = (select employee_id
from fnd_user
where user_name = '&user_name')
Sql queries to get organization id from requisition, purchase order and purchase order release?
From Requisition:
select hr.name, prh.segment1, prh.org_id
from po_requisition_headers_all prh,
hr_all_organization_units hr
where prh.org_id = hr.organization_id and
prh.segment1 = '&Enter_Req_Number';
From Purchase Order:
select hr.name, poh.segment1, poh.org_id
from po_headers_all poh,
hr_all_organization_units hr
where poh.org_id = hr.organization_id and
poh.segment1 = '&Enter_PO_Number';
select hr.name, poh.segment1, por.release_num, por.org_id
from po_headers_all poh,
po_releases_all por,
hr_all_organization_units hr
where poh.org_id = hr.organization_id and
por.org_id = poh.org_id and
poh.po_header_id = por.po_header_id and
poh.segment1 = '&Enter_PO_Number' and
por.release_num = '&Enter_Release_Num';
How To Progress ATO Lines Passed Supply Eligible?
Various ATO lines are stuck in status of Supply Eligible. You can progress them manually, but how to do this automatically?.
When enter a sales order with an ATO Model on TOP and ATO Items on the lines below, you need to progress each order line manually via "Actions" and "Progress Order" to Create External Requisitions.
In case you do not wish to progress the order manually, there is a concurrent program 'AutoCreate Purchase Requisitions' that picks up all the eligible lines on the basis of what parameters are specified and will dump these lines in requisition interface table. The next run of Requisition Import program will pick up the lines and create requisitions out of them.
What Fields are the Required Fields for a Group of Lines Modifier?
For a modifier line with Modifier Level = Group of Lines, the required fields are:
- Volume Type
Valid values for level = Group of Lines are Item Amount or Item Quantity.
If the pricing request is eligible to receive the modifier, the pricing engine considers the item quantity or item amount consumed for a group of order lines.
- Product Attribute
- Product Attribute Value
Note: If you do not want to limit application by one product, one may enter Product Attribute = ALL_ITEMS and Product Attribute Value = ALL.
How is Receiving supported across multiple operating units in Release 12?
When the Receipts form is opened, the list of values (LOV) will be displayed of the inventory organizations which are available to the user through the security profile. Receiving forms unlike other transaction entry forms in Oracle Purchasing, does not make it mandatory for the user to choose an operating unit even after selecting the inventory organization to receive the shipment. User will still be allowed to change to an operating unit which may not necessarily include the inventory organization chosen initially. For eg. if M1 is an inventory organization which is not included in an operating unit 'Vision Communications (USA)', and if M1 is chosen initially as the receiving inventory organization, user is still allowed to select the operating unit context as Vision Communications (USA). This is an intended feature in Release 12.
Terms and Definitions Used in Intercompany Accounting
Intercompany Journal
This is a journal entry which has transactions for at least
two different companies (or balancing segment values).
Intercompany Journal Out of Balance
An out of balance intercompany journal is one which does not have equal
credit and debit totals for each group of lines by company.
Balancing Segment
This is the accounting flexfield segment that has the balancing segment
qualifier assigned to it. Typically the balancing segment stores the company
values. However, it could represent the cost center, the department or some
other values.
The terms balancing segment and company segment are usually interchangeable.
It is mandatory that one segment of your accounting flexfield be designated
as the balancing segment.
Intercompany Segment
The intercompany segment is the accounting flexfield segment that has
the intercompany segment qualifier assigned to it. This qualifier is only
available in release 11i and is optional. This segment shares the same
value set as the balancing segment.
Clearing Account
A clearing account is a temporary account that holds amounts to be
transferred to another account.
Clearing Company
This is the company value used to clear payables or receivables transactions.
General Ledger uses this company to balance intercompany transactions.
Trading Partner
Trading partner is the company against which the line transaction is made.
Transaction Types
Transactions types are the classifications for journal entries based on
the number of companies involved in the credit and debit side
of the transaction.
The different transaction types are:
One to One: Two different companies in the journal. One company
has the net debit balance and the other has a net credit balance.
Many to One: Different companies have net debit balance and one
company has net credit balance.
One to Many: One Company has net debit balance and more than one
companies have net credit balance.
Many to Many: Two or more companies have net debit balance and
two or more companies have net credit balance.
What are the components of the standalone Oracle Forms product?
The standalone Oracle Forms product is composed of the following:
Forms Builder - this program is used to create and modify Forms modules.
Forms Compiler - this program is used to generate your FMX files.
Forms Runtime - this program is the engine that runs your Form logic when you form is deployed in client/server.
Forms Metric Server - this program is used in Forms load balancing.
Forms Metric Client - this program is used in Forms load balancing.
Forms CGI - this program dynamically generates the applet html that defines your form.
Forms Server - this program listens for Forms Runtime engine requests.
Forms Web Runtime - this program is the engine that runs your Form logic when your form is deployed over the web.
Recent Posts
- Oracle Nukes ETRM
- Urgent Required- IT MNC- Oracle Apps SCM Professionals-Bangalore,Pune,Chennai,Hyderabad
- Account Receivables Tables list oracle r12.2
- General Ledger tables
- Account Payables Tables
Recent Comments
Archives
- April 2021
- June 2015
- April 2015
- March 2015
- July 2014
- April 2014
- February 2014
- January 2014
- December 2013
- November 2013
- October 2013
- August 2013
- January 2013
- June 2012
- May 2012
Categories
- Account Payables
- Advanced Pricing
- General Ledger
- implementation
- Inventory
- jobs
- Multi Org
- Oracle apps general
- oracle fnd
- oracle forms
- oracle hrms
- Order Management
- Purchasing
- Receivables
- Uncategorized
- vision instances