Order&Shipping Transactions Status Summary

本文详细介绍了订单管理流程中的各个状态阶段,包括下单、预订、拣选、发货及关闭订单的过程,以及每个阶段的状态变化,如已下单、已预订、等待发货等。同时,文章还解释了发货细节状态,例如库存不足导致的回订、已发货、已确认等状态,为读者提供了一站式的订单与发货状态理解指南。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

Order&Shipping Transactions Status Summary

StepOrder Header StatusOrder Line StatusOrder Flow Workflow Status (Order Header)Line Flow Workflow Status (Order Line)Shipping Transaction Status(RELEASED_STATUS in WDD)
1. Enter an OrderEnteredEnteredBook Order ManualEnter – Line N/A
2. Book the OrderBookedAwaiting ShippingClose OrderSchedule ->Create Supply ->Ship – Line Ready to Release(R)
3. Pick the OrderBookedPickedClose OrderShip – Line1.Released to Warehouse(S)(Pick Release but not pick confirm)
2.Staged/Pick Confirmed(Y)(After pick confirm)
4. Ship the OrderBookedShippedClose OrderFulfill – Deferred1.Shipped(After ship confirm)
2.Interfaced(C)(After ITS)
BookedClosedClose OrderFulfill ->Invoice Interface ->Close Line -> End
5. Close the OrderClosedClosedEndEnd


(1) Occurs when pick release has started but not completed. Either no allocations were created or allocations were not yet been pick confirmed.
(2) Occurs when deferred interface is turned on and interface has not kicked off.


OM = Order Management Sales order form
SE = Shipping Transactions or execution form


1)Entered (OM): Order is saved but not booked

2)
Booked (OM): Order is Booked.

3)
Awaiting Shipping (OM): Order is booked but lines are not yet picked.
Navigating to Shipping Execution, the delivery line status flow is:

4)
Not Ready to Release (SE): A delivery line may be in this status when it is interfaced manually into Shipping, is not scheduled and has no reservations. When lines are imported automatically from Order Management this status is not used

5)
Released to Warehouse (SE): Pick Release has started but not yet completed. One of the reason could be allocation have not been pick confirmed. The Pick Release process creates a Move Order Header & Mover Order Line in Inventory. This is a common status for users that perform a two-step pick release process. This status indicates that inventory allocation has occurred however pick conformation has not yet taken place.

6)
Ready to Release (SE): Order Line is booked and passed to shipping execution. The line is now eligible to pick Release.

7)
Backordered(SE): The status of Backorderd is assigned to a line under the following circumstances.

· The Pick Release process attempted to allocate inventory to the line and all or a partial quantity of the item was not available. In this case the system automatically backorders the discrepant quantity.
· At Ship confirm the user enters a shipped quantity for an item that is less than the original requested quantity.
· The user manually Backorders the entire delivery.
8) Shipped (SE) : The delivery line is shipped confirmed.

9)
Confirmed (SE) : The delivery line is shipped or backordered and the trip stops are open.

10)
Picked (OM) : Pick release is complete, both allocations and pick confirm

11)
Picked Partial (OM) : This status occurs when a delivery line is not allocated the full quantity during Pick Release and Ship Confirm has not occurred

12)
Interfaced (SE) : The delivery line is shipped and Inventory interface concurrent process is complete.

13)
Awaiting Fulfillment (OM) : When fulfillment set is used, Not all shippable lines in a fulfillment set or a
configuration are fulfilled

14)
Fulfilled (OM) : All lines in a fulfillment set are fulfilled.

15)
Interfaced to Receivables (OM) : The order is linked with Receivables and the invoice is created.

16)
Partially Interfaced to Receivables (OM) : This status is used in a PTO flow and indicates that the particular PTO item is required for revenue.

17)
Closed (OM) : Closed indicates that the line is closed.

18)
Canceled (OM) : Indicates that the line has been completely canceled. No further processing will occur for this line.

WSH_DELIVERY_DETAILS.Release_Status can have any of the below valid values

SELECT lookup_type,
  lookup_code,
  meaning,
  description
FROM fnd_lookup_values
WHERE lookup_type = 'PICK_STATUS'
AND LANGUAGE      = 'US';
LOOKUP_TYPE LOOKUP_CODEMEANINGDESCRIPTION
PICK_STATUSBBackorderedLine failed to be allocated in Inventory
PICK_STATUSCShippedLine has been shipped
PICK_STATUSDCancelledLine is Cancelled
PICK_STATUSEReplenishment RequestedLine has been replenishment requested
PICK_STATUSFReplenishment CompletedLine has been replenishment completed
PICK_STATUSIInterfacedLine has been shipped and interfaced to Order Management and Inventory
PICK_STATUSKPlanned for CrossdockingLine has been Planned for X-dock
PICK_STATUSLClosedLine has been Received
PICK_STATUSNNot Ready to ReleaseLine is not ready to be released
PICK_STATUSPPurgedLine has been purged from source system
PICK_STATUSRReady to ReleaseLine is ready to be released
PICK_STATUSSReleased to WarehouseLine has been released to Inventory for processing
PICK_STATUSXNot ApplicableLine is not applicable for Pick Release
PICK_STATUSYStaged/Pick ConfirmedLine has been picked and staged by Inventory

WSH_NEW_DELIVERIES.status_code column values

SELECT lookup_type,
  lookup_code,
  meaning,
  description
FROM fnd_lookup_values
WHERE lookup_type = 'TRIP_STATUS'
AND LANGUAGE      = 'US';
LOOKUP_TYPE LOOKUP_CODE MEANINGDESCRIPTION
TRIP_STATUSCLClosedTrip has completed
TRIP_STATUSITIn-TransitTrip is in-transit and has begun
TRIP_STATUSOPOpenTrip is Open and has not begun


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:
1. Created move order headers and lines.
2. Found available quantity and created inventory allocations.
3. 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:
1. Has become unavailable, for example, damaged, between picking and shipping.
2. 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.

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


转载请注明出处:http://blog.youkuaiyun.com/pan_tian/article/details/7696528

========EOF========

<think>好的,我现在需要帮助用户解决在Remix IDE中找不到Web3 Provider环境选项的问题。根据用户提供的引用内容,我需要整理出相关的步骤和可能的解决方法。 首先,用户提到在Remix的Environment下拉框中缺少Web3 Provider选项。根据引用[2],用户应该进入“Deploy & run transactions”部分,然后在Environment中选择Injected Web3或Web3 Provider。如果选项不存在,可能的原因有几个: 1. **插件未启用**:Remix的一些功能依赖于插件。用户需要确认“Deploy & run transactions”插件是否已激活。检查左侧的插件管理器,确保该插件已启用。 2. **Remix版本问题**:线上版本和本地安装的Remix可能有差异。用户使用的是线上版本还是本地部署?引用[3]提到线上版本是https://remix.ethereum.org,而本地版本可能在node_modules中。如果用户使用的是旧版本,可能需要更新到最新版,因为Web3 Provider功能可能在新版本中才有。 3. **网络连接或浏览器插件问题**:如果选择Injected Web3,需要安装MetaMask等钱包插件,并且确保浏览器已正确连接。引用[2]提到会弹出MetaMask插件进行账号绑定,所以用户需要确认插件已安装并登录。 4. **配置错误**:在引用[4]中,部署时需要将Web3 Provider的地址设置为Ganache的服务器地址,如http://127.0.0.1:7545。如果用户的环境设置中没有正确配置URL,可能导致选项不可见或无法连接。 接下来,我需要整理解决步骤。首先检查插件是否启用,然后确认Remix版本,接着安装必要的浏览器插件,最后正确配置Provider的URL。如果问题依旧,可能需要清除缓存或尝试不同的浏览器。 此外,用户可能需要手动输入Provider的URL,如引用[4]所示,在选择了Web3 Provider后输入正确的本地节点地址。还要注意,某些情况下可能需要先编译合约才能看到部署选项,如引用[4]提到的编译步骤。 最后,确保用户了解不同环境选项的区别:Injected Web3用于连接MetaMask等钱包,而Web3 Provider用于直接连接本地或远程节点,如Ganache或Infura。</think>在Remix IDE中添加Web3 Provider环境选项的解决方法如下: ### 步骤1:确认插件状态 1. 打开Remix左侧导航栏的**插件管理器**(Plugins) 2. 搜索并激活`Deploy & run transactions`插件[^2] 3. 若已激活但未显示,尝试刷新页面或清除浏览器缓存 ### 步骤2:版本验证 1. 访问线上最新版地址:https://remix.ethereum.org 2. 本地部署需检查版本号,要求至少v0.12.0+[^3] 3. 更新本地版本命令: ```bash npm install -g remix-ide ``` ### 步骤3:环境配置 1. 进入`Deploy & Run`标签页 2. 在Environment下拉框中: - **Injected Web3**:需提前安装MetaMask插件并登录[^2] - **Web3 Provider**:手动输入节点地址(如Ganache的`http://127.0.0.1:7545`)[^4] 3. 特殊配置示例: ```javascript // 自定义Provider配置(需在控制台操作) const web3 = new Web3(new Web3.providers.HttpProvider("http://localhost:8545")); ``` ### 异常处理 | 现象 | 解决方案 | |------|----------| | 下拉框无选项 | 检查插件是否被防火墙拦截 | | 连接超时 | 验证本地节点(如Ganache)是否启动 | | 账号未绑定 | 在MetaMask中切换至正确网络 |
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值