BAPI_MDPROVIDER_GET_MEMBERS OPTIONAL_PROPERTIES

in the Function Call BAPI_MDPROVIDER_GET_MEMBERS (executing this remotely in java via sapjco) there are table params for OPTIONAL_PROPERTIES and SELECTED_PROPERTIES. i'm assuming these are useful for deriving member properties that are not normally part of the result set for this function call? If I want the results from this function call to include a property not normally part of the output params, how would I make use of this?

There is a parameter on that function module called ALL_PROPERTIES. Default value is space meaning don't retrieve all the properties. Try sending 'X' in that and see what you get. If you have acces to R/3 you can see the parameters of the function module (BAPI) using transaction se37.
Hope this helps.
Cheers,
Dion

Similar Messages

Empty LOV on webi

Hi there,
I created an OLAP universe on bw query, and created a webi on that universe. LOVs of all variables are empty, while executing on BEx web anlyzer, variable value candidates are not empty. Any insight?
The env is BOE XI 3.1 SP2 + BW 7.0018
Thanks,
Chris

hi Chris,
in the logfile you can see the following:
: MDDataProviderBW.GetMembers(Cat=ZBKG_S19,Cube=ZBKG_S19/ZBKG_S19_Q0001,Dim=[0MATERIAL__ZPRDFM],Hry[0MATERIAL__ZPRDFM],Lvl=[0MATERIAL__ZPRDFM].[LEVEL01],Mem=,OpCode=,PropFlag= )
Thu Jan 07 11:30:05.314: SAPMODULE: FIS: MDDataProviderBW.GetMembers(StartRow=0,EndRow=499)
Thu Jan 07 11:30:06.314: SAPMODULE: FIS: RFC function call MDDataProviderBW.GetMembers returned S
Thu Jan 07 11:30:06.314: SAPMODULE: FIS: Call to MDDataProviderBW.GetMembers took 1.000 seconds
Thu Jan 07 11:30:06.314: SAPMODULE: FIS: Got 0 membe
is your variable based on this navigation attribute ?
if so could you do the following:
- go to transaction se38
- start program BAPI_MDPROVIDER_GET_MEMBERS
- enter the values as shown above
- hit F8
Ingo

Purpose of the function modules BAPI_IOBJ_GETDETAIL, BAPI_MDPROVIDER_GET_ME

Hi,
Can any one please explain the following doubts...
1) What is the purpose of the function modules BAPI_IOBJ_GETDETAIL, BAPI_MDPROVIDER_GET_MEMBERS and when will they be used in BW, the purpose.
2) What are the different function modules useful in tracing the performance on the BW Side?
Thanks & Regrads,
Dinakar.

HI,
BAPI_IOBJ_GETDETAIL:
To get the information about the InfoObjects.
BAPI_MDPROVIDER_GET_MEMBERS:
when you call BAPI_MDPROVIDER_GET_MEMBERS, BI hierarchies with
time-dependent names or time-dependent structures are also evaluated with the
current key date.
Check this thread and the link
List Of BAPIs used for Extraction..?
http://help.sap.com/saphelp_nw04s/helpdata/en/9b/c1993c54966f3ae10000000a114084/frameset.htm

BOBJ 4.0 Upgrade: Impact on Int Kit customizations for crystal reports?

BW Version 7.01
BOBJ version XI 3.1
We would like to upgrade to BOBJ 4.0, could anyone provide input on these questions?
1 - Can we keep BW 7.01, or do we need to look into upgrading to 7.3? We'd prefer to not touch bw now. If we move to bobj 4.0, does BW need to be touched?
2 - We have modified these function modules in BW (i believe they are part of the integration kit in SAP BW) to meet end user requirements for crystal reports; will crystal reports in BOBJ 4.0 still work with these? I believe one of the improvements is that these aren't used anymore for performance reasons???
BAPI_MDPROVIDER_GET_VARIABLE
BAPI_MDDATASET_CREATE_OBJECT
BAPI_MDDATASET_GET_AXIS_DATA
BAPI_MDPROVIDER_GET_MEMBERS
BAPI_MDPROVIDER_GET_MEMBERS
3 - 99% of our reports are crystal, are there any other hurdles or reasons why we should be cautious moving to 4.0? We are looking to roll out explorer, webi, and xcelsius and would rather go ahead and catch up to 4.0...
Thanks,
Matt

Hi,
1. i'd recommend having a seperate BW for BI4 purposes. If anything, it makes management of integration TRANSPORTs much easier, given that you can only have 1 version active..
(yes, although there's no SAP IK Kit, transports are still imported into backend)
2. OLAP BAPI access is still there in BI4.0, namely for the CR 2011 tool with BW MDX Driver , and for Webi documents using the legacy Universe Design Tool OLAP.unv file.
the new OLAP data access driver for SAP in BI4.0 is the BW's BI Consumer Service (BICS API). The function modules for this are generally called: BICS_PROV_GET*
3. No hurdle at all. You can migrate your content as-is without fear of change. that's principally why the CR 2011 client is there for the 4.0 RTC - for adoption and onboarding. That legacy CR client technology is wholy unchanged, apart from .xlsx support and a 'read only' save mode.
the Crystal for Enterprise product is still playing catch up. It hasn't got all (any) of the direct drivers you would expect from crystal, but it can consume the new .unx common semantic layer and the BICS jco driver (neither of which the CR2011 product can)
... as of 4.1 (Q1 2012) the fit-gap in features is answered. i.e. they've all been fwd ported.
i hope this helps
Regards,
H

BAPI_MDPROVIDER_GET_MEMBERS OPTIONAL_PROPERTIES

Similar Messages

Maybe you are looking for