WOS4_V1.20.0 Release

New Feature:
  •  Set an entry at WOS4 to give notification to login user on new version release time or release note

1) New release notification on the WOS main page;

2) Rlease Note button in WOS main page, can switch to new version page when click it.

  • Inbound Import function should allow to submit different originalSIDate for parts with same SI orderNo via 1 excel file

1) Given a SI contains parts with different originalSIDate

When use import inventory fucntion to this SI

Then the originalSIDate of generated inventory should be the same as the specified value in SI order

2) update Inbound template content. User should download newest inbound template.

  • Apply the customs info of part profile to set the part desc on overseas invoice and SF Express International label

When print SF Express international Label

Then should use the part desc of custom info of part profile which setting in WMS system.

Note:

1> If there’s not custom info, then should follow the current mechanism use the part description from the order

2> confirmed with user, there’s not specific rules to determine to use the import or export custom info, so we just use export custom info of departure country/region this time.

When generate invoice for overseas order

Then should use the part desc of custom info of part profile

Note:

If there’s not custom info, then should follow the current mechanism use the part description from the order

 

  • [Shimadzu] Add system validation on Shimadzu Order No. when user submits new Shimadzu Outbound Order to avoid manual mistake
  1. When WOS4 receives shimadzu outbound template, will check the Shimadzu order No, if already existed in WOS4 and the order status is not cancelled, will reject the order and remind the user;
  2. If the shimadzu order No is existed but order is cancelled, WOS4 will can generate the order;
  3. If the shimadzu order No is not existed in WOS4, system can generate the order normally.
  • Not allow to adjust the inventory with a partNo which does Not have part profile via Inventory Update function

 

If part doesn’t have part profile in WOS4, system should‘t allow WOS4 user to add inventory for it via Inventory Update application

 

  • Should avoid picking for normal order that allocated the Expired/Expiring inventory

When set the expiry date threshold in WMS part profile, when assign picking order in WOS4, system will check if expired date of the part is in the setting,

if yes, will fail to assign picking and give below reminder message,

Failed to assign picking, the allocated inventory is expired/about to expired. Included:
[{Part No},{Part No}…..] of {Order No}
[{Part No},{Part No}…..] of {Order No}

分配拣货失败,已分配的库存已过期或即将过期。包括:
{订单号}所含{商品编号},{商品编号}
{订单号}所含{商品编号},{商品编号}

If pass the validation, will assign picking normally.

 

  • Support set up schedule task to notify stakeholder the expiring/expired inventory

1) Send the expiry report on scheduled time to specified recipients for warehouse customer, below info is needed,

warehouse, customer, recipients, winthin days, scheduled time

2) The report is named with Inventory_Going_To_Expiry_Report_Template.xlsx;

3) The e-mail is like below,

<Subject>

 

{WarehouseCode } {CustomerCode} inventory expiry status notification

 

<Body>

 

Dears,

Please find attached inventory which is expired or will be expired in {x} days.

 

Sincerely,

UFL warehouse system

 

  • Enhancement on the handling logic of applying catalog setting to order on exceptional cases

 

catalog function enhancement:

enhancement1:

When there’s two catalog only the fileName is different

Then the two catalog should be work successfully

 

enhancement2(log and exception dealing):

 When a part of the customer is set to use catalog conversion

When the system fail to convert the part no of this part with catalog with below, Should notifiy the warehouse and supporter,

1> Fail to connect to catalog DB

2> Error occur during conversion

Enhancements:
  •  
Fixings:
  • The easyship order receiving records and Kafka consumption records should be stored.
  •  Inventory should be saved successfully after receive done