ME55 - Release Purchase Request

Hi Gurus,
I am facing problem in T-Code ME55 throwing message by SU53 that authorization obj : M_BANF_FRG and Pur. Req. Release code x9. I have changed Role and assign the said obj. but when i exec. the t-code me55 this execute sucessfully. But there is no pur. req. pending for release. But WhenIi see the same in another login then there are so many pur. req. are pending for release, what will the cause? pl help.
Regards,

Hi,
You have problem only in configuration to the best of my understanding .
If that is not there than in the CL20N where you create master data for release strategy.
Try to do a check why release strategy is not applying by carefully examining the data you have key in.
Don't do too many things at the same time.
I suggest you to check the data.
Also if you don't put the value for any of the release characterstic and that characterstic is assigned to the class Release strategy will not work.
Please refer to SAP Note 207490, 365604 & 493900 for your better understanding.
Regards
Ankur

Similar Messages

Releasing of request number

In how many ways can u release a request number.I know se10,se09,se01. are there any other ways.
Tanks
Raghav

Hi Raghu,
GO to se01, se09 or se10
select your request no.
if not released u can delete it from here.
And,
Do you mean the Purchase requisiton ,then go to ME52
select the line and press the delete button and save.
cheers,
Hema.

Z Report of Transaction ME28.(Release Purchase Order)

Dear all,
               I want to make Z Report for the Transaction ME28 (Release Purchase Order).
I am facing problem of GUI status in my Z Report. Actually Report is not displaying like ME28.
and all the menu and function keys are also not coming properly.
So, pls suggest me good solution.
Thanks & Regards,
Sandip Sonar.

I am attaching a copy of ME28. Please give it to your ABAP consultant.
He should be able to do the needful:
REPORT RM06EF00 NO STANDARD PAGE HEADING MESSAGE-ID ME.
       Anzeigen Einkaufsbelege zur Belegnummer                       *
Tabellen                                                            *
INCLUDE FM06LTO1.
INCLUDE FM06LCFR.
**table added t16fc - SAPBY     6 Feb 98
TABLES: T16FG, T16FS, T16FV, T16FE, RM06B, T160B, T16FC.
DATA: BEGIN OF XEKPO OCCURS 100.
        INCLUDE STRUCTURE EKPO.
DATA: END OF XEKPO.
*- Interne Tabelle der Zustände -
DATA: BEGIN OF ZUS OCCURS 10.
        INCLUDE STRUCTURE T16FV.
DATA: END OF ZUS.
DATA: BEGIN OF ZUSKEY,
         MANDT LIKE EKKO-MANDT,
         FRGGR LIKE EKKO-FRGGR,
         FRGSX LIKE EKKO-FRGSX,
      END OF ZUSKEY.
Parameter und Select-Options                                        *
PARAMETERS:     P_FRGCO LIKE T16FC-FRGCO OBLIGATORY.
SELECT-OPTIONS: S_FRGGR FOR EKKO-FRGGR.
PARAMETERS:     P_FRGSE LIKE RM06A-P_FRGSE DEFAULT 'X',
                P_FRGRS LIKE RM06A-P_FRGRS,
                P_FRGVO LIKE RM06A-P_FRGVO DEFAULT 'X',
set default to 'X' to show items as well - SAPBY
                P_MITPOS AS CHECKBOX DEFAULT 'X',
set default to 'DEFAULT' - SAPBY
                LISTU LIKE T160O-LISTU DEFAULT 'DEFAULT'.
SELECT-OPTIONS: S_BSTYP FOR EKKO-BSTYP,
                S_EKORG FOR EKKO-EKORG,
                S_EBELN FOR EKKO-EBELN MATCHCODE OBJECT MEKK
                                       MEMORY ID BES,
                S_BSART FOR EKKO-BSART,
                S_EKGRP FOR EKKO-EKGRP,
                S_LIFNR FOR EKKO-LIFNR MATCHCODE OBJECT KRED,
                S_RESWK FOR EKKO-RESWK,
                S_BEDAT FOR EKKO-BEDAT.
Hilfsfelder                                                         *
INCLUDE FM06LCEK.
DATA: XFRG1 LIKE EKKO-FRGZU,
      XFRG2 LIKE EKKO-FRGZU.
DATA: XSELKB LIKE EKKO-BSTYP,
      XSELKK LIKE EKKO-BSTYP,
      XSELKL LIKE EKKO-BSTYP,
      XSELKA LIKE EKKO-BSTYP.
FIELD-SYMBOLS: .
DATA: HFDPOS LIKE SY-FDPOS.
**workflow line added for workflow
DATA : LAST_USER_COMMAND LIKE SY-UCOMM.
Intitialisierung                                                    *
INITIALIZATION.
PERFORM ANFORDERUNGSBILD(SAPFM06L) USING XSELKB XSELKK
                                           XSELKL XSELKA.
lines 67, 70 and 73 commented out -SAPBY
**listu = t160b-listu.
S_BSTYP-SIGN = 'I'.
S_BSTYP-OPTION = 'EQ'.
**if xselkb ne space.
S_BSTYP-LOW = 'F'.
APPEND S_BSTYP.
**endif.
IF XSELKK NE SPACE.
    S_BSTYP-LOW = 'K'.
    APPEND S_BSTYP.
ENDIF.
IF XSELKL NE SPACE.
    S_BSTYP-LOW = 'L'.
    APPEND S_BSTYP.
ENDIF.
IF XSELKA NE SPACE.
    S_BSTYP-LOW = 'A'.
    APPEND S_BSTYP.
ENDIF.
next two lines added to default the release code
IMPORT T16FC-FRGCO FROM MEMORY.
get parameter id 'ZRC' field t16fc-frgco.
P_FRGCO = T16FC-FRGCO.
Seketionsbild                                                       *
AT SELECTION-SCREEN ON LISTU.
PERFORM LISTUMFANG(SAPFM06L) USING LISTU.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FRGCO.
CALL FUNCTION 'HELP_VALUES_FRGAB'
       EXPORTING
            I_FRGOT = '2'
       IMPORTING
            E_FRGAB = P_FRGCO
       EXCEPTIONS
            OTHERS = 1.
AT SELECTION-SCREEN.
CALL FUNCTION 'ME_REL_CHECK_MANY'
       EXPORTING
            I_FRGOT = '2'
            I_FRGCO = P_FRGCO
       TABLES
            T_FRGGR = S_FRGGR
            T_T16FV = ZUS.
Beginn der Selektion                                                *
START-OF-SELECTION.
NOT_FOUND = 'X'.
SET PF-STATUS 'FREI'.
SET TITLEBAR '001' WITH P_FRGCO.
PERFORM FRG_INIT(SAPFM06L) USING P_FRGCO P_MITPOS.
*- Lesen Belegköpfe -
SELECT * FROM EKKO APPENDING TABLE XEKKO
                     FOR ALL ENTRIES IN ZUS
                     WHERE FRGRL EQ 'X'
                       AND FRGGR EQ ZUS-FRGGR
                       AND FRGSX EQ ZUS-FRGSX
                       AND EBELN IN S_EBELN
                       AND BSTYP IN S_BSTYP
                       AND EKORG IN S_EKORG
                       AND LIFNR IN S_LIFNR
                       AND RESWK IN S_RESWK
                       AND BEDAT IN S_BEDAT
                       AND BSART IN S_BSART
                       AND EKGRP IN S_EKGRP
                       AND LOEKZ EQ SPACE.
IF P_FRGRS NE SPACE.
    SELECT * FROM EKKO APPENDING TABLE XEKKO
                       FOR ALL ENTRIES IN ZUS
                       WHERE FRGRL EQ SPACE
                         AND FRGGR EQ ZUS-FRGGR
                         AND FRGSX EQ ZUS-FRGSX
                         AND EBELN IN S_EBELN
                         AND BSTYP IN S_BSTYP
                         AND EKORG IN S_EKORG
                         AND LIFNR IN S_LIFNR
                         AND RESWK IN S_RESWK
                         AND BEDAT IN S_BEDAT
                         AND BSART IN S_BSART
                         AND EKGRP IN S_EKGRP
                         AND LOEKZ EQ SPACE.
ENDIF.
SORT XEKKO.
*- Prüfen Freigabevoraussetzungen -
LOOP AT XEKKO.
    MOVE-CORRESPONDING XEKKO TO ZUSKEY.
    READ TABLE ZUS WITH KEY ZUSKEY BINARY SEARCH.
    CHECK SY-SUBRC EQ 0.
    XFRG1 = ZUS+9(8).
    XFRG2 = XEKKO-FRGZU.
    TRANSLATE XFRG2 USING 'X +'.
    OVERLAY XFRG1 WITH XFRG2 ONLY '+'.
    SEARCH XFRG1 FOR 'X'.
*---- Keine Freigabezuständigkeit -
    IF SY-SUBRC NE 0.
      DELETE XEKKO.
    ELSE.
*---- Freigabestelle merken -
      HFDPOS = SY-FDPOS.
      ASSIGN XFRG2+SY-FDPOS(1) TO .
*---- Freigabe bereits erfolgt -
      IF P_FRGRS EQ SPACE AND
          EQ SPACE.
        DELETE XEKKO.
      ELSE.
*---- Freigabe noch nicht erfolgt -
        IF P_FRGSE EQ SPACE AND
            NE SPACE.
          DELETE XEKKO.
        ELSE.
*---- Freigabevoraussetzung fehlt -
          IF XFRG1 CA '+' AND
             P_FRGVO NE SPACE.
            DELETE XEKKO.
          ELSE.
            EKKO = XEKKO.
            PERFORM FRG_FEKKO_AUFBAUEN(SAPFM06L) USING HFDPOS.
          ENDIF.
        ENDIF.
      ENDIF.
    ENDIF.
ENDLOOP.
SORT XEKKO.
*- Lesen Belegpositionen -
IF P_MITPOS NE SPACE.
    SELECT * FROM EKPO APPENDING TABLE XEKPO
                       FOR ALL ENTRIES IN XEKKO
                       WHERE EBELN EQ XEKKO-EBELN.
ENDIF.
*- Ausgabe -
LOOP AT XEKKO.
    EKKO = XEKKO.
    PERFORM EKKO_ANSCHRIFT(SAPFM06L).
    PERFORM EKKO_AUSGABE(SAPFM06L).
    IF P_MITPOS NE SPACE.
      LOOP AT XEKPO WHERE EBELN EQ EKKO-EBELN.
        EKPO = XEKPO.
        PERFORM FC_ME_READ_HISTORY(SAPFM06L).
        PERFORM EKPO_AUSGABE(SAPFM06L).
      ENDLOOP.
    ENDIF.
ENDLOOP.
Ende der Selektion                                                  *
END-OF-SELECTION.
IF NOT_FOUND NE SPACE.
    MESSAGE S260.
    IF SY-CALLD NE SPACE.
      LEAVE.
    ELSE.
      LEAVE TO TRANSACTION SY-TCODE.
    ENDIF.
ENDIF.
WRITE: /(81) SY-ULINE.
OK-Code-Eingabe                                                     *
AT USER-COMMAND.
**workflow inserted 6 Feb 98 by SAPBY
    PERFORM WORKFLOW_AT_USER_COMMAND.
INS GSB 18/02/2004 - check user approving is not user that create
PO
if sy-ucomm = 'FRGU' or sy-ucomm = 'FRGS'.
loop at xekko.
if xekko-ERNAM = sy-uname.
     CALL FUNCTION 'POPUP_TO_DISPLAY_TEXT'
       EXPORTING
         TITEL              = 'Error'
TEXTLINE1 = 'As the creator of this pruchase order you cannot approve it
as well !'
    leave program.
endif.
endloop.
endif.
PERFORM USER_COMMAND(SAPFM06L).
Seitenueberschrift                                                  *
TOP-OF-PAGE.
PERFORM TOP(SAPFM06L).
TOP-OF-PAGE DURING LINE-SELECTION.
PERFORM TOP(SAPFM06L).
**& form workflow_at_user_command
TEXT
---> p1 text
<-- p2 text
FORM WORKFLOW_AT_USER_COMMAND.
IF LAST_USER_COMMAND IS INITIAL.
    LAST_USER_COMMAND = SY-UCOMM.
ENDIF.
IF SY-UCOMM EQ 'ZURU'.
     PERFORM TRIGGER_WORKFLOW.
ENDIF.
CASE SY-UCOMM.
    WHEN 'BU'.
      IF P_MITPOS EQ 'X'.
        CHECK LAST_USER_COMMAND <> 'FRGR'.
        PERFORM TRIGGER_WORKFLOW.
      ELSE.
        CHECK LAST_USER_COMMAND = 'FRGS'.
        PERFORM TRIGGER_WORKFLOW.
      ENDIF.
    WHEN 'FRGU'.
      PERFORM TRIGGER_WORKFLOW.
ENDCASE.
LAST_USER_COMMAND = SY-UCOMM.
ENDFORM.
**& form TRIGGER_WORKFLOW.
TEXT
---> p1 text
<-- p2 text
FORM TRIGGER_WORKFLOW.
DATA : BEGIN OF ZEKKO OCCURS 20.
          INCLUDE STRUCTURE ZEKKO.
DATA : END OF ZEKKO.
DATA : BEGIN OF YEKKO OCCURS 20.
          INCLUDE STRUCTURE ZEKKO.
DATA : END OF YEKKO.
DATA : WFBAN LIKE EKKO-EBELN,
       WFERN LIKE EKKO-ERNAM.
CLEAR : WFBAN, WFERN.
MOVE-CORRESPONDING XEKKO TO YEKKO.
CONCATENATE YEKKO-FRGZU 'X' INTO YEKKO-FRGZU.
APPEND YEKKO.
MOVE-CORRESPONDING XEKKO TO ZEKKO.
*XEKKO-KZ = 'F'.
APPEND ZEKKO.
SELECT SINGLE KOKRS KOSTL
     INTO (EKKN-KOKRS, EKKN-KOSTL)
     FROM EKKN
     WHERE EBELN = XEKKO-EBELN
     AND EBELP   = '00010'.
if sy-subrc <> 0.                  " Cost centres not mandatory at XXX
exit.
endif.
CALL FUNCTION 'Z_ME_REL_EVENT_EKKO'
     EXPORTING
          I_CALL_UPDKZ = 'F'
          I_WFBAN      = EKKO-EBELN
          I_FRGCO      = T16FC-FRGCO
          I_ERNAM      = SY-UNAME
          I_UCOMM      = SY-UCOMM
     TABLES
          I_EKKO_NEW   = YEKKO
          I_EKKO_OLD   = ZEKKO.
ENDFORM.

EhP 5 New function, sharing template of Purchase Request or Purchase Order

Hi Experts,
From SAP ERP MM EhP 5, we can create, save and load " template " of Purchase Request or Purchase Order.
This is discribed on SAP release note of EhP 5 "LOG_MM_CI_3: Public Templates in Purchase Orders and Requisitions".
Does someone know whether this public document template is shared cross company codes, cross clients?
Best regards,
Tadasuke

Hi Tadasuke,
Maybe here you can get some info
https://websmp107.sap-ag.de/erp-ehp
Regards

WF: mail to user for purchase request and purchase order

Hi all,
I activated the WF for released of purchase request and purchase order and the system correctly send mail to the user, but not only one, seven mail for purchase request released...
Is there a possibility for sending mail only time?
Thanks!
Best regards,
Gaetano

can you please check the parameters you have maintained for the report which is used for generating the mails?
please maintain the flag --> one mail for workitem --> and let me know the system response.

ME51(2/3/4)N Reset release purchase requisition

Hello,
I need to reset the issue of the purchase request after a specific condition occurs.
To reset the issue I found the user exit EXIT_SAPLMEREQ_010
(Includes ZXM02U12 MEREQ001 and extension).
I first used this function:
      CALL FUNCTION 'ME_REL_STRATEGIE_EBAN'
         EXPORTING
            i_eban_new           = wa_im_eban
           I_EBAN_OLD          = IM_T_EBAN_PERS
           I_EBKN_NEW          = IM_T_EBKN
           I_EBKN_OLD          = IM_T_EBKN_PERS
          I_XCLASS             =
          I_CHANGE_OK          =
          I_CHECK_ALWAYS       =
         IMPORTING
           E_EBAN                = wa_eban
           E_RESET               = wa_ereset
but I did not understand how to use it.
Then I used the field-symbol:
DATE f_FRGKZ (30) VALUE '(SAPLMEREQ) EBAN-FRGKZ'.
FIELD-symbols <FRGKZ>.
ASSIGN (f_FRGKZ) TO <FRGKZ>.
        MOVE 'X' TO <FRGKZ>.
But a dump is generated on the move: Error at assignment: overwritten protected field.
HELP ME - I don't know what to do.
Edited by: Ermelinda86 on Jul 8, 2010 10:36 AM

Hi Ermelinda86,
I had a problem similar to what you're experiencing. I solved by changing appropriately customizing.
The route from the transaction "spro" is as follows:
Material Management --> Purchasing ---> Purchase Requisition ---> Release Procedure -
> Procedure with classification ---> Set Up procedure with classification -
> Release Indicator
Material Management --> Purchasing ---> Purchase Requisition ---> Release Procedure -
> Procedure with classification ---> Set Up procedure with classification -
> Release Strategies ---> Release Statuses
I also found a useful guide at this link:
http://www.sap123.com/a/59/
Bye
Prode

Purchase request referring to a deleted purchase order

Hi,
I'm working at a release upgrade from 4.6 to ECC 6.0 and I'm facing the following issue.
I created a purchase order referring to a purchase request.
Although I've deleted the purchase order, its number is still displayed in the purchase request.
Instead in the previous release 4.6c, after having deleted the purchase order, its number disappeared.
Do you know how to solve this different behaviour?
Thanks!

Ciao Elisa,
If PO item was delete, system will update the PO qty in PR statistics with ZERO. And appear information to advise this item has been opened. But 'Processing stat' will still keep 'B' - Ordered.
For your reference, please also kindly review the note 493315
FAQ: Purchase requisition (general) -> question 1
~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~
1. You delete a purchase order item with reference to the purchase requisition. Why is the last purchase order in the purchase requisition not reset and why is processing status "B" not changed?
Answer:
See Note 65839.
"This is actually not an error. This is because checks for whether a purchase requisition has already been completed are always made on the basis of the quantity ordered. The processing status and the last purchase order are not used in this case.
Thus the processing status and the last purchase order are not reset, since it very often occurs that purchase requisitions are completed via several purchase orders - that is, they are partially ordered several times. In this case, it would even be completely incorrect to reset the status when deleting the last purchase order item, since the previous purchase order can still exist.
However, since the program no longer has this information, namely, which purchase order is the last active one, the processing status is left on "B" and the purchase order number is not corrected, because this could only cause "even more incorrect" statistics."
Regards,
Mauro

Purchase Request cration

Hi friends,
Is it possible to create Purchase request with refernce to Request for Quotation? Client required PR approval after price updation. Price updation will be done tru RFQ. Please confirm
Rgds
Madhavan

hi
>Is it possible to create Purchase request with refernce to Request for Quotation?
no it is not possible as in cycle u wil find the pr and then rfq ,
also as the reqisition is the first document in the procurement cycle it is prepared by the end user.
>Client required PR approval after price updation. Price updation will be done tru RFQ. Please confirm
now u can set the RFQ release seperately ,no need for pr release
then make the field of RFQ no as mandetory in PO
regards
kunal

Release purchase requsition

Dear All,
Company activated release procedure for purchase requisitions but release procedure is not working when we add one more line item in a released purchase requisition # .
Release Indicator details field changes after release process set as "4".
please advise me to solve this issue.
tks/rajesh.

hi,
please see below indicators are used for release statuses in release strategy.
Release ID          Description
1                   Request for quotation
2                   RFQ/purchase order
3                   RFQ/PO no change of date
4                   RFQ/PO no changes
A                   Fixed RFQ
B                   Fixed RFQ/purchase order
X                   Blocked
please confirm which one i have to choose as such threy are used below indicators
R1 R2 R3                Release indicator
                         X Blocked
                         2 RFQ/purchase ord
                         X Blocked
                         2 RFQ/purchase ord
tks/rajesh

Workflow for Purchase request

Hi all,
I would be glad, if someone can let me know weather SAP B1 9.0 supports purchase request object in Workflow.
If yes let me know the process.
Regards,
Neslin

Hi Aarya,
Check whether approver 1 can release PR for approver 2 and approver 3 with normal ME54N transaction. If yes, then its an issue of authorization.
Check out the authorization object M_EINK_FRG in user profile in this case. I think the authorization for release codes assigned to approver 2 and 3 is given to approver 1.
Nikhill

Who released purchase requisition

Hello,
is there a way to find out the user name who released a purchased requisition?
Thanks
Anne

hi
goto the PR
then in environment select item changes
there u will find the changes with t code ME55 (release )
from there u will get the user id who changed the PR status to released in transaction me55
regards
kunal

Subcontracting Purchase Requestion

All
Assume i have the following two material masters.
1. Raw nut - Material Master valuation price Rs.10 per Kg. (Raw material)
2. Treated nut - Material master valuation price Rs. 12 per Kg. (Semi finished product).
Please note that charges for making a treated nut is say Rs.2 per kg and this will be done by the subcontractor and we supply the raw nuts to him.
I am making a subcontracting purchase requestion for say 10 kg of Treated nut and in the component i have added the Raw nut . The problem is the PR took the valuation price as Rs.12 per kg and determining the release strategy based on this price. It is misleading. The actual price i am going to pay to the subcontracting vendor is the cleaning charges of Rs.2 per kg, but the PR took Rs.12 per kg and therefore the total price of the PR become very high and it needs to be released by the high authority. Say for 1000 kg, the total price become 12000
The PO is working fine. In PO we have subcontracting info record, and the PO took the price this info record .i.e. Rs.2 per kg and the total price of the PO shows only 2000.
Can you please let me know how correct this in the PR..? My PR release strategy should set for only Rs.2000 and not for 12000 in this case. Appriciate your help.
Thanks upfront.
Venkat.

Hi Venkatachalam,
System will always propose the Material Master Valuation price. Even if you have entered infor record in pr.
You have only two options
What you can do is change the valuation price in pr manually whenever you create pr.
Or
Setup a seperate release strategy with subcontracting document type.
Reg,
Ashok
Reward if useful

Source of supply for Service Purchase request. ESM

Source of supply for Service request.
In the customizing for external source of supply, I am making the customizing at client level
SPRO (IMG) -> Materials Management -> External Services Management ->
Source Determination and Default Values -> for Client
In Source determination I have checked the customizing to consider
A. Material group at item level
B. And I am also selecting one of the 3 below at service level.
1.     All service
2.     At least one service
3.     No search at service level
Issue is, the source list I get in ME51N for a given purchase request item is considering only the material group customizing.
I do not see any change in the source list out of making change in the customizing at service level(Customizing B above).
So, is there any other customizing or other case which determines the list.
In short , I am getting same result in the source list irrespective of the customizing I do at service level (Customizing B above).

Hello David,
System assign only one supplier for one PR and even with the quota arrangement also if you have multiple proposals then the system assign the same supplier for all the proposals this is standard behavior you can add this to ideas forum.
kindly submit it to SAP via the SAP Idea Forum.
- Open the Help on the too right of the system.
- Click "Make SAP Business ByDesign better", it
will lead you to the idea forum.
- Submit your new feature in the forum. SAP will review your
new feature requests form customers or partners and plan it in the future
releases after valuation.
Regards,
Suresh.

Status - discussion on Purchase Request

Hello All
Can any one explain in details on status of Purchase request ?
Header as well as Item status -Purchase request
Muthu

Hi Muthu,
Now that i get to see your question more clearly, let me explain it to you.
Now the scenario is between Plant Maintenance and Materials Management. What you are saying is, when a PM Order with PM02/PM03 is control key is created, it will create a Purchase Requisition.
This is correct and in this case, the direct owner or controller is the Plant Maintenance Order itself. If you notice, when you release the Order, then only the PR is generated? And when you Teco the Order, the PR line items are automatically deleted? This is to prevent future creation of Purchase Orders based on PR when the Order is already closed.
For cases like these, involving both PM and MM, the owner is the Order, you cannot do the changes in PR. You have to do the changes in the Order. By doing so, the PR will be updated automatically.
So the status that i thought you were talking about in the first place is irrelevant. That is just showing the status of the PR in a different term. It is showing the status of PR if, it has been converted to a PO, RFQ, etc.
Hope this clears things for you.

How to release Purchasing document

HI ALL :
can anyone help me ? thanks a lot

Hi,
Release Purchasing Documents on following T.codes:
For PR :ME54N,ME55,
For RFQ:ME45,
For PO:ME28,ME29N
Regards,
Biju K

ME55 - Release Purchase Request

Similar Messages

Maybe you are looking for