惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

D
Docker
小众软件
小众软件
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
酷 壳 – CoolShell
酷 壳 – CoolShell
Apple Machine Learning Research
Apple Machine Learning Research
月光博客
月光博客
人人都是产品经理
人人都是产品经理
大猫的无限游戏
大猫的无限游戏
V
V2EX
阮一峰的网络日志
阮一峰的网络日志
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
博客园 - Franky
WordPress大学
WordPress大学
有赞技术团队
有赞技术团队
Hugging Face - Blog
Hugging Face - Blog
Jina AI
Jina AI
博客园 - 聂微东
S
SegmentFault 最新的问题
量子位
宝玉的分享
宝玉的分享
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
博客园_首页

博客园 - 土鸟

微信挪车功能成功上线,祝贺一下自己 Form personization(Form 个性化)报无权限 (OSP)外包工单关工单失败 failed jobs because of past close date,关工单报错 APP-BOM-20516 错误处理一例 Outer Join Query Over Dblink Can Fail With ORA-904 (Doc ID 730256.1) Oracle Purchasing QUESTIONS AND ANSWERS 符合中国人习惯的oracle取周的日期函数 Form开发中Block的顺序 关于Forms_ddl的应用 Form开发技巧二-----SPECIAL1菜单编成 Form开发技巧一 ------- 相同ORG只允许同时一个Session作业 提高电脑运行速度---清理内存工具 Oracle ADI 错误及解决方式汇总---来自metalink Oracle EBS付款条件 Examples To howto Insert into Transaction Open Interface 传说中的蹭网卡 无法建BOM APP-SQLGL-08252异常处理
Some User Can Not Execute "Ship Confirm"(Doc ID...
土鸟 · 2014-03-15 · via 博客园 - 土鸟

APPLIES TO:

Oracle Shipping Execution - Version 11.5.10.2 and later
Information in this document applies to any platform.
***Checked for relevance on 03-JUN-2010*** 
Form:WSHFSCDL.FMB - Ship Confirm Deliveries

SYMPTOMS

When attempting to Ship Confirm, some users receive errors, but the same SO can be Ship Confirm without errors by other users. 

The following errors appear:
Error: Some deliveries selected for Ship Confirm have errors or warnings.
Error: Failed to submit concurrent program - Interface Trip Stop.
------------------------------------
Error: The inventory information for deliveries at stop XXXX could not be updated. (TRIP_NAME=NNNN)
------------------------------------
Error: Stop XXXX cannot be set to status CLOSED.
------------------------------------
Error: Stop XXXX on trip NNNN is not closed and is prior to the stop YYYY on trip NNNN. Please close the previous stop or re-sequence the stops, if necessary.
------------------------------------
Error: Stop YYYY cannot be set to status CLOSED.
------------------------------------
Error: 0 stops were successfully closed.
0 stops were closed with warnings.
2 stops had errors and could not be closed.
0 stops had warnings and could not be closed.

There aren't any other problems with other concurrent request programs

Ship confirm is ok with Defer Interface checked and then manuly submit ITS

CAUSE

This issue is caused by the setup of printer or printer style

SOLUTION

Verify printer setup and drivers on interface trip stop concurrent program for users that receive errors by comparing with the settings from users that can ship confirm

REFERENCES

BUG:6713731 - SOME USERS CAN NOT EXECUTE SHIP CONFIRM

Bug 6713731 : SOME USERS CAN NOT EXECUTE SHIP CONFIRM

     

To Bottom

 
 

Type

B - Defect

Fixed in Product Version

 

Severity

2 - Severe Loss of Service

Product Version

11.5.10.2

Status

32 - Not a Bug. To Filer

Platform

46 - Linux x86

Created

24-Dec-2007

Platform Version

ES 3

Updated

07-Jan-2008

Base Bug

N/A

Database Version

9.2.0.5.0

Affects Platforms

Generic

Product Source

Oracle

   
   

Related Products

   

Line

Oracle E-Business Suite

Family

Order Management

Area

Order Management

Product

996 - Oracle Shipping Execution

       
Hdr: 6713731 9.2.0.5.0 SHIP_CONFM 11.5.10.2 PRODID-996 PORTID-46
Abstract: SOME USERS CAN NOT EXECUTE SHIP CONFIRM
 
*** 12/24/07 06:09 am *** (ADD: Impact/Symptom->FUNCTIONAL )
*** 12/24/07 06:09 am ***
Tar Number: SR:6684029.992
BUG TYPE CHOSEN
---------------
  Code
PROBLEM STATEMENT:
------------------
When attempting to Ship Confirm, the following error occurs.
 
Error: Some deliveries selected for Ship Confirm have errors or warnings.
Error: Failed to submit concurrent program - Interface Trip Stop.
------------------------------------
Error: The inventory information for deliveries at stop PREMIER -
USA:Somerset could not be
updated. (TRIP_NAME=839217)
------------------------------------
Error: Stop PREMIER - USA:Somerset cannot be set to status CLOSED.
------------------------------------
Error: Stop PREMIER - USA:Somerset on trip 839217 is not closed and is prior
to the stop
1599:NEWPORT, TN on trip 839217. Please close the previous stop or
re-sequence the stops, if
necessary.
------------------------------------
Error: Stop 1599:NEWPORT, TN cannot be set to status CLOSED.
 
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, not all users can ship confirm.
 
 
 
Verified the issue in the screen shots as noted below:
 
SCREEN SHOTS
-----------------------
Filename = Filename
See the following error:
 
Error: Some deliveries selected for Ship Confirm have errors or warnings.
Error: Failed to submit concurrent program - Interface Trip Stop.
------------------------------------
Error: The inventory information for deliveries at stop PREMIER -
USA:Somerset could not be
updated. (TRIP_NAME=839217)
------------------------------------
Error: Stop PREMIER - USA:Somerset cannot be set to status CLOSED.
------------------------------------
Error: Stop PREMIER - USA:Somerset on trip 839217 is not closed and is prior
to the stop
1599:NEWPORT, TN on trip 839217. Please close the previous stop or
re-sequence the stops, if
necessary.
------------------------------------
Error: Stop 1599:NEWPORT, TN cannot be set to status CLOSED.
------------------------------------
Error: 0 stops were successfully closed.
0 stops were closed with warnings.
2 stops had errors and could not be closed.
0 stops had warnings and could not be closed.
 
 
STEPS TO REPRODUCE THE PROBLEM:
-------------------------------
The issue is limited to some users, while other users are able to perform the
same transaction:
1. Query up the Delivery in the Shipping Transactions form
2. Press Ship Confirm button
3. Error message comes up
WORKAROUNDS:
------------
Research - 19-DEC-2007 13:17:12 GMT - AXHILDEB.DE
(Note: This is INTERNAL ONLY research.  No action should be taken by the
customer on this
information.
This is research only, and may NOT be applicable to your specific situation.)
 
Article-ID:         Note 437095.1
Circulation:        MODERATED (EXTERNAL)
Folder:             EBS.Mfg.Shipping
Topic:              SE-INT-SC. Shipping Execution Open Interface
Title:              WSH_DELIVERIES_PUB.DELIVERY_ACTION API GIVES ERROR IN
JAPAN
                    OU
 
Article-ID:         Note 228311.1
Alias:              SOL:OSS360624
Circulation:        ARCHIVED (EXTERNAL)
Folder:             EBS.Mfg.Shipping
Topic:              SE-TRIP.Trips
Title:              WSHFSTRX Unable to Update the Trip Status, Getting Error
*** 12/24/07 06:10 am ***
*** 12/24/07 06:14 am ***
*** 12/24/07 08:04 am ***
*** 12/25/07 09:03 pm ***
*** 12/26/07 02:04 am *** (CHG: Sta->30)
*** 12/26/07 02:04 am ***
*** 12/26/07 02:06 am ***
*** 01/03/08 03:37 am *** (CHG: Sta->11)
*** 01/03/08 03:38 am ***
Bhupendra,
1) It works OK when running step by step.
2) No problem with other concurrent processes.
3) Uploaded l1247398.zip to the bug folder.
Thanks, Steve.
*** 01/04/08 05:57 am *** (CHG: Sta->30)
*** 01/04/08 05:57 am ***
*** 01/07/08 04:47 am *** (CHG: Sta->11)
*** 01/07/08 04:47 am ***
*** 01/07/08 05:20 am *** (CHG: Sta->32)
*** 01/07/08 05:20 am ***