Idoc error (Account vendor no. is currently blocked by user user name )

Hello ,
I am sending a cremas idoc from external system (XI) to R3
But the idoc doesnt get posted.
It throws the following error 51
Account <vendor no.> is currently blocked by user <user name(login id for R3)>
I tried resending this idoc using tcode we19 and was successful in testing it
However, when i try sending it through XI, it gives me the error
Does any one know how this can be solved?
Regards,
Roshani

Hi,
Please make sure that no more screens are open while trying to send the idoc and try again after you get succes from WE19 , It should be posted.
Also check the thread it says in sm12 if there is any lock entry delete it.
Error :Account 1000 is currently blocked by user SAPUSER
Thanks!
Edited by: sudhir tiwari on Nov 21, 2008 1:07 PM

Similar Messages

  • IDOC POsting Error: Transition no. OBJ_SYS is blocked by another user

    Hi Experts,
    I m sending the XML from a third party system into SAP using XI as middleware for IDOC posting (FB01).
    I m getting an error <b>Transition no. <xx> is blocked by another user</b> while sending intercompany and cash applications. SAP is unable to process such XML directly.
    But if i login to SAP and mannually post the IDOC, it is getting posted successfully.
    Any idea what may be the cause?
    Useful answers will be rewarded for sure.
    Regards
    DhanyaR Nair

    Hi Dhanya,
            In your inbound idoc processing program, pls do use the lock mechanism for the FI document which you are processing and if it cannot be locked then keep it on wait for sometime and check for the same.
            If its a standard program check whether it can be done in XI.
          When SAP is locking the transaction it will be unlocked after the commit work and hence its happening.
      The reason why you may not be getting this in individual processing is that you are doing the same thru a single session. And the lock if am not wrong is happening in table level and not in record level.
    Cheers
    JK

  • How to unblock a G/L account which is blocked by a user?

    Hi experts,
    A user has made a posting via T.code F-02.
    When she wants to clear the account via T.code F-03, she gets the message that "account X 0898 is currently blocked by user X.
    Where can I unblock the account.
    Thank you for your feedback.
    Kind regards,
    Linda

    Hi Jaya,
    Thank you.
    This issue dates from last Friday, so no other users are working with this account.
    I think the user has locked the account (maybe by closing not properly the screen).
    How can I take away that lock?
    There is no posting block on the account (no flag on the field posting block in table SKB1).
    Thanks!
    Kind regards,
    Linda

  • Re:'Delivery number is currently being processed by user

    Hi,
      I am creating new delivery based on sales order and assiging craeted delivery to shipment using VL01N and VT01N.Some times getting error as 'Delivery number is currently being processed by user'. I am using synchrounus
    update in BDC.
    Can i use  'Commit work and Wait'  along with synchrounus update in BDC?
    To avoid this error message is there any alternate solution.
    Regards,
    Suresh Kumar.

    i have had the same issues, and niether synchronous update, nor commit and wait work in all cases.
    an option would be to enqueue the delivery in between the two steps.
    create the delivery, then enqueue the delivery (LIKP, i think) with a wait code on it. the system will wait until the first process releases the lock on the delivery and then give it to you. The lock will be discarded when you do a commit after second step, but for readability, i always dequeue.
    this is what we do, and i cannot guarantee it will work for you.

  • Account 1103535 is currently blocked by user ALE_RFC_COMM

    We are receiving this error occasionally when processing CREMAS IDocs. We are receiving the IDoc from PI and processing through ALE. Occurring at the same time we have DEBMAS IDocs coming into the system through Crossworlds being processed by a user defined function module. I am wondering if we are having contention between the two processes? In some cases the vendor number is the same as the customer number but not always.  Can someone please provide some insight?
    Thanks
    Jim

    Hi James,
    Schedule another background for program RBDMANI2 by giving the message type as input for that program.  This program will process the idoc's which have failed during the initial execution.  The error likes currently blocked by user is only at that particular point of time, when your background job executes those sort of error idoc's will be processed and you will not have those things in the error list.
    Usually you get those sort of errors when the jobs are running concurrently and trying to use the same tables.  You can your program as well as it is a custom program, you might have forgot to clear any varibales in that, even if you don't clear the variables properly in the program then also it leads to these sort of errors.
    Thanks,
    Mahesh.

  • "The server responded with an error. The server is currently unreachable or the connection was blocked"

    Hi, since this morning i receive this message on my Mac Air (10.8.5) when i open iCal (which is synced through iCloud): "The server responded with an error. The server is currently unreachable or the connection was blocked". You know what it can be?
    Thanks for your help!

    Are you behind a firewall at work or elsewhere?  Does you calendar sync with some other system like google (could be the google server is not responding)?  All we know from the message is that your mac cannot reach the server.  Maybe try later.  Are you using wifi or have an ethernet connection to the router?

  • IDOC Error V1 042 - Sales document X is currently being processed by user X

    Hello Experts,
    I am using the IS-Retail solution of SAP and I am facing a IDOC Error which keeps the IDOC in Status 51. I traced the Error Message and it was V1 042. I am using an Inbound IDOC 'SHP_OBDLV_CREATE_STO01' to create the STOs (Deliveries) using the POs and there is a locking issue of the PO giving error message 'Sales document XXX is currently being processed by user XXX'.
    I have created a backgroung job using a program to post the STOs using IDOCs that picks up multiple files from Application Server and processes them one by one. Now when 2 or more files use the same PO then this error occus.
    I added a couple of minutes of wait time between the file processing but that did not help.
    Please let me know if you have faces same situation and what solution did you apply.
    Regards,
    PS

    Hopefully you have fixed this by now, but for anyone else who might be looking at this problem.  We had this problem and we had the 2 programs check to see if the other was already runing.  If so the program would submit itself for a number of minutes, different for both programs, and then exit.  We also, and just before this, checked to make sure that there were not 2 of the running programs running and if so to exit.  This was necessary because re-scheduling could put a program in conflict with itself.  I hope that this may help someone.  We used the join V_OP and searched for the program name, not the job name.
    Kevin

  • Idoc : Validation on Vendor and G/L account

    Hi Friends,
    We are having an Ext-Classic Scenario and doing Invoice without reference to PO ; once the invoice is created (w/o r.po) it will generate the Internal Number range ( 81xxx) and once it's approved it triggered the IDoc for ECC to generate the FI doc.51XXXX .
    Couple of records are getting stuck in Idoc in ECC with msg type BBPIV like for G/L account not ready for Tax code or vendor is not confirmed in ECC . Please let me know how to set the Validation on G/l Account / Vendor for Invoice without reference to PO.
    Which BADI can be used .
    Regards,
    Lalit

    Dear HARITH HAMDAN,
    I request you to kindly refer SAP Note 800294, which explains your question on Aging report to be run Back dated.
    Example:
    Today is the 12.12.2007, I need to see the ageing report for open
    customer receivables on 30.11.2007. Between the 30.11.2007 and
    12.12.2007 some of the then open invoices have been paid.
    Reports => Financials -> Ageing -> Customer Receivables Ageing
    Set 'Ageing Date' last date of the period, here 30.11.2007.
    Set 'Posting Date' from '01.01.2007' (= Start of fiscal year) to
    '30.11.2007'.
    Bring tab 'By Journal Postings' into the foreground.
    Tick boxes 'Display Customers with Zero Balance' and 'Consider
    Reconciliation Date'.
    Click on 'OK'.
    This setting will generate an ageing report showing all AR invoices
    posted between 01.01.07 to 30.11.07 that are not reconciled on
    30.11.2007.
    Regards,
    Raghu N
    SAP Business One Forums Team

  • Error:- Account is block for posting

    Dear guru's
    Please help us to resolve this problem as on urgent basis,Your suggestion and solution is really appreciated by us.........
    Error:-  Account 1333 3333 is blocked for posting While Invoice is release to accounting through the transaction code vf02-clicking on releasing flag.please tell me some path from where this error can be resolved
    Thanks and regards
    G.J.Raju
    Sap Consultant

    Goto FSP0, enter the account number and the chart of accounts.
    Goto GL Account -> Block.
    There the field "Block for Posting" might have been set for the GL Account.
    Regards,
    Abhishek

  • Idoc error in AP posting

    Hi Friends,
    We are doing the intercompany transaction and the org structure is as follows -
                                    Supplying                        Receiving
    Company Code           1000                                2000
    Sales Org                   1000                                2000
    Customer                  1000001
                                    (Internal Customer
                                     Receiving)
    Vendor                                                            2000001 (Vendor - Supplying)
    In the process, we do the intercompany billing from company 1000 to 2000, during the intercompany billing there is not output tax is applicable for the 2000 customer.  However when we post the payable posting in receivng company input tax is applicable as X1(Tax code).
    My questions -
    1.  How the tax codes are going to map in OBCG transaction, as i dont have any output tax -
    2.  When i am creating the billing document, system is showing the following error in inbound idoc for account payable posting
    Formatting error message in the field BSEG-GSBER
    For the above problem, i checked the field status of GL and i made business area field as optional but still the problem is persisiting
    Anticipating a positive response
    Best Regards.,
    Goutham

    what is message number and ID ?

  • FI Archiving - System error: Customer/vendor line item not on OI basis

    While archiving FI Documetns using object FI_Documnt, I am getting message System error: Customer/vendor line item not on OI basis for few non archivable documents. Is it like these also open items and can not be able to archive them. Or what is the root cause of these error message.
    Regards,
    Shailesh

    Hi Adisha,
    This error pertains to the accounting fundamentals and SAP does not have anything to do with this....you ask yourself that if you were not using SAP and simlar problem came your way what would you have done...this has no solution...
    Either you wait for the next invoice with big amount but which seems bit impractical..
    In this we really need to consult the Accounting Standards to see what it could allow.
    Regards,
    Chintan Joshi

  • Runtime error - FBL1N - vendor balance with customer line item

    Hi gurus,
    One scenario where i have assign vendor as customer & customer as vendor in vendor & customer data. also make tick mark for both clearing with vendor & customer.
    when i see the customer report with vendor item it shows me the customer & vendor dues but when i tried to see the vendor balance with customer line item it gives dump error.
    Runtime Errors         PERFORM_NOT_FOUND
    Exception              CX_SY_DYN_CALL_ILLEGAL_FORM
    Error analysis
        An exception occurred that is explained in detail below.
        The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_FORM', was
         not caught in
        procedure "%_LDB_CALLBACK" "(FORM)", nor was it propagated by a RAISING clause.
        Since the caller of the procedure could not have anticipated that the
        exception would occur, the current program is terminated.
        The reason for the exception is:
        The program "RSDBRUNT" is meant to execute an external PERFORM,
        namely the routine "CB_DDF_GET_KNA1 " of the program "RFITEMAP ", but
        this routine does not exist.
        This may be due to any of the following reasons:
        1. One of the programs "RSDBRUNT" or "RFITEMAP " is currently being developed.
        The name "CB_DDF_GET_KNA1 " of the called routine may be incorrect, or
        the routine "CB_DDF_GET_KNA1 " is not yet implemented in the program "RFITEMAP
        2. If the program SAPMSSY1 is involved in the runtime error, one of
        the function modules called via RFC is not flagged as remote-capable.
        (see Transaction SE37  Goto -> Administration -> RFC flag)
        3. There is an inconsistency in the system. The versions of the
        programs "RSDBRUNT" and "RFITEMAP " do not match.
    Warm regards,
    Dhananjay R.

    Hi martin
    still problem was not solved. actually i am working on ECC 6.0 & not required to implement the sap note on development. i had done the configuration in vendor master & customer master for clearing.
    please suggest me.....what to do ?
    Than'x
    Dhananjay R

  • IDoc Error

    Hi there
    I am getting the below error at the time of generating an IDoc
    No account for cash management payment advice; FI payment advice: 1000 D 0000100023 06007576
    I thought this must be due to the ''Open item management' being supressed on the GL Master but apparently its not...
    Does anyone have an idea as to why this error might appear?
    Thank you
    Rukshana

    Hi Rukshana,
    This is very strange, I could not find ANY note in all SAP database related to this error message.
    I guess that you have checked in FS00 this account mentioned in the message. Did you try to compare this account master data with another one that it is working? Maybe you will find the reason.
    I am sorry but I do not know why this error happen to you.
    Best Regards,
    Vanessa.

  • Error deleting VHD: There is currently a lease on the blob and no lease ID was specified in the request

    When attempting to delete a VHD's blob you may receive the following error:
    There is currently a lease on the blob and no lease ID was specified in the request
    While these errors are expected if a VHD is still registered as a disk or image in the portal, we have identified an issue where a lease remains even if the blob is not registered as a disk or image in the portal.
    If you receive one of these errors, first make sure the VHD is not in use:
    In the Windows Azure management portal, if the disk shows up under Virtual Machines,
    Disks, and the Attached To column is not blank, you should first remove that VM in the
    Attached To column by going to VM Instances, selecting the VM, then clicking
    Delete.
    If Attached To is blank, or the VM in the Attached To column was already removed, try removing the disk by highlighting it under
    Disks and clicking Delete Disk (this will not physically delete the VHD from blob storage, it only removes the disk object in the portal). If you have multiple pages of disks it can be easier to search for a specific disk by
    clicking the magnifying glass icon at the top right.
    If Delete Disk is grayed out, or the disk is not listed under Disks, but you still cannot reuse it or delete it, review the options below.
    Breaking the lease
    You can use the
    Lease Blob API to break the lease in this scenario, which is also available in the Windows Azure PowerShell assembly
    Microsoft.WindowsAzure.StorageClient.dll using
    LeaseAction Enumeration.
    To use the BreakLease.ps1 script to break the lease:
    Download Azure PowerShell by clicking Install under Windows here:
    http://www.windowsazure.com/en-us/manage/downloads/
    Start, Search, type Windows Azure PowerShell and open that console.
    Run Get-AzurePublishSettingsFile to launch a browser window to
    https://windows.azure.com/download/publishprofile.aspx to download the management certificate in a
    .publishsettings file in order to manage your subscription with PowerShell.
    Get-AzurePublishSettingsFile
    Run Import-AzurePublishSettingsFile to import the certificate and subscription information. Replace the path below with the full path to the .publishsettings file if you didn't save it to your
    Downloads folder. If you saved it to Downloads you can run it as-is, otherwise replace the path with the full path to the
    .publishsettings file.
    Import-AzurePublishSettingsfile $env:userprofile\downloads\*.publishsettings
    Copy the script below into a text editor such as Notepad and save it as
    BreakLease.ps1.
    Run Set-ExecutionPolicy to allow script execution:
    Set-ExecutionPolicy unrestricted
    Run BreakLease.ps1 with the URL to the VHD in order to break the lease. The script obtains the necessary storage account information, checks that the blob is not currently registered as a disk or as an image, then proceeds to break the
    current lease (if any).
    Sample output:
    BreakLease.ps1 -Uri 'http://clstorage.blob.core.windows.net/vhds/testvm1-testvm1-2012-06-26.vhd'
    Processing http://clstorage.blob.core.windows.net/vhds/testvm1-testvm1-2012-06-26.vhd
    Reading storage account information...
    Confirmed - storage account 'clstorage'.
    Checking whether the blob is currently registered as a disk or image...
    Confirmed - the blob is not in use by the Windows Azure platform.
    Inspecting the blob's lease status...
    Current lease status: Locked
    Unlocking the blob...
    Current lease status: Unlocked
    Success - the blob is unlocked.
    BreakLease.ps1
    Param([string]$Uri = $(Read-Host -prompt "Please specify a blob URL"))
    $ProgressPreference = 'SilentlyContinue'
    echo "Processing $Uri"
    echo "Reading storage account information..."
    $acct = Get-AzureStorageAccount | ? { (new-object System.Uri($_.Endpoints[0])).Host -eq (new-object System.Uri($Uri)).Host }
    if(-not $acct) {
    write-host "The supplied URL does not appear to correspond to a storage account associated with the current subscription." -foregroundcolor "red"
    break
    $acctKey = Get-AzureStorageKey ($acct.StorageAccountName)
    $creds = "DefaultEndpointsProtocol=http;AccountName=$($acctKey.StorageAccountName);AccountKey=$($acctKey.Primary)"
    $acctobj = [Microsoft.WindowsAzure.CloudStorageAccount]::Parse($creds)
    $uri = $acctobj.Credentials.TransformUri($uri)
    echo "Confirmed - storage account '$($acct.StorageAccountName)'."
    $blobclient = New-Object Microsoft.WindowsAzure.StorageClient.CloudBlobClient($acctobj.BlobEndpoint, $acctobj.Credentials)
    $blobclient.Timeout = (New-TimeSpan -Minutes 1)
    $blob = New-Object Microsoft.WindowsAzure.StorageClient.CloudPageBlob($uri, $blobclient)
    echo "Checking whether the blob is currently registered as a disk or image..."
    $disk = Get-AzureDisk | ? { (new-object System.Uri($_.MediaLink)) -eq $blob.Uri }
    if($disk) {
    write-host "The blob is still registered as a disk with name '$($disk.DiskName)'. Please delete the disk first." -foregroundcolor "red"
    break
    $image = Get-AzureVMImage | ? { $_.MediaLink -eq $blob.Uri.AbsoluteUri }
    if($image) {
    write-host "The blob is still registered as an OS image with name '$($image.ImageName)'. Please delete the OS image first." -foregroundcolor "red"
    break
    echo "Confirmed - the blob is not in use by the Windows Azure platform."
    echo "Inspecting the blob's lease status..."
    try {
    $blob.FetchAttributes()
    } catch [System.Management.Automation.MethodInvocationException] {
    write-host $_.Exception.InnerException.Message -foregroundcolor "red"
    break
    echo "Current lease status: $($blob.Properties.LeaseStatus)"
    if($blob.Properties.LeaseStatus -ne [Microsoft.WindowsAzure.StorageClient.LeaseStatus]::Locked) {
    write-host "Success - the blob is unlocked." -foregroundcolor "green"
    break
    echo "Unlocking the blob..."
    $request = [Microsoft.WindowsAzure.StorageClient.Protocol.BlobRequest]::Lease($uri, 0, [Microsoft.WindowsAzure.StorageClient.Protocol.LeaseAction]::Break, $null)
    $request.Timeout = $blobclient.Timeout.TotalMilliseconds
    $acctobj.Credentials.SignRequest($request)
    try {
    $response = $request.GetResponse()
    $response.Close()
    catch {
    write-host "The blob could not be unlocked:" -foregroundcolor "red"
    write-host $_.Exception.InnerException.Message -foregroundcolor "red"
    break
    $blob.FetchAttributes()
    echo "Current lease status: $($blob.Properties.LeaseStatus)"
    write-host "Success - the blob is unlocked." -foregroundcolor "green"
    Alternate method: make a copy of the VHD in order to reuse a VHD with a stuck lease
    If you have removed the VM and the disk object but the lease remains and you need to reuse that VHD, you can make a copy of the VHD and use the copy for a new VM:
    Download CloudXplorer. This will work with other
    Windows Azure Storage Explorers but for the sake of brevity these steps will reference CloudXplorer.
    In the Windows Azure management portal, select Storage on the left, select the storage account where the VHD resides that you want to reuse, select
    Manage Keys at the bottom, and copy the Primary Access Key.
    In CloudXplorer, go to File, Accounts,
    New, Windows Azure Account and enter the storage account name in the
    Name field and the primary access key in the Secret Key field. Leave the rest on the default settings.
    Expand the storage account in the left pane in CloudXplorer and select the
    vhds container (or if the VHD in question is one uploaded to a different location, browse to that location instead).
    Right-click the VHD you want to reuse (which currently has a stuck lease), select
    Rename, and give it a different name. This will throw the error
    could not rename…there is currently a lease on the blob… but click
    Yes to continue, then View, Refresh (F5) to refresh and you will see it did make a copy of the VHD since it could not rename the original.
    In the Azure management portal, select Virtual Machines,
    Disks, then Create Disk at the bottom.
    Specify a name for the disk, click the folder icon under VHD URL to browse to the copy of the VHD you just created, check the box for
    This VHD contains an operating system, select the drop-down to specify if it is
    Windows or Linux, then click the arrow at the bottom right to create the disk.
    After the portal shows Successfully created disk <diskname>, select
    New at the bottom left of the portal, then Virtual Machine,
    From Gallery, My Disks, and select the disk you just created, then proceed through the rest of the wizard to create the VM.
    Thanks,
    Craig

    Just to add an update to this, it looks like the namespaces have changed with the latest version of the SDK. I have updated the script to use the new namespaces, namely: Microsoft.WindowsAzure.Storage.Blob.CloudPageBlob and Microsoft.WindowsAzure.Storage.CloudStorageAccount.
    Param([string]$Uri = $(Read-Host -prompt "Please specify a blob URL"))
    $ProgressPreference = 'SilentlyContinue'
    echo "Processing $Uri"
    echo "Reading storage account information..."
    $acct = Get-AzureStorageAccount | ? { (new-object System.Uri($_.Endpoints[0])).Host -eq (new-object System.Uri($Uri)).Host }
    if(-not $acct) {
    write-host "The supplied URL does not appear to correspond to a storage account associated with the current subscription." -foregroundcolor "red"
    break
    $acctKey = Get-AzureStorageKey ($acct.StorageAccountName)
    $creds = "DefaultEndpointsProtocol=http;AccountName=$($acctKey.StorageAccountName);AccountKey=$($acctKey.Primary)"
    $acctobj = [Microsoft.WindowsAzure.Storage.CloudStorageAccount]::Parse($creds)
    $uri = $acctobj.Credentials.TransformUri($uri)
    echo "Confirmed - storage account '$($acct.StorageAccountName)'."
    $blob = New-Object Microsoft.WindowsAzure.Storage.Blob.CloudPageBlob($uri, $creds)
    echo "Checking whether the blob is currently registered as a disk or image..."
    $disk = Get-AzureDisk | ? { (new-object System.Uri($_.MediaLink)) -eq $blob.Uri }
    if($disk) {
    write-host "The blob is still registered as a disk with name '$($disk.DiskName)'. Please delete the disk first." -foregroundcolor "red"
    break
    $image = Get-AzureVMImage | ? { $_.MediaLink -eq $blob.Uri.AbsoluteUri }
    if($image) {
    write-host "The blob is still registered as an OS image with name '$($image.ImageName)'. Please delete the OS image first." -foregroundcolor "red"
    break
    echo "Confirmed - the blob is not in use by the Windows Azure platform."
    echo "Inspecting the blob's lease status..."
    try {
    $blob.FetchAttributes()
    } catch [System.Management.Automation.MethodInvocationException] {
    write-host $_.Exception.InnerException.Message -foregroundcolor "red"
    break
    echo "Current lease status: $($blob.Properties.LeaseStatus)"
    if($blob.Properties.LeaseStatus -ne [Microsoft.WindowsAzure.Storage.StorageClient.LeaseStatus]::Locked) {
    write-host "Success - the blob is unlocked." -foregroundcolor "green"
    break
    echo "Unlocking the blob..."
    $request = [Microsoft.WindowsAzure.Storage.StorageClient.Protocol.BlobRequest]::Lease($uri, 0, [Microsoft.WindowsAzure.Storage.StorageClient.Protocol.LeaseAction]::Break, $null)
    $request.Timeout = $blobclient.Timeout.TotalMilliseconds
    $acctobj.Credentials.SignRequest($request)
    try {
    $response = $request.GetResponse()
    $response.Close()
    catch {
    write-host "The blob could not be unlocked:" -foregroundcolor "red"
    write-host $_.Exception.InnerException.Message -foregroundcolor "red"
    break
    $blob.FetchAttributes()
    echo "Current lease status: $($blob.Properties.LeaseStatus)"
    write-host "Success - the blob is unlocked." -foregroundcolor "green"

  • Unable to refresh the schema of FIM MA.Getting an error in Event viewer ""the current version of database is not compatible with the one expected by Forefront Identity Manager service. The current version of database is : 1116. The expected version is :1"

    Hi,
    We have installed FIM MA with an account that have all the sufficient rights.It got created successfully and worked for Full Import and Full Sync. But, due to some version incompatabilities, we have installed a patch.PFB link for the patch.
    http://support.microsoft.com/en-us/kb/2969673/en-us
    Now, we are trying to refresh the schema of FIM MA. While doing that we are facing an error "Failed to connect to database". The user account with which we are connecting has read and write permissions on DB.In the event viewer some errors are
    logged like  "the current version of database is not compatible with the one expected by Forefront Identity Manager service. The current version of database is : 1116. The expected version is :1122" with event ID 3. PFB images for more detailed
    view.
    Please advice how to fix the issue.
    Thanks
    Prasanthi.

    Hello,
    seems to me that you maybe only updated the syncengine but not portal/webservice.
    I had that error once after an recovery from scratch and forgot one of the hotfixes to apply to all services.
    -Peter
    Peter Stapf - ExpertCircle GmbH - My blog:
    JustIDM.wordpress.com

Maybe you are looking for