BBP_LOCATIONS_GET_ALL

Hi all
We are using BBP_LOCATIONS_GET_ALL program but this error occurs:
"Error Accessing System R3_D113" (Message no. BBP_LOCATION001).
We check the RFC and it's OK (we test in SM59)
We check the names of logic systems and it's OK
We already test with:
BBP_LOCATIONS_GET_FROM_SYSTEM / BBP_LOCATIONS_GET_SELECTED and it's the same trouble.
Obviously there are a lot of plants in backend.
We have: SAP SRM 5.00
Soft Comp - Highest Support Package
SAP_ABA - SAPKA70015
SAP_BASIS - SAPKB70015
PI_BASIS - SAPKIPYJ7F
ST-PI - SAPKITLQI5
SAP_BW - SAPKW70017
SAP_AP - SAPKNA7012
SRM_PLUS - SAPKIBK012
SRM_SERVER - SAPKIBKT12
And we have: R/3 Release 4.6C
Some ideas?
10x
Pp

Check the authorizations of the RFC user.  It should have wide authorizations to create the business partner in SRM.
SM59 check is a technical connection check.  It doesn't check lot of authorizations which the SRM application requires for different transactions.
If all the authorizations are correct, it sholud not have any issue, we did hundereds of plants replication on SRM 5 and SRM 6 also.  It doesnt have any issues.
DV

Similar Messages

  • Error BBP_LOCATIONS_GET_ALL

    We have SRM 4.0 and R/3 4.6
    We modify a plant u201CAssign plant to company codeu201D in MM, this modification is due to transmit to SRM.
    When we executed the program BBP_LOCATIONS_GET_ALL, the system sends dump of run time:
    - The termination occurred in the ABAP program "SAPLBBP_PDH" in "ADD_LOCATION". The main program was "BBP_LOCATIONS_GET_ALL".
    In trx SLG1 the process is done with warning and messages appears with u201Clocations already existsu201D.
    However, in the tab of Extended Attributes, Locations, the modifications realized in the plant in R/3 are not visualizes in SRM.
    What append?
    Any advice?

    Hi
    learnty that you have re-assigned the plant to diffrent company code in r/3.
    but in srm when you first replicated plant made entry in bbp_locmap with company code and plant combinations.
    can you delete BP entry via bupa_test_delete and try to pull the plant again to srm and map the plant with r/3. test first in testing system. it is not a good practice to do this reassignment.
    regards
    Muthu

  • Error - Start Program BBP_LOCATIONS_GET_ALL

    Dear All,
    Iam getting this Error - Start Program BBP_LOCATIONS_GET_ALL , when iam trying to display already existing org.unit in PPOSA_BBP.
    What all the prequistes to be checked before running this BBP_LOCATIONS_GET_ALL programme , or any other alternative to solve this error.
    Thanks & Regards,
    Gopal

    Gopal,
    Try to run report BBP_ATTR_XPRA400. This report does the conversion all the organisation structure attributes. Also report BBP_LOCATION_MIGRATION_SET will unlock your plant replication program, if there exists one.
    PLease assign points for helpfull answers
    Thanks
    Sundeep

  • Start program BBP_LOCATIONS_GET_ALL first Error

    Hi, Friends,
    I am new to SRM, and facing some problem with shopping cart.
    First I have created a user with SU01, then given the role of  mySAP SRM Operational Purchaser.
    After that using Tcode users_gen and Create Users from Existing SU01 Users I have generated EBP user for that user.
      Then in the mySAP portal I cant use any steps including Shop, Check Status, Approval or anything else.
    When I clicked the settings then I got this massage :
    Note
    The following error text was processed in the system EBI : Start program BBP_LOCATIONS_GET_ALL first (see Note 563180 and long text)
    The error occurred on the application server dewall41_EBI_00 and in the work process 0 .
    The termination type was: ABORT_MESSAGE_STATE
    The ABAP call stack was:
    Form: CHECK_MIGRATION_RUN of program SAPLBBP_LOCATION
    Function: BBP_LOC_ATTR_V5502A_COMPLETE of program SAPLBBP_LOCATION
    Method: ATTRIBUTES_READ_LOCAL_5502 of program CL_BBP_ATTR_SCENARIO==========CP
    Method: ATTRIBUTES_READ_LOCAL of program CL_BBP_ATTR_SCENARIO==========CP
    Function: RHGA_READ_ATTRIBUTES_EXT of program SAPLHRBAS00GENATTR_RUNTIME
    Form: READ_ATTRIBUTES_EXT of program SAPLBBP_ATTR_PDORG
    Function: BBP_ATTR_MAINT of program SAPLBBP_ATTR_PDORG
    Form: ATTR_READ of program SAPLBBP_UM_UI
    Module: INIT_TRANSACTION of program SAPLBBP_UM_UI
    Please Help.
    Regards Amit.

    Hi Amit,
    Here are the details given in the OSS Note:
    Summary
    Symptom
    Locations as of EBP 4.0 - plant replication
    As of EBP 4.0, a business partner of type location must exist for every R/3 plant; for this reason, the plants must be replicated from all R/3 Backend systems known in the system.
    The system does not start an EBP application before the replication has not been executed successfully; the program terminate themselves and the system refers to this note with an error message.
    If you upgrade from BBP 2.0B or BBP 2.0C, you must first convert the old 'Shopping carts' so that the program plants described here can convert to locations. Use the BBP_TRANSFORM_SCS report for the conversion (see also note 481100).
    Process:
    The replication must be explicitly triggered by means of program BBP_LOCATIONS_GET_ALL.
    This program checks first whether the system in question is an upgrade system, and if necessary it checks whether XPRA BBP_ATTR_XPRA400 was terminated with errors (in this case, BBP_LOCATIONS_GET_ALL terminates and has to be restarted after a successful run of the XPRA).
    After the XPRA check, the system determines from table BBP_BACKEND_DEST all backend systems that can be accessed by RFC.
    Then the system reads all locations already existing in the EBP in order
    to convert any existing data in a legacy system
    to obtain comparison values to avoid duplicate records (identical data records with different partner numbers)
    Then the system imports the data for the plants from all back end systems determined before, compares them with the existing master records and either adds mapping entries or generates new business partners accordingly.
    In upgrade systems the following activities are also carried out:
    Conversion of the favorites (user-specific values for the last used business partners of the type location from table BBP_GRCPLANT_FAV)
    Conversion for user attributes WRK and REQUESTER (the business partner number is added to attribute WRK, the logical backend system is added to attribute REQUESTER)
    Conversion of the legacy documents (an entry with partner function 'Location' must be added to references 'Backend plant'; entries with business partner of type location as the ship-to party must be deleted and also an entry with partner function 'Location' must be added)
    If all subtasks could be executed without errors, the program finally sets the transaction authorization (that is, as of this time it is possible to start 'normal' EBP transactions as, for example, the shopping cart, again).
    The transaction authorization consists of a 'switch' in table T77S0 (GRPID = EBP and SEMID = LMIGR) which is delivered with value '0'.
    As long as this value is not set to 'X', all EBP transactions terminate themselves.
    Success/warning/error messages in program BBP_LOCATIONS_GET_ALL are stored in application log BBP_LOCATIONS_GET (Transaction SLG1).
    Setting the transaction authorization manually:
    The customer can decide to set the 'switch' in table T77S0 to 'X' and to allow the work start under the following circumstances:
    Only one error has occurred, this should be ignored
    One of several back ends broke down during an upgrade or during an installation, and a postponement of the system start cannot be allowed.
    Troubleshooting is not possible/required.
    This is only a local scenario (which should actually not exist because at least an FI R/3 Backend system should exist) so that a replication of plants is not possible.
    For this purpose, program BBP_LOCATION_MIGRATION_SET is availbale which sets required value 'X' in table T77S0 (if the program was started inadvertently, the original value can be restored using BBP_LOCATION_MIGRATION_RESET).
    If the replication from a backend system could not be executed it is possible to repeat this step at a later time via program BBP_LOCATIONS_GET_FROM_SYSTEM for exactly this R/3 system.
    If only single plants cannot be replicated (for example due to inadequately maintained data), they can be copied to the EBP after being revised with program BBP_LOCATIONS_GET_SELECTED (the program can also be used during normal operation to transfer new plants to locations).
    You can also create individual locations via the Web transaction 'Managing Business Partners' and assign them to an R/3 plant.
    Other terms
    Location, business partner, delivery point, plant, component, procurement, Business-to-Business, Ecommerce, e-commerce, Web, SAP Business-to-Business Procurement BBP, Business to Business, electronic commerce, e-business, Ebusiness, Internet, New Dimension, EBP, SAP Enterprise Buyer, Enterprise Buyer professional edition, SRM, Supplier Relationship Management
    Reason and Prerequisites
    IMPORTANT:
    This note does not apply to your R/3 system
    It only applies to EBP 4.0 and higher
    For upgrades from BBP2.0B and BBP2.0C, you must first execute the BBP_TRANSFORM_SCS report (Note 481100)
    Solution
    Proceed as described above.
    Header Data
    Release Status: Released for Customer
    Released on: 25.07.2005  06:48:45
    Master Language: German
    Priority: Recommendations/additional info
    Category: Upgrade information
    Primary Component: SRM-EBP-ADM-XBP External Business Partner
    Secondary Components: SRM-EBP-SHP Shopping Cart
    Affected Releases
    MDM 200 200 200  
    COM_CRMMDM 40 4.0 4.0  
    UIFRW 40 4.0 4.0  
    SRM_SERVER 500 500 500 X
    SRM_SERVER 550 550 550 X
    SRM_SERVER 600 600 600 X
    SRM_SERVER 700 700 700 X
    CGVMIC 10 100 100  
    BBPCRM 4.0 400 400 X
    Related Notes
    872533 - FAQ: Middleware
    737800 - Enhancements to upgrade on SAP CRM 4.0 SR1
    618400 - Support Package 01 for SRM 3.0
    481100 - EBP: Upgrade to Release 3.0A: Conversion of shopping carts
    Thanks,
    Pradeep

  • Defining job BBP_LOCATIONS_GET_ALL using SA38

    I have defined a job using SA38  and th eprogram is "BBP_LOCATIONS_GET_ALL". the job status is Released and then changing to Cancelled. It is never taking the status Finished.
    Any help is appriciated.
    Thanks,
    Eswar

    Hi,
       Maintain an entry in <b>SPRO>SRM server>technical basic settings-->Define backend systems</b> for your R/3 system.
    BR,
    Disha.
    Pls reward points for useful answers.

  • BBP_LOCATIONS_GET_ALL deletes plants in PPOMA

    Hi all.
    SRM 4.0, backend ECC 6.0, extended classic scenario.
    We schedule a batch run every day where the locations are all the time updated using the BBP_LOCATIONS_GET_ALL step. However, I have noticed that several of my locations in PPOMA seem to disappear on a daily basis, so I removed the BBP_LOCATIONS_GET_ALL step from the batch - and now my plants do not disappear anymore.
    Have you guys seen this type of behaviour before that the program BBP_LOCATIONS_GET_ALL can actually delete plants from PPOMA? I cannot find any pattern as to which plants it deletes, but it seems to be plants in organizational units where several plants are maintained.
    Thanks for info.

    Hi
    <b>Looks like a bug in the system.. Which SRM version are you using ?</b>
    <u>Please see some other related SAP OSS Notes -></u>
    Note 927536 Problems w/ plants during EBP3.0/3.5 upgrade to SRM server 
    Note 933939 Problems w/ plants during upgrade EBP3.0/3.5->SRM Server (2)
    Note 771934 Problems with locations: BBP_LOCATIONS_GET_ALL
    Note 811408 Replication (vendor/plant) from R/3 Release 4.7
    Note 690619 Plants are not transferred during location replication
    Note 563180 Locations - Replication of R/3 plants
    Note 501935 Delta download of plants via business object DNL_PLANT
    Note 887102 Error message concerning locations after SRM4.0 upgrade
    <u>Hope this will definitely help. Do let me know in next reply.</u>
    Regards
    - Atul

  • Difference between DNL_Plant and BBP_locations_get_all

    Hi friends
    what is the difference between DNL_Plant and BBP_locations_get_all
    thanks a lot
    Regards
    VinayKrishna

    Hi,
    Program  BBP_LOCATIONS_GET_ALL  is used to  get all the plants in the R/3 backend system to SRM.
    DNL_PLANT is a business object you can see in  trascn R3AC for delta download of plants
    See these related  notes:
    Note 501935 - Delta download of plants via business object DNL_PLANT
    Note 563180 - Locations - Replication of R/3 plants
    BR,
    Disha.
    Do reward points for useful answers.

  • BBP_LOCATIONS_GET_ALL vs BBP_LOCATIONS_GET_SELECTED

    Hi All ,
    We are trying to replicate Plants from ECC to SRM . There are some Plants which are not relevant for SRM perspective, hence we are planning to replicate ONLY plants that are required in SRM using report(BBP_LOCATIONS_GET_SELECTED).
    If we use BBP_LOCATIONS_GET_SELECTED, are there any additional steps needed in SRM compared to replicating all planrts using BBP_LOCATIONS_GET_ALL.
    Your inputs will be a help.
    Thanks,
    Sasikala

    Hi,
    Just Check the authorizations of the RFC user.Try giving SAP_ALL and SAP_NEW profie to RFC user from ECC to SRM.If all the authorizations are correct, then there should not be any issues.You can always check the issue log in transaction SLG1.
    BR,
    Deepti.

  • Client copy with configuration data in R/3. Is there any effect on EBP sys

    Hi all,
    We are using classic scenario. Our client is reorganizing their Org structure for that we need to do client copy with only configuration data.
    In this scenario we are uploading the master and transactional data through ALE in order to retain the same number ranges and the same data in EBP system.
    My doubt is when we do config steps Define logical system and assign the logical system to the client and define Idoc message types etc... Is it necessary to run BBP_LOCATIONS_GET_ALL job. If yes the same data like Plant and storage location and all master data will override the existing data or not. And what about the open Purchase orders and open goods receipts.
    Can you please reply immediately. It is very urgent.
    Thanks in advance

    waiting online

  • Error while creating the Organization structure.

    Hi,
    I am trying to create an Organization structure in SRM 5 sytem, I have created a Root for the structure and when i try to click on the Attribute Inheritance or the Check tab below i am getting an error "Start program BBP_LOCATIONS_GET_ALL first (see note 563180 and long text)" but i have replicated one plant from the R/3 system using BBP_LOCATIONS_GET_SELECTED and the material groups and all the other relevant datas from R/3. I can see in the table BBP_LOCMAP the plant been associated with the relevant company code. I am now struck in creating the organization structure. I am not sure where i am going wrong while creating the Org model.Please give me your valuable inputs to overcome this error.
    Regards
    GGL

    Go to transaction SM30, table T77S0
    Add an X to the following entry:
    Group = EBP          
    Sem abbr. = LMIGR        
    Val. Abbr. = X       
    Description = Locations Successfully Migrated
    This tell the system that the locations have been replicated and the error indicating location get all needs be executed will go away.
    thanks,
    justin
    Edited by: Justin Farley on Feb 25, 2009 7:16 PM

  • Error while creating Org structure     Message no. BBP_LOCATION009

    Hi
    Iam trying to build an SRM6.0 with backend as R/3 4.7
    I have replicated the plats from back end with report BBP_LOCATIONS_GET_FROM_SYSTEM
    On errors rectified the same and finally, SLG1 report shows no errors.
    But still noticed that T77S0 table entry with GPID=EBP, SEMID= LMIGR is not set to ‘X’ (Refer note 563180)
    Due to the above problem while creating org structure when I click on ‘Att inheritence’ or “Extended attributes –Locations” tab,
    I get the message:
    Start program BBP_LOCATIONS_GET_ALL first (see Note 563180 and long text)
             Message no. BBP_LOCATION009
    Diagnosis
        You tried to call a program that uses a location. The locations have not
        yet been replicated.
    System Response
        The current program has been terminated.
    Procedure
        Start the program  to replicate the locations. You can find more
        information in SAPNet in Note .
    Procedure for System Administration
    You can disable this message by starting table maintenance (SM30) for
    table T77S0. Change the entry EBP/LMIGR to "X". Note that the system
    cannot supply certain information if the locations are not replicated.
    Locations that do not exist can be deleted during attribute maintenance.

    are you working with multiple backend systems?
    can you retry downloading the plants with the report
    BBP_LOCATIONS_GET_ALL
    and then give the logical sys name as yr present backend?
    BR
    Dinesh

  • Few basic SRM questions .......

    I recently completed the SRM training from SAP and I have few basic questions and need help. Full points will be rewarded.
    These are my questions and it is based on SRM 5.0 Classic Scenario with R/3 backend
    1. Invoice  & confirmation transferred to R/3 via  ALE ? .  All other documents are transferred to R/3 via RFC?
    2. Based on the configuration, if the material is available in the backend then reservation will be created. Other wise PO will be created.  For text items, PR will be created.
         a. Who (purchaser) will process the PR in R/3 and how it is processed?.
         b. Who (purchaser?) will process the reservation in R/3 and how it is
             processed?. Assume no sourcing is setup in this case and No MRP run.
    3. How the vendor is linked to the Material or product category in SRM?. During the vendor replication from R/3, vendor and material/prod category link is automatically maintained?
    4. How the vendor is linked to a specific purchasing org/group? Is it based on the prod category assigned in the org structure for each purchasing org or purchasing group?
    5. How to do delta prod category replication?
    6. How to do Delta Material Replication?.
    7. Contracts and vendor list:-
        In our SAP training we created these from the browser. But in the actual
        implementation how do we create this?. Is it always from the browser?
    8. Direct Material and Plan driven Procurement.
       Can we use catalog items as direct material?. Just for example - > What
       about ‘Car Batteries’ that  is directly used in production and has the inventory
       also. But we are using electronic catalog for procuring this item. Is it possible to
       order this as direct material?
    9. How to replicate Plant. How to use DNL_PLNT?. Is BBP_LOCATIONS_GET_ALL will replicate all the PLANT's and its locations from the R/3 backend?
    10. In the HR system, which transaction we can view the org structure?

    Hi
    Answers to your questions ->
    1. http://help.sap.com/saphelp_srm50/helpdata/en/e9/d0fc3729b5db48e10000009b38f842/frameset.htm
    http://help.sap.com/saphelp_srm50/helpdata/en/74/ec7b3c91c1eb1ee10000000a114084/frameset.htm
    http://help.sap.com/saphelp_srm50/helpdata/en/55/d77c3c3fd53228e10000000a114084/frameset.htm
    http://help.sap.com/saphelp_srm50/helpdata/en/77/e97b3c91c1eb1ee10000000a114084/frameset.htm
    2.  Provided the necessary role is given to the Purchaser (Buyer) in the System.
    a) Yes
    b) Yes
    3. http://help.sap.com/saphelp_srm50/helpdata/en/e5/f5e938b4ece075e10000000a114084/frameset.htm
    http://help.sap.com/saphelp_srm50/helpdata/en/70/00c73a584611d6b21700508b5d5211/frameset.htm
    4. http://help.sap.com/saphelp_srm50/helpdata/en/2c/867d3ca2156c6ae10000000a114084/frameset.htm
    The vendor ORG has to be seperately created through trasaction PPOCV_BBP before replicating the Vendors from the R/3 System.
    http://help.sap.com/saphelp_srm50/helpdata/en/70/00c73a584611d6b21700508b5d5211/frameset.htm
    5. http://help.sap.com/saphelp_srm50/helpdata/en/42/d3b671ba67136fe10000000a1553f7/frameset.htm
    6.  http://help.sap.com/saphelp_srm50/helpdata/en/29/d586398dcfd74fe10000000a11402f/frameset.htm
    http://help.sap.com/saphelp_srm50/helpdata/en/05/9b8139437eac2ae10000000a11402f/frameset.htm
    http://help.sap.com/saphelp_srm50/helpdata/en/f5/b4bcdac7c40c4dba53e3695d18236c/frameset.htm
    7. Yes, from Browser it's quite easy and is quite user-friendly.
    8.
    http://help.sap.com/saphelp_srm50/helpdata/en/d3/4b9c3b122efc6ee10000000a114084/frameset.htm
    http://help.sap.com/saphelp_srm50/helpdata/en/18/db183d30805c59e10000000a114084/frameset.htm
    9.
    You can use the following three routines to download locations from the backend system and store them as business partners in SAP Enterprise Buyer.
    BBP_LOCATIONS_GET_ALL
    To get all the location numbers from each backend system that is connected
    BBP_LOCATIONS_GET_FROM_SYSTEM
    To get all the location numbers from one particular backend system
    BBP_LOCATIONS_GET_SELECTED
    To get selected locations
    Previously, locations were not given business partner numbers in SAP Enterprise Buyer. If you are configuring an upgrade, you can use routines BBP_LOCATIONS_GET_FROM_SYSTEM and BBP_LOCATIONS_GET_SELECTED to check that the following conversions have been made:
    ·        Conversion of user favorites
    ·        Conversion of user attributes
    ·        Conversion of old documents
    Routine BBP_LOCATIONS_GET_ALL checks these automatically.
    Once you have run the routines, the location data is available in the SAP Enterprise Buyer system. Table BBP_LOCMAP contains the mapping information (in other words, which business partner number corresponds to which location in which backend system).
    For more information, see SAP Note 563180 Locations for EBP 4.0 – plant replication
    http://help.sap.com/saphelp_srm50/helpdata/en/62/fb7d3cb7f58910e10000000a114084/frameset.htm
    http://help.sap.com/saphelp_srm50/helpdata/en/77/e97b3c91c1eb1ee10000000a114084/frameset.htm
    10. PPOCA_BBP(Create) / PPOMA_BBP(Change) / PPOSA_BBP(Display).
    Regards
    - Atul

  • Replication of few Plants(Locations) from SAP R/3 Backend system

    Hi All,
    Some of the plants which has been created in SAP R/3 Backend System but they are not visible in Enterprise Buyers Portal Production System.
    In order to get the missing plants replicated to EBP System shall I run the program
    BBP_LOCATIONS_GET_FROM_SYSTEM  or any other program i have to run,please advise.
    Thanks in advance.
    Regards,
    Pranab

    Hi Pranab,
    In order to replicate the selected plants from R/3 to EBP. Run the report (SA38)
    BBP_LOCATIONS_GET_SELECTED in SRM
    In order to replicate all the plants then ru the report BBP_LOCATIONS_GET_ALL.
    Award points for suitable answers.
    Rgds,
    Teja

  • Data Consistency when Copying/ Refreshing ECC 6.0 and SRM-SUS 5.0 Systems

    Hello,
    We are planning a refresh / system copy of an ECC 6.0 and SRM-SUS 5.0 system
    The refreshes will be completed from backups taken of production systems refreshed onto the QA Landscape.
    I have referenced the following SDN thread that provides some guidelines on how to refresh R/3 and SRM systems and maintain data consistency between the systems using BDLS and changing entries that correspond to backend RFC destinations:
    [Is there a process/program  to update tables/data after System Refresh?;
    This thread is fairly old and relates to earlier versions of R/3 (4.7) and SRM (3.0).  We have heard that at higher system versions there may be technical reasons why a refresh canu2019t be performed.
    Does anyone have experience of completing successful refreshes of landscape that contain ECC and SRM systems at higher SAP versions (ideally ECC 6.0 and SRM-SUS 5.0)  Does anyone know whether it is technically possible?
    Are there any additional steps that we need to be aware of at these higher SAP versions in completing the copy to ensure that the data remains consistent between ECC and SRM?
    Thanks
    Frances

    I have seen this somewhere in the forum: See if this helps you
    BDLS: Convertion of logical system (SRM).
    Check entry in table TWPURLSVR.
    Check RFC connections (R/3 and SRM)
    SPRO, check or set the following points:
    Set up Distribution Model and distribute it
    Define backend system
    Define backend sytem per product category
    Setting for vendor synchronization
    Numbe ranges
    Define object in backend sytem
    Define external services (catalogs)
    Check WF customizing: SWU3, settings for tasks
    SICF: maintain the service BBPSTART, SAPCONNECT
    SE38:
    Run SIAC_PUBLISH_ALL_INTERNAL
    Run BBP_LOCATIONS_GET_ALL
    Update vendor BBPUPDVD
    Check Middleware if used.
    Run BBP_GET_EXRATE.
    Schedule jobs (bbp_get_status2, clean_reqreq_up)
    Convert attributes with RHOM_ATTRIBUTE_REPLACE

  • Database table/FM to find relation between plant and company code in SRM

    Hi,
    I have a requirement where I need to determine the relation between the plant and company code in SRM.
    The plant and company code both belong to R/3. We are replicating the plant by using the report BBP_LOCATIONS_GET_ALL.
    This plant is now available as a BP in SRM. But from which SRM table or using which SRM FM can I get the relation between this and the company code?
    Thanks,
    Srivatsan

    Hi
    <b>Check table BBP_LOCMAP. (Plants) -  Manage Table Business Partner   > System   > Location
    BBP_COMPCODE_FAV               User-Specific Favorites for Permitted Company code.</b>
    Hope this will help.
    Please reward suitable points, incase it suits your requirements.
    Regards
    - Atul

Maybe you are looking for