on 06-12-2014 1:57 PM
Hi,
We are implementing cross catalog search in SRM 702 SP5. We have enabled OCI 5.0 & TREX. I am trying to upload catalog data in JSON format using transaction /SRMNXP/CAT01. Once executed, I see there the import history shows green. Is there a way to see more details on the execution of the job?
Please let me know.
Thanks,
Ashwin
Hi Gopi Krishna,
I also facing a same issue. After uploding the JSON file we are unable to find the entries in Staging table.
I am new to the SRM UI. Could you please let me know the technically, how it will upload the data into staging table and sample JSON file. Is there any condition to follow before upload the file.
It would great help for me if you provide the solution.
Thanks
Sree
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Experts,
I want to retrieve data from the Punch-out Catalog into SRM staging tables using HTTP web service.
The external catalog link is accessible from SRM portal without any issue but when I am trying to import the data using /SRMNXP/CAT01 it is runing forever and nothing is updating in staging table.
Please reply asap .
Thanks,
JP
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ashwin,
Could you please tell me how I can convert data into JSON format.
Please see some line from SRM_UI_Add_On_SP01.
They have written that there is two we can can import third party catalog.
2.4.3 Catalog Data Import Formats
3rd party catalog providers can supply the data according to OCI 5.0 specification in 2 ways:
JSON file
HTTP(s) Webservice.
Could you please let me know the configuration or the step to do this.
Thanks,
JP
Hi Jay,
I believe there is some confusion here. The two methods mentioned in the document is related to the delivery method of the file. The supplier catalog can be sent as a file or hosted on there end and extracted via HTTP/HTTPs web service.
If you go into /SRMNXP/CAT01, you will notice that these are one of the options.
On your other question on how to convert, this has to be done via:
1. Manual data conversion
2. Using Ariba Procurment content.
You can refer to article created by Michael Jud .
Thanks,
Ashwin
Hi Ashwin,
In your first paragraph, you have wrote that "The supplier catalog can be sent as a file or hosted on there end and extracted via HTTP/HTTPs web service.".
My question is if catalog will be sent by file it should be in json format and we just need to upload with transaction /SRMNXP/CAT01.
But if we want to extract using web service , how should i approach , do the client will give me such URL,if you have such example , please let me know, i will show to my client and will ask to create same urL.
Thanks,
JP
Hi JP,
The URL shall be entered in the /SRMNXP/CAT01. The data is this present in JSON format but instead on the file sent to you, the hosted data can be pulled from the supplier on periodic basis.
As an example: It will look like this: https://asfdsdf.32452fgv.com/invoke/JSONMX&FUNCTION=DOWNLOADJSON
I cannot share the actual URL as this will reveal other confidential information.
Thanks,
Ashwin
Hi Ashwin, Hi All,
How is the HTTP call made to catalog supplier is it via SPRO->Define external services and by giving additional parameters such as FUNCTION = DOWNLOAD JSON?
If yes, can this be scheduled or will it be a manual process?
Or is the HTTP call to get JSON data made thru code? Especially if it has to be scheduled, lets say hourly or nightly?
I have gone thru the OCI 5 specification and this aspect was not clear. Since you say you have already enabled OCI 5 it will help if you could shed more light on this aspect.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ashwin,
Check by double clicking the log entry in the import history.
Regards,
Bhargava
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bhargava,
Thanks for the reply, we had to apply changes based on note to fix the import history log.
1882385 - SRMNXP:Catalog extraction Post Processing Office BC sets.
But in the log, it is stating "XXX: Could not create number range for Search Term Language". This seems to be causing issue with the searching for cross catalog.
Thanks,
Ashwin
Hi Ashwin,
Yes, we see the data in the staging tables and also the indexing went good as we can see the entries in optimized column in ESH_COCKPIT
The issue is resolved now.I want to share the solution here. The problem was with some mandatory attributes in JSON file which the system was checking during the search return and failing. It was the price validity range for catalog items. After maintaining it manually in /SRMNXP/CAT_ITM the search worked good. And one more thing is we should deactivate the Catalog View ID feature in SPRO if not relevant.
Thanks a lot for your support Ashwin.
Best Regards,
Gopi
Hi Gopi,
I am in the same situation as you were earlier
OCI 5 extraction to staging tables done. Search Connectors set up in ESH cokcpit, Indexing scheduled and completed without errors. I see optimized entries for Attachments, Price conversion table/scales and SRM NXP search terms.
Yet when I go to Search in the UI, I'm not getting any results, I see the loading icon without any results for ever.
I have already made sure that Price validity range is being extracted from JSON file and also present in cat_itm table. Also no catalog views are present in SPRO.
Two questions:
Any inputs appreciated...
Thanks,
Praveen.
Gopi, thanks for the quick response -
I ran the test program by giving connector name and freestyle search and I see entries for SRM (internal) product categories but not for the entries obtained by OCI 5 extraction, although the count does show up in "All Hits".
For search terms -
For internal Product Categories -
Note that from the ESH cockpit I'm not getting any errors for the search terms, and the indexing completes successfully without any errors.
Hi Gopi,
The search connector name has not been changed from the default template. These are the settings during the execution of the search test program ESH_TEST_SEARCH:
This does give the required result as:
The optimized entries are as shown below:
Also by opening the Enterprise Search page from the ESH cockpit (ESH cockpit -> Related Links -> Enterprise Search) I can key in the search parameters and I get the accurate results (see below).
This leads me to believe that the indexing and search are working okay. But the results from the search are not appearing on SRM UI page. Could it be because any additional configuration settings are required to bind the search results to the SRM UI?
Did you have to make any configuration changes in Embedded Search/TREX in order to display the results in UI?
PS: I'm positive I have configured all the required attributes from the user side in PPOMA_BBP.
Any suggestions are appreciated.
Thanks,
Praveen.
Hi Keith - Yes I did. I've been meaning to create an end-to-end config document with nitty-gritty not present in the cookbook
Turns out we needed to implement notes:
2049470 - Search based on Product Category Hierarchy and
2034525 - Catalog Extractor for Product Relationships - Inclusion of Target Catalog Name
These corrections are present in SP06.
Also be sure to select the correct template in the Enhanced Search customizing options as below:
You want to clear the (Gateway & Browser) cache after these settings since the changes are being made to the models in ESH cockpit and load the UI page again.
Let me know if this works for you too..
Regards,
Praveen.
My Apologies - updated correct second note, the (second) one mentioned in last note was for Product Relationships and is only applicable if you intend to maintain them.
For returning Search results in UI, you want to implement these two:
2049470 - Search based on Product Category Hierarchy
2051459 - Search for Item in Category Hierarchy has No Results
Thanks,
Praveen.
User | Count |
---|---|
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.