Skip to Content
author's profile photo Former Member
Former Member

Need Help- Setting up Cust. Specific Products

Experts,

I have this unique situation..

Current client has 3000 customers and they currently have around 2000 product lists (not products, Each list is kind of unique to each customer it is 1:1). I have 2 issues.

1. How do I create this 2000 lists for these customers,, do I have to do the Product Views/ Catalog Views or is there any other way? If i have to do a product view... Can any one please share the tables where they get stored for conversion purposes.

2. Even though they have lets say 20 products in their product list, they want to see only those products which are been ordered in the last 12 months.. not all the products in their view.. How is it possible ? Meaning out of 20 they only order 10 products, so every time a customer is logged in the system must show them a list of the 10 products which are frequently ordered.. If they need to order the 11nth product then they have to serach in the product catalog... I took a smaller quantity here but that can 10 frequent and 500 in their product list..

Any thoughts and ideas would be greatly appreciated and rewarded.

SundaragirišŸ˜­

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Aug 06, 2013 at 03:18 PM

    Venkata - Good question!

    Q1: Easiest way probably would be to configure a dedicated catalog view for each individual customer. This might sound daunting initially but will greatly minimize the ongoing maintenance moving onwards.

    Q2: This sounds like a very custom development effort; based upon the views the created in Q1, products are presented in the UI layer. As stated products which should be presented are based upon order history for the past 12 months.

    Any new catalog view requires to be published and activated before it become available to the customers. To fulfill this requirement you might think to develop a background job which runs periodically that goes to the following steps:

    1) Select order history for past 12 months;

    2) Determine corresponding order line items;

    3) Create/maintain catalog view based on outcome step 2;

    4) Publish catalog view by customer.

    Question; how do you introduce any new products to such catalog?

    Hope this helps,

    Tiest

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Sep 06, 2013 at 01:53 PM

    Hi Venkata,

    If you have not gone ahead yet with your approach and would like to consider something more flexible/performant, read further. Else, just ignore šŸ˜Š

    I am going with a few assumptions here because I do not know your landscape:

    1. You are using a B2B scenario

    2. You are in ISA 5.0 / 7.0 but not WCEM.

    3. You have a CRM backend replicating to a TREX system or an ERP backend and using r3memory catalog

    Now, to the details:

    1. You could mimic your trex replication process to fill up the catalog contents to some zret tables, instead of the normal sret tables (in case of CRM) or to some custom tables (in case of r3).

    2. Use inclusion/exclusion concepts for customer views (instead of catalog views as that is a daunting task in setting up). The inclusion / exclusion could be based on any factor/attribute of your customer/product master. You could design that.

    3. Now on your ISA, if you are using the memory catalog concept, you could change the backend call to read from zret tables, then apply the inclusion/exclusion logic in the same call using the logged on user information.

    4. What you get back will exactly be what you defined to see for each customer.

    I know it is a totally custom solution, but trust me it works well and easy to change the logic in the backend system for future needs.

    Pradeep

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.