Search Criteria addition

Hi All,
I wanted to make an enhancement in the BP master data. I wanted to add the SSN number field in the General data tab of the BP master screen. I have done this thing through EEWB.
1. How can i put validations to this field ?
2. How can i use this thing in the search area of the IC Winclient ?
Please give me ur valuable suggestions, that can help me carry on with my work.
Thanks in advance.
Regards,
Prashant.

Hi Prashant,
Answer to your first question.
After adding the fields to the BP transaction the EEWB generates a screen for you. You can write the validation for your fields in the PAI of the screen, the same way as you do in the screen programming.
<b>Reward points if it helps.</b>
Regards,
Amit Mishra

Similar Messages

Can't get additional Spotlight search criteria

When I do a spotlight search, and click on the "plus" button to reveal additional search criteria options, the space opens up but the controls are not shown. I uploaded a screenshot to demonstrate.
I deleted the com.apple.spotlight prefs file to no avail. Anything else I should try, a cache that could be cleared? Or is there a setting somewhere I'm missing? Thanks for any help.

Resetting my Finder preferences by remove the file ~/Library/Preferences/com.apple.finder.plist (or, to preserve your settings in case this tip doesn't work, just move that file out of that folder) brought back the additional search criteria choices but not the right sidebar sort listing

Additional search criterias for opportunities: SYS_PROBABILITY, MilestoneDt

Dear experts,
we need additional search criterias for opportunities
1.) we need to be able to search for the standard field of SYS_PROBABILITY
2.) we need to be able to search for milestone dates we defined
Do you have any idea how to handle these?
Thanks in advance,
BR Matthias

Dear Shiromani,
thanks for your input.
I know about the possibilities of using AET, but the field I need: SYS_PROBABILITY does not show up in the available fields to be added.
Furthermore we dont want to make our self generated fields searchable, but we want to search for specific Milestone Dates we customized.
Any ideas?
Thanks, BR Matthias

IRC Addition Search Criteria Flexfield

Hi
I want to add one search criteria for recruiters and managers for searching on vacancies. This is a simple text item that I added in "Additional Search Criteria Details" as 150 character Optional value set.
But while searching that field is not used at all. I checked the same with IrcVacancyVO query that is executed at the time of search.
When i tried the same thing on vision instance i can see that the query fired IrcVacancyVO have where condition added for the added field.
Any idea which setup step I am missing.

Thanks Tim and NewB
I have set the value for profile option IRC: Search Criteria Segment Matching as ATTRIBUTE1.
Also i tried to run the query by diagnostics on at statement level and noticed one thing in the log
aboutpage_flexFieldRows=[{3=, TableDetail=SegmentsSEARCH_BY_POSITION: (Attribute) displayed, (ColumnName) ATTRIBUTE1, (ValueSet-ListType) 150 Characters Optional-2Context: (Attribute) , (ColumnName) ATTRIBUTE_CATEGORY, (ValueSet-ListType) $FLEX$.DF_CONTEXTS-2WarningDev mode error: The flexfield in query region feature is not fully supported yetDev mode error: The flexfield may cause layout problems in messageComponentLayout bean if the messageComponentLayout's column attribute is greater than 1, 2=IRC_SEARCH_CRITERIA, 1=PER, 0=tableLayout: (SearchCriteriaFlex)}, {3=, TableDetail=SegmentsSEARCH_BY_POSITION: (Attribute) displayed, (ColumnName) ATTRIBUTE1, (ValueSet-ListType) 150 Characters Optional-2Context: (Attribute) , (ColumnName) ATTRIBUTE_CATEGORY, (ValueSet-ListType) $FLEX$.DF_CONTEXTS-2WarningDev mode error: The flexfield in query region feature is not fully supported yet, 2=IRC_SEARCH_CRITERIA, 1=PER, 0=tableLayout: (SearchCriteriaFlexResults)}, {3=, TableDetail=SegmentsSEARCH_BY_POSITION: (Attribute) displayed, (ColumnName) ATTRIBUTE1, (ValueSet-ListType) 150 Characters Optional-2Context: (Attribute) , (ColumnName) ATTRIBUTE_CATEGORY, (ValueSet-ListType) $FLEX$.DF_CONTEXTS-2WarningDev mode error: The flexfield in query region feature is not fully supported yet, 2=PER_VACANCIES, 1=PER, 0=tableLayout: (IrcFlexField1)}]
aboutpage_securityRows=oracle.cabo.ui.data.ListDataObjectList@2a0263
aboutpage_applicationModuleHashtable={oracle.apps.irc.vacancy.server.VacancySearchAM=Y}
aboutpage_voPickList=MessageChoiceBean, localName='messageChoice'
aboutpage_voDetailsHashtable={oracle.apps.irc.vacancy.server.IrcVacancyVO={entityObjectNames=oracle.apps.per.schema.server.PerAllVacanciesEO oracle.apps.per.schema.server.PerJobsEO oracle.apps.per.schema.server.PerGradesEO oracle.apps.per.schema.server.HrAllOrganizationUnitsVlEO oracle.apps.per.schema.server.HrLocationsAllEO oracle.apps.per.schema.server.PerAllPeopleFEO oracle.apps.per.schema.server.HrLookupsEO oracle.apps.per.schema.server.HrAllPositionsFEO oracle.apps.irc.schema.server.IrcVacancySearchCriteriaEO , attributeRows=oracle.cabo.ui.data.ListDataObjectList@2cf6a, properties={OAFLEX_VIEWDEFIMPL_FLEXFIELD_HELPER=oracle.apps.fnd.framework.server.OAFlexViewDefImplFlexfieldHelper@38d3f, _SVC_DomainInfos=oracle.jbo.server.ViewObjectServiceImpl$Domains@12e42e7, _SVC_ImmediateDomainsCache=[]}, entityObjectsRows=oracle.cabo.ui.data.ListDataObjectList@7f4683, query=SELECT Vac.VACANCY_ID, Vac.DATE_FROM, Vac.NAME, Vac.DATE_TO, Vac.DESCRIPTION, Vac.NUMBER_OF_OPENINGS, Vac.LAST_UPDATE_DATE, Vac.CREATION_DATE, Job.NAME AS JobName, Job.JOB_ID, Grade.NAME AS GradeName, Grade.GRADE_ID, Org.NAME AS OrgName, Org.ORGANIZATION_ID, Loc.LOCATION_CODE, Loc.LOCATION_ID, Recruiter.FULL_NAME AS RECRUITER_NAME, Recruiter.PERSON_ID AS RECRUITER_ID, Recruiter.EFFECTIVE_START_DATE, Recruiter.EFFECTIVE_END_DATE, Recruiter.EMAIL_ADDRESS, Manager.FULL_NAME AS MANAGER_NAME, Manager.PERSON_ID AS MANAGER_ID, Manager.EFFECTIVE_START_DATE AS MAN_EFFECTIVE_START_DATE, Manager.EFFECTIVE_END_DATE AS MAN_EFFECTIVE_END_DATE, Manager.EMAIL_ADDRESS AS EMAIL_ADDRESS1, Status.MEANING, Status.LOOKUP_TYPE, Status.LOOKUP_CODE, Vac.REQUISITION_ID, (select count(assignment_type) from per_all_assignments_f paaf where paaf.vacancy_id = Vac.vacancy_id and paaf.assignment_type = 'A' and :1 between PAAF.EFFECTIVE_START_DATE AND PAAF.EFFECTIVE_END_DATE and (fnd_profile.value('IRC_AGENCY_NAME') is null or exists (select 1 from irc_agency_vacancies iav1 ,per_all_people_f per1 ,irc_notification_preferences inp1 where iav1.vacancy_id=vac.vacancy_id and iav1.agency_id=fnd_profile.value('IRC_AGENCY_NAME') and per1.person_id=paaf.person_id and per1.party_id=inp1.party_id and (inp1.agency_id=iav1.agency_id or iav1.manage_applicants_allowed='Y')) ) ) AS APPLICANTS, (select count(distinct assignment_id) from per_all_assignments_f paaf where paaf.vacancy_id = Vac.vacancy_id and assignment_type = 'E' ) AS FILLED, decode(vac.manager_id,:2,'Y','N') AS MY_VACANCIES, Vac.BUDGET_MEASUREMENT_TYPE, Vac.BUDGET_MEASUREMENT_VALUE, posEO.NAME AS NAME1, posEO.POSITION_ID, posEO.EFFECTIVE_START_DATE AS EFFECTIVE_START_DATE2, posEO.EFFECTIVE_END_DATE AS EFFECTIVE_END_DATE2, NULL AS ACCESS_FLAGS, Vac.STATUS AS VACANCY_STATUS, Bg.NAME AS NAME2, Bg.ORGANIZATION_ID AS ORGANIZATION_ID1, Vac.BUSINESS_GROUP_ID, VSC.EMPLOYEE, VSC.CONTRACTOR, VSC.EMPLOYMENT_CATEGORY, VSC.TRAVEL_PERCENTAGE, VSC.MIN_SALARY, VSC.MAX_SALARY, VSC.SALARY_CURRENCY, VSC.PROFESSIONAL_AREA, VSC.WORK_AT_HOME, VSC.MIN_QUAL_LEVEL, VSC.MAX_QUAL_LEVEL, VSC.ATTRIBUTE_CATEGORY, VSC.ATTRIBUTE1, VSC.ATTRIBUTE2, VSC.ATTRIBUTE3, VSC.ATTRIBUTE4, VSC.ATTRIBUTE5, VSC.ATTRIBUTE6, VSC.ATTRIBUTE7, VSC.ATTRIBUTE8, VSC.ATTRIBUTE9, VSC.ATTRIBUTE10, VSC.ATTRIBUTE11, VSC.ATTRIBUTE12, VSC.ATTRIBUTE13, VSC.ATTRIBUTE14, VSC.ATTRIBUTE15, VSC.ATTRIBUTE16, VSC.ATTRIBUTE17, VSC.ATTRIBUTE18, VSC.ATTRIBUTE19, VSC.ATTRIBUTE20, VSC.ATTRIBUTE21, VSC.ATTRIBUTE22, VSC.ATTRIBUTE23, VSC.ATTRIBUTE24, VSC.ATTRIBUTE25, VSC.ATTRIBUTE26, VSC.ATTRIBUTE27, VSC.ATTRIBUTE28, VSC.ATTRIBUTE29, VSC.ATTRIBUTE30, VSC.SEARCH_CRITERIA_ID, Vac.ATTRIBUTE_CATEGORY AS VAC_ATTRIBUTE_CATEGORY, Vac.ATTRIBUTE1 AS VAC_ATTRIBUTE1, Vac.ATTRIBUTE2 AS VAC_ATTRIBUTE2, Vac.ATTRIBUTE3 AS VAC_ATTRIBUTE3, Vac.ATTRIBUTE4 AS VAC_ATTRIBUTE4, Vac.ATTRIBUTE5 AS VAC_ATTRIBUTE5, Vac.ATTRIBUTE6 AS VAC_ATTRIBUTE6, Vac.ATTRIBUTE7 AS VAC_ATTRIBUTE7, Vac.ATTRIBUTE8 AS VAC_ATTRIBUTE8, Vac.ATTRIBUTE9 AS VAC_ATTRIBUTE9, Vac.ATTRIBUTE10 AS VAC_ATTRIBUTE10, Vac.ATTRIBUTE11 AS VAC_ATTRIBUTE11, Vac.ATTRIBUTE12 AS VAC_ATTRIBUTE12, Vac.ATTRIBUTE13 AS VAC_ATTRIBUTE13, Vac.ATTRIBUTE14 AS VAC_ATTRIBUTE14, Vac.ATTRIBUTE15 AS VAC_ATTRIBUTE15, Vac.ATTRIBUTE16 AS VAC_ATTRIBUTE16, Vac.ATTRIBUTE17 AS VAC_ATTRIBUTE17, Vac.ATTRIBUTE18 AS VAC_ATTRIBUTE18, Vac.ATTRIBUTE19 AS VAC_ATTRIBUTE19, Vac.ATTRIBUTE20 AS VAC_ATTRIBUTE20, decode((select update_allowed||delete_allowed from irc_rec_team_members rec where rec.vacancy_id = VAC.vacancy_id and rec.person_id = :3), 'NN', 'VIEW', 'UPDATE') AS TEAM_ACCESS, (select count(*) from hr_api_transactions where transaction_ref_table = 'PER_ALL_VACANCIES' and transaction_ref_id = Vac.vacancy_id and creator_person_id = :4 and status = 'S') AS SaveForLaterLocks, (select count(*) from hr_api_transactions where transaction_ref_table = 'PER_ALL_VACANCIES' and transaction_ref_id = Vac.vacancy_id and status != 'D' and (creator_person_id != :5 or transaction_state != null or status != 'S' )) AS TRANSACTION_LOCKS, (select decode((SELECT count(pav1.vacancy_id) FROM per_all_vacancies pav1 WHERE pav1.vacancy_id =vac.VACANCY_ID AND(pav1.status ='CLOSED' OR (pav1.date_to is not null and NOT :18 BETWEEN pav1.date_from AND pav1.date_to))),0,'Y','N') from dual) AS APPLY_FLAG FROM PER_ALL_VACANCIES Vac, PER_JOBS_VL Job, PER_GRADES_VL Grade, HR_ALL_ORGANIZATION_UNITS_VL Org, HR_LOCATIONS_ALL_VL Loc, PER_ALL_PEOPLE_F Recruiter, PER_ALL_PEOPLE_F Manager, HR_LOOKUPS Status, HR_ALL_POSITIONS_F_VL posEO, HR_ALL_ORGANIZATION_UNITS_VL Bg, IRC_SEARCH_CRITERIA VSC WHERE VAC.vacancy_id = VSC.object_ID(+) AND VSC.object_type(+) = 'VACANCY' and Vac.Job_id = Job.JOB_ID(+) and Vac.Grade_id = Grade.GRADE_ID(+) and Vac.Organization_id = Org.ORGANIZATION_ID(+) and Vac.Location_id = Loc.LOCATION_ID(+) and Vac.Recruiter_id = Recruiter.PERSON_ID(+) and :6 between nvl(Recruiter.EFFECTIVE_START_DATE,:7) and nvl(Recruiter.EFFECTIVE_END_DATE, :8) and Vac.Manager_id = Manager.PERSON_ID(+) and :9 between nvl(Manager.EFFECTIVE_START_DATE,:10) and nvl(Manager.EFFECTIVE_END_DATE,:11) and Status.LOOKUP_TYPE(+) = 'VACANCY_STATUS' and Vac.Status = Status.LOOKUP_CODE(+) AND vac.position_id = posEO.position_id(+) AND :12 between nvl(posEO.EFFECTIVE_START_DATE, :13) AND nvl(posEO.EFFECTIVE_END_DATE, :14) AND VAC.business_group_id = BG.Organization_id and EXISTS (select null from PER_VACANCIES PV where PV.vacancy_id = VAC.vacancy_id) AND (exists (select null from irc_agency_vacancies iav where iav.agency_id = FND_PROFILE.VALUE('IRC_AGENCY_NAME') and iav.vacancy_id = vac.vacancy_id AND :15 between nvl(START_DATE,:16) AND nvl(END_DATE, :17)) or FND_PROFILE.VALUE('IRC_AGENCY_NAME') is null) ORDER BY Vac.NAME}, oracle.apps.irc.candidateSearch.server.IrcVacancySearchCriteriaVO={entityObjectNames=, attributeRows=oracle.cabo.ui.data.ListDataObjectList@1ee8250, properties={OAFLEX_VIEWDEFIMPL_FLEXFIELD_HELPER=oracle.apps.fnd.framework.server.OAFlexViewDefImplFlexfieldHelper@a6247e, _SVC_DomainInfos=oracle.jbo.server.ViewObjectServiceImpl$Domains@1307341, _SVC_ImmediateDomainsCache=[]}, entityObjectsRows=oracle.cabo.ui.data.ListDataObjectList@1ad5641, query=SELECT NULL AS SELECTFLAG,........
Is some thing this causing the issue

Additional Search Criteria for I-Objects in IC Web Client

Hi,
I need to add addtional search criteria like City, Region and Zipcode for I-Objects in the IC Web Client. Can anyone suggest me how to include these new fields?
Thanks,
Vijay

Hi Igor,
Thanks for your reply. Could you please let me know how did you proceed on this problem. Did u contact SAP for this? If so, what is the procedure to contact them? Please let me know so that I will be able to take up this issue with my client.
Thanks,
Vijay

How to add a new search criteria in Advance Search Page in OAF

HI,
In my application (R12) we can access customer related information from 2 places (2 different responsibilities as mentioned below), both are OAF pages.
1. AX receivables
2. Sales online
From both the responsibilities we can perform search for customer related information as well (Simple as well as Advance Search).
But Advance Search screen from 'Sales online' allows user to perform search, based on few additional fields as well such as 'Classification' (it's an lov based field).
Now, User is asking to add that field on search page of AX receivables as well.
So, how to add one more field (as search criteria), on an standard 'Customer' screen?
Additional Info :
1. LOV is based on HzPuiClassificationFilterVO
2. And this VO is available on both pages. (oracle.apps.ar.hz.components.search.server.HzPuiClassificationFilterVO)
So can we achieve this by Personalization only ? if yes plz share the steps as well.
Regards,
Adi

Yes. It is possible through personalization.
1. Create a criteria row under Advance Search
2. Create a Result Item under advance table columns
3. Create a Query Criteria Map based on the criteria and result item above.
Please note the newly added criteria field should be in the Searchresults VO attributes list.
Otherwise you need to extend the VO as well.
Hope this helps.
Regards,
-Mukesh.

ESS Who is Who - Add search criteria

Hi all,
I have tried searching the forums, but can't find an answer for my problem. I want to add an additional field to the search criteria for the who is who iview.
I am able to change the advanced search, but I want to add a search criteria on the first screen. Changing the service for the adress book (Employee Self-Service -> Service-Specific Settings -> Address Book -> Who's Who -> Who's Who (ESS): Selection and Output) does not change this first screen.
Anyone know how I can make this change?
Thanks in advance.
Kind regards,
Marlies

If by selecting fields you mean in the Who's Who (ESS): Selection and Output, then yes.
I have there available 3 tabs, none have the default settings.
First tab I can set the selectionfields, but when changing/adding a field here, my "simple search" does not change. The changes here are reflected under the advanced search, which is nice, but not what I want.
I simply want to add 1 additional field to the first search screen, so the user does not have to always use the advanced search option.

Best way to implement dynamic search criteria

I was recently showing a group of developers some of the Toplink basics. As an example I showed a way to build a Toplink expression for an object search where the search criteria are determined at runtime. Doing this in raw SQL is a bit tricky because you need to place the 'AND' statements between the criteria, but I found a simple method to do this with an expression (or at least I think I did). I simply used and() to add each criteria expression, including the first one. Toplink seemed smart enough to derive the SQL without the additional AND statement.
My question to the Forum is, is this the best way to build the expression and is it flawed? Here is my code snippet and the generated SQL.
public Expression createExpression(ExpressionBuilder builder, Object[] parameters) {
// Build expression for a Dealer Search
String name = (String)parameters[0];
String location = (String)parameters[1];
String email = (String)parameters[2];
Expression searchExpression = builder;
// NAME = 'name'
if (name != null) {
searchExpression =
searchExpression.and(builder.get("name").equal(name));
// LOCATION = 'location'
if (location != null) {
searchExpression =
searchExpression.and(builder.get("location").equal(location));
// EMAIL = 'email
if (email != null) {
searchExpression =
searchExpression.and(builder.get("contactInfo").get("email").equal(email));
return searchExpression;
Toplink generated SQL with location="Mt. Prospect, IL", email=null, and name=null:
SELECT VERSION, LOCATION, ID, NAME FROM DEALER WHERE (LOCATION = 'Mt. Prospect, IL')
Thanks.

All JPA strategies require something (like a table or sequence object) be in the database, with table sequencing being the most portable, though EclipseLink does allow custom sequence stratgies where you could use something else, such as the UUID. Sequencing is described here described here http://wiki.eclipse.org/EclipseLink/Examples/JPA/PrimaryKey with a custom UUID example shown here http://wiki.eclipse.org/EclipseLink/Examples/JPA/CustomSequencing .

How to add search criteria options in CRM UI?

Dear all,
we`ve recently updated to SolMan 7.1 SPS10 (source was SPS04). Now I`m struggling a bit with adding
an additional search criteria to the Incident Management Search View.
I already considered OSS Note 1918128 (same Title as this thread) and I was able to check this in our - not yet updated - Productive System
where this has been implemented already.
Adding the Object /AICRM/PROJECT_ID to the customizing table BTQSRVREQ in SPRO with some Operators didn`t make the trick
See attached Screenshot.
Can you please assist me how I can add an additional Search Criteria to the Icident Management Search context (selectable/Operators etc.?).
Reason behind is - we`d like search for open / closed incident for certain Projects as filter criteria.
In Addition it would be also great to know - How the Incident Management Standard View / Table can be extended
by the column "Project ID".
The Project ID itsself is already linked a new created Icident - hence I`m able check the Project assignment by opening
a specific Icident and personalize the view.
regards and many thx in advance
Benjamin

Hi Benjamin,
Enhancing the one order framework search is a common topic available on a lot of threads and blogs, hence I will add a link here :
SAP CRM Technical Tutorials by Naval Bhatt.: How to enhance Opportunity search for a custom date type
You can refer to this blog for help but lastly it's all debugging and trying that will help you achieve this in your scenario
/Hasan

Adding a new search criteria in Web UI for Sales Order

Hi,
We have a requirement for Web UI as follows :
We want to add the ID number (identification number in BP ) as search criteria for Sales Order simialr to search criteria available in Accounts with ID number .
Can any one please give some inputs on this ?
Regards
Vinayak

Hi Vinayak,
I will try to give you some technical advise.
What you would need to do is:
In transaction SM30 open up view: CRMV_OBJ_BTIL
There is an entry for External Object Name "BTQAct"
The currently used DDIC structure is CRMST_QUERY_ACT_BTIL
You will need to adjust this structure to bring completely new parameters to the UI. This means put in your own.
As you can see in detail for this entry there are three fields with name "Structure" the last one is for the GenIL handler class. Currently it should be empty (there is some fancy SAP logic to determine it automatically). You can override it with your own handler class implementing the logic. As a hint: The implementation class currently used is: CL_CRM_QACT_RUN_BTIL
Anyhow most 1Order searches are handled by the class CL_CRM_Q1O_SEARCH perhaps you can use it as well. Additionally it would be a good idea to provide your users with a value help.
Oh and there is a customizing that lets you define which options (IS, BETWEEN, IS NOT, ...) should be available for the user. Please do not try to do this hardcoded
cheers Carsten

Add search criteria field to ERPQOrder

I would like to add additional search criteria fields to the Dynamic Query Object ERPQOrder. I want to enhance the class CL_CRM_QORDER_RUN_ERPIL for the purpose. Is there a way to accomplish this requirement?

Following steps:
In the Append the structure CRMST_QORDER_ERPIL add the new fields.
Update the design layer by adding the new fields to the UI object type ERP and reference design object ERPQORDER in view cluster CRMVC_SDESIGN_G.
In the view cluster CRMVC_DQ update if the new fields have wild card allowed or not.
Using the BSP component workbench, enhance the component view ERP_S/ErpOrdSQ
Using the UI configuration tool add the new search criteria fields.
Enhance the class method CL_CRM_QORDER_RUN_ERPIL~PREPARE_SELECTION_PARAMETERS to include additional filter criteria.

Change the default search criteria in CMD-F

When you enter CMD-F from a Finder window, the default search criteria that come up is "Kind" is "Any". This is probably the most useless search criterion I can imagine. It is always necessary to add more criteria to get a minimally useful search under way.
Can anyone point me to a source I could use to change this default? In my case, the most common and useful starting point would be "Filename" Contains, and then a blank field into which I could enter a string that might be all or part of a filename.
Thanks.

I don't know how to change the default, but you can set up any number of starting points for searches like this:
Enter Command-F in a Finder window, then set the criteria Filename and Contains. Click the Save lozenge.
In the Save dialog, you will have the option of saving this search to the Finder Sidebar in addition to the default ~/Library/Saved Searches. Click on Smart icon in the Sidebar and a new Finder Search tab will open with your parameters set.
If you don't want to save this search in your Sidebar, you can command-drag its smart folder from ~/Library/Saved Searches to the Finder Toolbar. Clicking on that will bring up a Finder Search with your parameters, as well.

Enhancements in ASN Search Query - additional selection parameter

Hi,
I am working on adding an additional search parameter in ASN Overview screen in supplier view. The search is POWL based and in the "Maintain Search Criteria" screen I have been able to add a custom field named "ZTEST_DATE" of type DATS.
To get the above work done I have followed the following steps
1. Enhanced the method IF_POWL_FEEDER~GET_SEL_CRITERIA of class /SCF/CL_FEEDER_ASN_OV.
2. Enhanced the method PREPARE_LOAD_ASN_FROM_DB of class /SCF/CL_WD_APPL_MODEL_ASN_OV in order to make the additional field as part of ODM parameter.
Now on running the query I get an error mesage sayng "Access Path for the parameter selection couldnt be found".
This error message can be traced to an exception which was raised in GET_ACCID_FOR_READ method of class /SCMB/CL_ODM.
To get rid of this issue I have added additional entry in two Tables /SCMB/ORCPRM (for defining new parameter ZTEST_DATE and linking it to the ODM component DLH1) and another entry in table /SCMB/ORDTPACCSQ to link the previously defined selection parameter to the access Path ORDN for Order Data Type DELV with a sequence no 24 (all the access sequence till 23 had already been taken up for the other selection parameters). Now I am facing trouble to create an active version of this entry. It should be noted that each entry in the table /SCMB/ORDTPACCSQ has two entries one active and one inactive for each Access Path linked to Order Data Type. At this moment only inactive access path could be created.
Is there any additional config step required to get an active version of the newly added access Path?
Thanks and Regards,
Rohit
Edited by: rkb_1984 on Dec 22, 2011 1:25 PM

Hello Rohit,
My understanding of your question is that, you are not able to create the ACTIVE access sequence with all those details what you've provided in your query. I am sure you might have used the Standard SPRO path for ODM configs.
You need to check whether you are creating the access sequence for the correct 'Access Path' or not (i.e. field ACCID in table /SCMB/ORDTPACCSQ). Also, you need to use the access sequence number beyond 90. Might be this would resolve your problem.
Regards,
Rohan Arvindrao

How to Dynamically add Search Criteria in Advance Search Region.

Hi All,
I want to understand how can we add Search Criteria dynamically in the Advance Search Region.
The Requirement is to add 4 additional search criteria for an org_id in a multi org structure. For other business those fields should not be visible.
I did try this with the form personalization but could not Show/hide the additional search criteria programatically for the business as we can only see 4 search criteria at the time of page load and other criteria comes in the drop down list to add which can not be show/hide after page load.
I thought of a solution to add search criterias dynamically for my org through extending controller.
I found the OAAdvanceSearchBean (advance search Region in controller) object for my Advance Search but could you tell me how can I add the Criteria Row in that Advance Search (createWebBean function) and then add the item in criteria Row dynamically.
Also please tell me how we can increase the showed criteria from default 4 to more, setDisplayedCriteriaCount(int) is not allowed and it is not working also.
Thanks.
Regards,
Ashish Bansal

Hi,
As Lars said The "Search Option Set" and the "Search Component Set" offer you quite some flexibility.
You can configure both of these component to customize your search.
Once you did it, you can create a new basic search iview and set these components.
On the other hand, you also customize the layout use to show result of search.
Dont'f forget that you need to configure Trex and create an index.
For instance, I configured the search criteria, the system only asked me some metadatas (created by us,whose value are dependents). Each time that you upload a document you set these attributes.
Then when you want to search, appear a screen with these values
Country :
City:
search field:
Patricio.

JHeadstart Recipe - JHeadstart recipe - non-databound search-criteria

From todayâs customer assignment I extract the following recipe â for BC4J, JSP and Struts:
Suppose that on the FindPage of our JHeadstart generated JSP application we would like to add one or more search-criteria that are not directly bound to ViewObject attributes. For example in the context of the ALS application: the FindBookPage contains a field labeled AuthorFirstName. Here, the user may enter the firstname of an author. The application should now only return books in the result set that have at least one contributing author whose firstname matches the one entered by the end-user. The ViewObject underlying the Bookpages does not contains Authorships and Author information. A direct query on this ViewObject can not make use of the AuthorFirstName property. Of course, when no value is entered in this field, the query should not look for authors at all!
When a value for AuthorFirstName is provided, an additional piece of where-clause should be activated that looks from the ALS_BOOKS table via the ALS_AUTHORSHIPS table in the ALS_AUTHORS table. Now how are we going to do that?
The recipe for this can be found at: http://technology.amis.nl/blog/index.php?p=230.
best regards,
Lucas

Search Criteria addition

Similar Messages

Maybe you are looking for