Transfer Context Type Enhancements (Doc ID 2949750.1)

Last updated on NOVEMBER 21, 2023

Applies to:

Goal

Per our previous discussion with the product team, regarding multi-brand requirements, the following enhancements will be needed.

Question: Describe how the current product functionality is insufficient.
Answer: Brand visibility on multi-brand stores that segregate store operations by brand.

Question: Provide a detailed description of the Enhancement Request.
Answer: 1. Transfer context types added to transfer request Notifications: Important if retailers segregate their store operations across multiple teams – they will know straight away what transfer requests are for which “context type”.

2. Transfer context types configured as mandatory in SIOCS: Allows to ensure context types are always used, attribute can become a key element when implementing SIOCS in retailers with concessions/department stores model.
2.1. Ideally this feature should be aligned between RMFCS and SIOCS so that both leverage context types for this purpose.

3. Transfer context types controlled by security: Allows to show/hide transfer context types to users according to their role in the store.

4. Add transfer context types as a filter or column on container lookups:
4.1. This would facilitate the usage of container lookups – using both EICS and SOCS screens to look up containers, identify incoming deliveries etc. With this filter, they could have a view by context type (Brand).


Question: Describe how this Enhancement will benefit your business.
Answer: For multi-brand stores, that operate with a different team inside the same store with full segregation of inventory these enhancements will facilitate the process of requesting and shipping goods between multi-brand stores.
 

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.