Some User Can Not Execute "Ship Confirm"(Doc ID 473312.1)
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 |
|
|
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 |
|
|
|
|
|
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 ***
