wsh_delivery_Details - Possible values for Released_Status


Table: WSH_DELIVERY_DETAILS
Column: RELEASED_STATUS

Possible Values:
B: Backordered- Line failed to be allocated in Inventory
C: Shipped -Line has been shipped
D: Cancelled -Line is Cancelled
N: Not Ready for Release -Line is not ready to be released
R: Ready to Release: Line is ready to be released
S: Released to Warehouse: Line has been released to Inventory for processing
X: Not Applicable- Line is not applicable for Pick Release
Y: Staged- Line has been picked and staged by Inventory

Delivery line statuses in detail
 Not Applicable (Code X)  
The delivery line can be invoiced but non-shippable, for example, a service line or a warranty line.
Not Ready for Release (Code N)
 The delivery line is not eligible for pick release. This happens when the order line is manually imported into Oracle Shipping Execution using the Import Delivery Line concurrent process or the corresponding order line has not reached the Awaiting Shipping workflow activity.
Ready for Release (Code R)
  The delivery line is eligible for pick release.  Occurs when the order line has reached the Awaiting Shipping workflow activity (it is booked, scheduled, and in Oracle Shipping Execution).
Submitted to Warehouse (Code S)
Pick release has processed the delivery line and has:
·        Created move order headers and lines.
·        Found available quantity and created inventory allocations.
·        Not pick confirmed. If you are using auto-pick confirm, it changes release status to Staged. If you are not using auto-pick confirm and want to progress the delivery lines, navigate to Oracle Inventory Move Order Transaction window and perform manual pick confirm.
Staged (Code Y)
 The delivery line is pick confirmed; inventory is transferred from storage sub-inventory to staging sub-inventory.  It remains staged until ship confirm.
 Backordered (Code B)
Some of the circumstances that can causes this status are listed below
ü  Pick release has processed the delivery line and cannot find the entire quantity.  This typically occurs when the Oracle Inventory indicates that there is not enough material (either because there is not enough material or because the inventory balance is incorrect).  
ü  At ship confirm, you: Enter Shipped Quantity that is less than Original Requested Quantity Backorder the entire delivery quantity transfer a reservation to cycle count.
ü  This typically occurs when the material that you want to ship:
·        Has become unavailable, for example, damaged, between picking and shipping.
·        Is available and you backorder material for specific business reasons. For example, all available material has been allocated to a specific customer when you find out additional supply for other orders will be delayed.
  Shipped (Code C)
  The delivery line’s delivery is ship confirmed and posted as in-transit, OM Interface and Inventory Interface have processed, and the trip is closed.
  Cancelled (Code D)
  The order line that the delivery line supports is cancelled.


Source:
http://www.shareoracleapps.com/2011/02/wshdeliverydetailsreleasedstatus-pick.html

Comments

Post a Comment

Popular posts from this blog

Oracle BI Publisher Tags For-each grouping for Matrix report

For-Each Extensions For-each tags can be confusing.  We will be going over the following tags:     For-each@ section :    For-each@ cell   For-each- group :   field1; field2;     For-each-group: current-group() ;field3;   For-each-group@ column       Sample XML:  <CORPORATION>      <NAME>Vision</NAME>     <DEPT>     <DEPT_NAME>IT</DEPT_NAME>      <EMPLOYEE>         <EMPNO>6</EMPNO>        <ENAME>Rich Walker</ENAME>        <JOB>CLERK</JOB>        <SAL>100</SAL>     </<EMPLOYEE>>     <EMPLOYEE>        ...
Read more

SQL Scripts for Custom Table Creation in Oracle Application 12.2.x

Due to introduction of Online Patching, Post 12.2.x version, there are certain steps to be followed while creating Custom Table. 1. For new table creations - after creating the table in custom schema execute below script to generate edition view and synonym for it in APPS schema. exec AD_ZD_TABLE.UPGRADE('xxcust_schema','xxcust_Table'); 2. For table alterations - after running the DDL run below script to regenerate the edition view for synchronizing any table changes. exec AD_ZD_TABLE.PATCH('xxcust_schema','xxcust_table') 3. Table grants must be done through API to avoid invalids. exec AD_ZD.GRANT_PRIVS('SELECT','xxcust_table,'xx_role') 4. To view objects in all editions, add "_ae" to the data dictionary views select * from user_objects_ae; 5. To update seed data tables in Patch edition, execute prepare command. example:  exec ad_zd_seed.prepare('WF_MESSAGES');  The prepare Procedure will creat...
Read more

Oracle Fusion Business Intelligence Roles

Oracle Business Intelligence roles apply to both Oracle Business Intelligence Publisher and Oracle Fusion Transactional Business Intelligence. They grant access to Business Intelligence functionality, such as the ability to run or author reports. These roles are in addition to the roles that grant access to reports, subject areas, Business Intelligence catalog folders, and HCM data. This topic describes the Business Intelligence roles. This table lists the Business Intelligence roles. Business Intelligence Role Description BI Consumer Role Runs Business Intelligence reports. BI Author Role Creates and edits reports. BI Administrator Role Performs administrative tasks such as creating and editing dashboards and modifying security permissions for reports, folders, and so on. BI Publisher Data Model Developer Role Creates and edits Business Intelligence Publisher data models. BI Consumer Role The predefined Transactional Business Intelligence Transacti...
Read more