SUS-MM Lanscape with SRM 5.0 as an Add-on with ECC6.0

All-
We are implementing SRM 5.0 as an add on with ECC 6.0. We are aware of all the constraints and those constraints do not matter within our scope. The open question that we have is that if SRM is installed as an Add on with ECC.
Can we also leverage the SUS-MM functionality within SRM, when installed as an Add on with ECC 6.0??
Any help would be appreciated.
Sundeep

Marcin,
FYI
http://help.sap.com/saphelp_erp2005/helpdata/en/index_srmaddon.htm
Sundeep

Similar Messages

SRM 5.0 as an Add on with ECC 6.0

Even i have the same question on how we would manage the distibution model when the SRM System is installed as an add on with ECC. Since being on the same client here are some of the Questions. I have also opened a new thread on this.
1.) How would the distribution model be distributed when on the same client?
2.) How would the Documents flow between two different systems?
3.) In an SUS-MM scenario, how would this be handled when installed on the same client?
4.) How would material and vendor replication facilitated?
Any thoughts would be highly appreciated !!
Thanks,
Sundeep

Hi Sundeep,
I have answered for vendor replication here :
One Client Solution
For product category, material and material type replication, this is same process through activation of relevant objects in table mdsv_ctrl_opt_a
Then you have to trigger the replication through mds_load_cockpit
For SUS, you have to select SUS_ONE (instead of EBP_ONE) in table bbp_backend_dest
That all what i know so far
Kind regards,
Yann

ERP release for Central Contract Management with SRM 7.0 EhP 1

Hi all,
i would like to have clarification with ERP and SRM release combinations regarding SRM 7.0 EhP1.
Indeed, the "Software Component Matrix for SAP SRM 7.0 EHP1", for Operational Contract Management, tells 'EHP 5 for SAP ERP 6.0 required'.
Moreover, in RKT dealing with SRM EhP1 delta overview, ERP 6.0 with EhP5 is mandatory for an upgrade to SRM7.01.
Nevertheless, i would like to have confirmation regarding this point.
We do not want to use PI to execute the Enterprise Services for CCM. So, we intend to switch BF SRM_WSRM_1 on.
But on the ERP side (EhP5), the only BF dealing with Contract Management is LOG_MM_P2PSE_2 which description is about Service Procurement (and more exactly for item hierarchies).
Does it mean we can use SRM 7.01 with ERP 6.0 EhP4 and without PI but only if we do not use Central Contracts with service hierarchies ?
Thank you for your help.
Regards.
Laurent.

Hi Laurent,
Yes.
When Central contract was designed in SRM 7.0 with ERP EhP4, it was designed with no service hierarchy. But in SRM 7.01 Central contral was enhanced to handle service hierarchy and it works with ERP EhP5. The problem is when we have SRM 7.01 and ERP EhP4. To handle this complication SRM 7.01 was designed to send flat service lines to EhP4 and lower release even though Central contract in SRM has service hierarchy. So while transfering to ERP EhP4 system in standard, all outlines are not consider for transfer and only service lines (Functional items) are transferred to ERP. To do so user needs to maintain the backend destination information of the connected backend system in table BBP_BACKEND_DEST via SM30 transaction with correct system type (for EhP4 system it will be ERP_4.0 and for EhP5 ERP_5.0). SAP Standard program checks this while XML generation for transfer and if system type is ERP_4.0 system it removes all outlines from temp table before generating the XML data. When it is done, ERP has only service lines in its XML and it does the manupulation to create the replication of central contract.
Master Guide (Including Upgrade Information) - SAP SRM 7.01 states:
"The use of SAP NetWeaver PI is optional but it is required for outbound XML-based messaging or for connecting non-SAP planning or execution systems."
So service hierarchy is possible in SRM 7.01 and ECC 6.04 but only with PI. For other CCM functionalities, SRM 7.01 and ECC 6.04 without PI works fine.
Best regards,
Christian Zeuch

PI 7.0 with SRM-SUS

Hello:
We want to install SRM-SUS and integrate it with MM and with other SRM installation. As we know we need PI for the integration. We've PI 7.0. Do you know if we need to migrate to 7.1 or the standard interfases for SAP-SUS can use PI 7.0 ?
Thanks in advance.
Fernando.

Hello:
We want to install SRM 7.01, is this version compatible with PI 7.0?. We suppose it, but it's a very recent version and we want to confirm this point.
Thanks again.

SAP eSourcing with SRM Extended Classic Scenario

Hi Team,
We are using ECC 6.0 with eSourcing. Currently we use SRM 5.0 with Classic Scenario.
Now we are planning an upgrade from SRM 5.5 to SRM 7.0 and want to do the Extended Classic Scenario. This will help us to do additional functionalities of SRM.
eSourcing can be used for Strategic RFx and CLM functionalities.
SRM can be used for SC, Operational Sourcing and PO. We can also use the SRM-SUS Scenario for PO confirmation and Invoices.
Have any one used eSourcing with SRM Extended Classic? In that case, please provide some light into how to use all these application to better streamline the overall Source to Procure strategy.
Also, do you think Classic is the way to go or Extended Classic is better? Any documents or pictures are greatly appreciated.
Thanks
Jogy

Hi
SAP provide standard integration b/w ECC and Esourcing/ CLM (PR (both inbound and outbound). However in case you decide to go with extended classic scenario,you might need e Sourcing/ CLM integration with SRM (since PO would be created in SRM) which is not provided out of the box by SAP. However custom interface (based on flat file transfer) can be built b/w SAP SRM and e Sourcing.
MM-SUS scenario is not much different from EBP-SUS scenario in terms of functionality.
Regards
Mudit Saini

Linking of ECC vendor with SRM ROS supplier in EBP

Hello,
How can we link manualy created ECC vendor with SRM ROS supplier in EBP, I dont have PI system.
Thnks,
Raju

Raju the link is established basically (if i talk purely technical) in table VENMAP.
it has 3 fields...
partner guid| logical_system| vendor number(in logical system)
so here
partner_guid is the guid of the supplier in BUT000
log_sys is the logical system to which you want it to connect it to(in this case ECC logical system)
and vendor is the vendor number in that connecting logical system(means ecc vendor number)
so this creates the link.
but which version of SRM and SUS are you using?

Vendor replication in One client ERP, with SRM 5.0 version

Hi Guys,
Can anyone suggest me how to do the vendor replication in the One client ERP i.e SRM is being on the same stack of the SAP R/3 system. which is set as a one of the node in the SAP R/3 SPRO path. this is in Version 5.0.
Please suggest how to do the Vendor replication in this, whether are there any prerquisties for doing this replication?
The VenMap Table is not getting updated with entries.
Please help me soon.
Regards
Srujan K

Hi
no ranges you need to take care of this if you want to transfer same no range as ECC no range.
slg1 - you can see logs
bucf - no range for vendors
+SAP Implementation Guide
++Cross-application components
+++SAP Business Partner
++++Business Partner
+++++Basic Settings
++++++Number Ranges and Groupings
+++++++Define Number Ranges
+++++++Define Groupings and Assign Number Ranges
sorry. do you want Suggestion ECC as well as SRM in one client?
Master Data Synchronization in mySAP ERP
Purpose
In order for the Supplier Relationship Management (SRM) application to run as add-on in a mySAP ERP environment, it is necessary to synchronize master data objects within this platform, that are similar from a business point of view, yet technically different.
Master data objects on ERP and SRM side that need to be synchronized
ERP (SAP ECC*)
Corresponding object in SRM
Vendor
Business partner
Material/service
Product
Material type/service type
Product category
ECC: Enterprise Core Component
Integration
Master data synchronization in ERP is carried out centrally.
For more information, see: Master Data Synchronization
Once you have set up master data synchronization for your objects using the Synchronization Cockpit, and after initial data synchronization and key mapping has been completed, delta reports that run in the background ensure that master data is always matched.
The individual configuration steps are described in the IMG:
Supplier Relationship Management ® SRM Server ® Master Data ® Master Data Synchronization in mySAP ERP (One Client)
Features
This function ensures that changes (create, change, delete) that are made to objects on one side cause immediate (bidirectional) update to the same objects on the other side. In this way, SRM and ECC data is permanently synchronized.
·         Purchasing organizations are not included in the automatic bidirectional master data synchronization and, as is also the case with mySAP SRM, have to be matched manually or via an update report (ECC -> SRM).
Replication (and the updates) from plant (MM) to business partner location (SRM) only occurs in one direction with the report BBP_LOCATIONS_GET_FROM_SYSTEM that is executed manually.
·         Where SAP Supplier Self-Services (SUS) runs together with mySAP SRM on one ERP platform, master data synchronization occurs as described above. If SUS runs separately of ERP, SAP NetWeaver XI is used to synchronize master data with SRM.
Master Data Synchronization
Purpose
Master data synchronization synchronizes master data objects in an SAP system that are similar from a business, but not from a technical, point of view, and in this way allows you to integrate different SAP applications seamlessly in your business processes.
You can use master data synchronization, for example, to set up integration of the SAP Business Partner with the customer master. This allows you to integrate SAP applications that make technical use of the Business Partner in their user interface, and use the customer master as a technical basis in subsequent business processes.
Implementation Considerations
In order to be able to use master data synchronization, you must have defined and activated Synchronization Control as well as Customer/Vendor Integration and/or Material/Service Integration in Customizing of the Cross-Application Components under Master Data Synchronization.
Pay attention to the following note on master data synchronization terminology:
The paired terms, customer/debtor and supplier/creditor/vendor, are used with the same meaning in master data synchronization, and one term can be substituted synonymously when the documentation is read.
Integration
Master data synchronization is based in particular on the two master data objects SAP Business Partner and SAP Product, and makes it possible for the following synchronization processes, among others, to be carried out:
·        Synchronization of the business partner with the customer/debtor master
·        Synchronization of the business partner with the supplier/creditor master
·        Synchronization of the product with the material master
·        Synchronization of the product with the service master
For a complete list of all synchronization processes that are defined and active in an SAP system, see the synchronization cockpit under Synchronization Processes.
Master data synchronization replaces the current technical solutions for Customer/Vendor Integration and complements some business processes that are based on integration between the product master and the material or service master (Material/Service Integration).
Master data synchronization also has an effect on the archiving processes of the master data objects business partner/customer master /vendor master and product/material master /service master.
For more information on activating/deactivating synchronization processes, see the IMG of the Cross-Application Components under Master Data Synchronization ® Synchronization Control.
Features
Synchronization Directions
A synchronization process is always defined as a one-way synchronization between a source object type and a target object type, meaning that the synchronization is only ever active in one direction, from the source object type to the target object type. If the data of an object instance of the source object type is changed, the corresponding data in the corresponding object instance of the target object type is changed at the same time. Both synchronization directions must be activated in the SAP system in order to allow the undirected synchronization of two master data object types.
Synchronization Scenarios
There are two synchronization scenarios in master data synchronization:
·        Synchronization from the master data maintenance
When you create and save new master data, the system carries out initial synchronization with the master data object types for which synchronization processes have been activated in the SAP system, and creates the corresponding master data.
If you change existing master data that has already been synchronized, the system locks this master data, and all the corresponding master data of the source object type and the target object type during maintenance. When you save the changed master data, the system generally carries out a delta synchronization with the master data object types for which synchronization processes have been activated in the SAP system, and changes the corresponding master data. In some cases, changing existing master data can lead to a delta synchronization having to be carried out.
·        Synchronization using the synchronization cockpit
You use the synchronization cockpit to prepare, perform and check the initial synchronization of master data objects in an SAP system.
Constraints
Master data synchronization can neither synchronize master data objects across systems, nor can it transfer master data objects from external or legacy systems. You can use the SAP external data transfer to transfer legacy or external data.
Synchronization Cockpit
Definition
User interface for master data synchronization in an SAP system.
Use
Using the synchronization cockpit, you can carry out all the steps for master data synchronization in an SAP system These are as follows:
·        Customizing synchronization
·        Selection, preparation and starting of synchronization runs.
·        Monitoring of synchronization runs
·        Postprocessingof synchronization errors
·        You can start the synchronization cockpit in Customizing of the Cross-Application Components under Master Data Synchronization ® Synchronization of Mass Data ® Execute Synchronization Cockpit.
Before you can work with the synchronization cockpit, the following prerequisites must be fulfilled:
·        There are data records for at least one source object in the SAP system.
·        You are authorized to carry out synchronization.
·        You are authorized to start the Postprocessing Office (PPO).
·        You have carried out the Customizing of the master data synchronization.
·        You have carried out the general Customizing for the PPO.
For more information, see the Implementation Guide (IMG) of the Cross Application Components under General Application Functions ® Postprocessing Office.
·        You have activated the writing of PPO orders for the master data objects in Customizing of the master data synchronization.
For more information see the Implementation Guide (IMG) of the Cross-Application Components under Master Data Synchronization ® Synchronization Control ® Activate PPO Orders for Platform Objects in the Dialog.
Structure
The synchronization cockpit is divided into three work areas:
·        Synchronization processes work area
This work area contains a list of the synchronization processes. The list displays only the active synchronization processes, or all the synchronization processes. You can change between the two views at any time.
·        Customizing synchronization work area
This work area contains an overview of all the reports that you can use for the Customizing synchronization.
·        Synchronization work area
This work area contains the tab pages Processing and Monitor, which you can use to prepare or monitor synchronization runs.
Integration
The Postprocessing Office (PPO) is integrated in the synchronization cockpit, so that it can be used to postprocess synchronization errors. If the PPO has not been activated, the synchronization cockpit does not start synchronization in the case of an error, and issues the relevant error message.
br
Muthu

Kanban integration with SRM

Hi,
We have implemented SRM 5.0 with MM-SUS scenario and backend system is SAP R/3 4.7.
In present scenario, schedules generated through MRP are available on Suppliers portal for ASN generation.
Now we are planning to go for KANBAN process in R/3 and integration with SUS.
Our requirements are as follows
1) MRP generated schedule releases in R/3 must be available on supplier portal as indicative schedule
2) KANBAN generated schedules in R/3 must be available on supplier portal as active schedule against which supplier will be able to generate the ASNs.
3) On schedule generation the same should be communicated to supplier and 3PL (transporter) through email / SMS.
Please let me know the feasibility of the above requirements in SRM. Whether it can be done with standard process or development is needed.
Thanks in advance
Best Regards,
Rahul Taskhedkar.
[email protected]

Hi
There is no standard interface available out of the box b/w SAP E Sourcing and SRM7.0. However you can create a custom XML/ flat file based interface with help from XI/PI expert.
SRM 7.0 doesnot offer contract authoring feature.
Regards
Mudit Saini

EP WITH SRM

Hi,
We are working with SRM and EP as user interface. One of the applications that we are gfoing to use is the auction with LAC (LIVE AUCTION COCKPIT) this is a java component from SRM.
We configured the LAC including the SSO with the ITS because at that moment we didn´t have EP and the application worked well. Then we install and configure the EP as our final user interface all the SSO with SRM and SUS are working well but when we work with the auctions and exceute the LAC (java component like EP) a login screen appears asking for a user and a password. why with the ITS that doesn´t happend and with EP ask for a user????
We try to configure a SSO between LAC and EP, is that possible????
Do we configure something like sso between EP and another java component (LAC)????
what do we need to configure?????
Thanks.

Hi Check below thread
read LAC installation guide in which sso information also available.
problem configuration LAC 1.0
Koti Reddy

We work with SRM 5 Ext' Classic & report based on organization plan

Hello expert,
We work with SRM 5 Extended Classic scenario and BW for reports.
We have a lot of purchasing types and we need a good report that can give as a clear picture of the purchasing process according to the organization units (departments). We have one purchase organization and a lot of purchase groups, and the way that the system is built doesnu2019t support this requirement. We need a report that is based on the organization plan.
For example:
We need the option to extract all HR unit purchase documents or all direct supply goods that are purchased by the supply chain department. The report also needs to give a clear picture of the purchase operations and costs of every unit.
Thanks,
Gil

Closed but Unanswered

How to create a document with SRM BAPIS

Dear colleagues,
I have a problem with SRM BAPIs. I need to insert a pdf document into a record using SAP BAPIs, This document is already in a table in a binary format
I am trying with these BAPIs:
    1.
          CALL FUNCTION 'BAPI_SRM_DOC_CREATE'
              EXPORTING
                rms_id                  = rms_id
                sps_id                  = sps_id
                documentid              = documentid
                description             = 'DESCRIPTION'
                do_commit               = 'X'
                documentid_check_unique = 'X'
              IMPORTING
                return                  = return
                objectid                = objectid
                documentclass           = documentclass
              TABLES
                required_properties     = required_properties.
          This BAPI is working as expected. It returns objectid for the new document.
     2. Now I'm using BAPI_RECORD_ADDELEMENT:
             ls_doc_id-objectid = objectid.
            CLEAR: ls_sp_poid. " clear weg und ls_sp_poid clearen
            ls_sp_poid-name = 'DOC_ID'.
            ls_sp_poid-value = ls_doc_id.
            APPEND ls_sp_poid TO lt_sp_poid.
            CLEAR: ls_doc_id.
            ls_sp_poid-name = 'VARIANT'.
            ls_sp_poid-value = '0'.
            APPEND ls_sp_poid TO lt_sp_poid.
            CLEAR: ls_doc_id.
            ls_sp_poid-name = 'VERSION'.
            ls_sp_poid-value = '0'.
            APPEND ls_sp_poid TO lt_sp_poid.
            ls_insertion_by_anchor-anchor = 'DECRET'.
            ls_insertion_by_anchor-parent_node_id = '5'.
            ls_insertion_by_anchor-parent_node_attr_name = 'DECRETAT'.
            ls_insertion_by_anchor-parent_node_attr_value = '40'.
          CALL FUNCTION 'BAPI_RECORD_ADDELEMENT'
              EXPORTING
                objectid                    = zrm_attcab_scr-phio_id
                documentclass               = documentclass
                sps_id                      = 'ZRM_SPS_DOCVAR'
                anchor                      = 'DECRETS'
                description                 = 'Descripcion'
                store_as_new_version        = 'X' "Si X se crea vacio
*               STACKED                     = ''
*               DOC_CONTEXT                 =
                element_type                = 'I'
*                 insertion_by_anchor         = ls_insertion_by_anchor
*                insertion_by_modelid        = insertion_by_modelid
*               INSERTION_BY_REFERENCE_NODE =
*              ALL_SAME_NAME_ANCHOR        = 'X'
*               SET_ELEM_DESCR_HARD         = ' '
*                omit_authority_check        = 'X'
              IMPORTING
                return                      = ls_return
              TABLES
                element_sp_poid             = lt_sp_poid.
*             ELEMENT_PROPERTIES                =
*             ELEMENT_VISIBILITY                =
         This BAPI returns an internal error
Am I following the correct steps or am I skipping anything?
Could anyone help me?
Thanks in advance!!

I have the same problem!!!
Anyone knows?
Thanks!

MDM catalog integration with SRM 7.0

Hi all,
We will be upgrading from SRM 5.0 to SRM 7.0
We currently have CCM .....Few questins on catalog enablement for us with SRM 7:
1.With SRM 7,0,can we use CCM oor MDM is the only option???
2.Is it better to have MDM as a seperate server and enable SRM MDM catalog content?
3.We have 2 punch out catalogs for 2 vendors.How to enable the punch out catalog links in SRM 7.0???What is the path for IMG config??
4. We have around 20 internal supplier catalogs .Now should we upload few of the supplier catalogs and then upload rest or can we upload all the suuplier catalogs at once through IMPORT MANAGER in MDM ???What are therestrictions in terms of the no of catalogs or catalog data that can be improted and mapped ???
5.What are additional features in SRM MDM 3.0 catalog in contrast to CCM??
6.The backend master data such as Supplier/Porg etc.....how is that synchronised from SRM to SRM MDM catalog???Is it through some scheduled programs???
7.What is the use of PI/XI in enabling SRM MDM catalog??Why is it mandatory??
8. What are the allowed file types for cataog data upload in MDM???Like it was CSV in CCM...
9. Where can I find some sample catalog files for test upload?
10.What are the lastest SP for MDM available for integration with SRM 7.0??
11. after price changes from supplier(thru negotiation),are these price changes to be updated manually for indiavidual items/products through MDM data manager or is there any way to automate this delta update for price in MDM???
12.Also maintaining catalog data in MDM for SRM procurement will be a seprate actibity just like maintaing catalog in CCM??
I have gone through the help links but wud like ansers to above ques based on experiences of the forum members...Please provide inputs to my above queries if anybody has worked on MDM catalog integration with SRM 7.0....
Thanks for your time.

HI,
1.With SRM 7,0,can we use CCM oor MDM is the only option???
   You can use any catalogs which support SAP OCI interface.
2.Is it better to have MDM as a seperate server and enable SRM MDM catalog content?
   MDM Server(contents) and AS Java(for UI) are required. Please check the installation guide.
3.We have 2 punch out catalogs for 2 vendors.How to enable the punch out catalog links in SRM 7.0???What is the path for IMG config??
   Same as SRM 5.0. Define External Web Services.
4. We have around 20 internal supplier catalogs .Now should we upload few of the supplier catalogs and then upload rest or can we upload all the suuplier catalogs at once through IMPORT MANAGER in MDM ???What are therestrictions in terms of the no of catalogs or catalog data that can be improted and mapped ???
Yes. You can use Import Manager. No issues.
6.The backend master data such as Supplier/Porg etc.....how is that synchronised from SRM to SRM MDM catalog???Is it through some scheduled programs???
MDM Extractor is available.
7.What is the use of PI/XI in enabling SRM MDM catalog??Why is it mandatory??
Mainly for contents mapping.
8. What are the allowed file types for cataog data upload in MDM???Like it was CSV in CCM...
Any. Even for DB interface is also supported. You see all options when you run import manager.
9. Where can I find some sample catalog files for test upload?
Sample repository definition is delivered. You can manually create 1 entry by Data Manager.
10.What are the lastest SP for MDM available for integration with SRM 7.0??
You can find it SAP Service Marketplace. http://service.sap.com/swdc
11. after price changes from supplier(thru negotiation),are these price changes to be updated manually for indiavidual items/products through MDM data manager or is there any way to automate this delta update for price in MDM???
You can use contract and contract items are transfered to Catalog.
12.Also maintaining catalog data in MDM for SRM procurement will be a seprate actibity just like maintaing catalog in CCM??
Yes. Catalog is just Catalog.
Regards,
Masa

SRM 4.0 (with SRM Server 5.0) ---- XI 3.0-------R/3

Hello Friends
Iam also working in SRM. I want to integrate SRM and XI for sending a PO from SRM to third party system through XI. I already have a PO created in SRM and I want to send it through XI to Third party system and then want to create corresponding Sales Order in that system.
We are using SRM 4.0(with SRM Server5.0)and XI 3.0.
Thanks in Advance........

Hi <b>Narayana</b>!!
Treat SRM as another R/3 system and use the general flow logic. Create a Sender RFC to send the PO that you have created from SRM system using RFC sender adapter to XI.
Another way:
You can create a work flow which will trigger an IDOC once your PO is created and the IDOC will reach XI using ALE. You need to configure RFC destinations and partner Profiles etc.
Once your PO informations reaches XI you have to configure reciver adapter based on your third Party.
Lets say your third party system is a J2ee application or another R/3 system then you have to configure either a reciver http adapter or a Reciever RFC adapter.
I know this is quite generic......
Cheers!!
AnuraG

OpenText integration with SRM

Hi gurus, I am new here.
I have studied VIM (vendor invoice management) by Opentext by my own during a month, and I am going to start to implement it in a project but I need to integrate VIM with SRM.
I have searched for information but I haven't succeed.
Could you recommend me some web page or tutorial?
Thanks!

Hello,
Purchase Orders exist in ECC backend (as their SRM Confirmations being Goods Receipt in ECC).
Invoice is based on ECC data, that's why i say, for me, there is no link/integration between VIM and SRM: documents used by VIM are the ECC ones.
Regards.
Laurent.

SRM PO's to be printed out with the PO

Hello All,
I have a requirement in my current project wherein the attachments with SRM PO's are to be printed out along with the PO.
In the SAP implementation guide for this it is mentioned that `SAP
delivers a standard implementation with which you can print and fax
attachment documents' and also mentions that to implement the BAdI ie
BBP_DOC_PRINTDOC the requirement is of installing the SAP interface
External Document Converter (XDC) of the SAP component Print and Output
Management (BC-CCM-PRN).
Does this mean i need a third party tool to make this possible or SAP provides a standard with which we can print and Fax attachement documents.
Regards,
Sreejesh

Hi,
here is a SAP document and thread (found in abap general SDN forum) where you should post your question.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/6e33a590-0201-0010-0197-99896fd22cda
XDC - External Document Converter
Kind regards,
Yann

SUS-MM Lanscape with SRM 5.0 as an Add-on with ECC6.0

Similar Messages

Maybe you are looking for