How are members, in SAP BPC, accepted in a script?

[former_member679004]

Hello,

This is more of a generic question that I am posting here with relation to an issue that I recently faced.

When we load data from BW to BPC, through the 'Load Transaction data from BW Infoprovider Delta', I understand that the data is being populated into BPC. If in the list of records that is being populated, if there are a few records that have characteristics/members that don't exist in BPC, what would be the ideal working of the DMP. Would it error out?

Because, the error I get when running the package is 'Error in default logic' and it shows the missing member in the messages.

In the above case, I have the following in the script -

*XDIM_MEMBERSET DIMENSION= %DIMENSION_SET% - What does this do?

What if there was no script written for this load? Then, how would the load work? Will the load still fail because of the missing member in SAP BPC?

How would I override this? Instead to run the default logic (Include script - below) only for the valid members of the dimension in SAP BPC ?

Please find the include program as below -

*SELECT(%ADTS_TO_FILTER_ACT%,[ID],AUDIT_FINANCIAL,FA_DERIVATION_ACTUAL = 'Y')
*SELECT(%ADTS_TO_FILTER_NON_ACT%,[ID],AUDIT_FINANCIAL,FA_DERIVATION = 'Y')


*FOR %CATEG% = %CATEGORY_SET%	
// 	*XDIM_MEMBERSET PROFITCENTER = %PROFITCENTER_SET%
	*XDIM_MEMBERSET CATEGORY = %CATEG%
	*XDIM_MEMBERSET AUDIT_FINANCIAL = %ADTS_TO_FILTER_ACT%,%ADTS_TO_FILTER_NON_ACT%
	*XDIM_MEMBERSET FUNCTIONALAREA = BAS(FUNCTIONALAREA)
	*START_BADI SUBSTITUTE_FUNCTIONALAREA
		CATEGORY = %CATEG%
		QUERY = ON
		WRITE = ON
		SKIP_FCST_ACTUAL_PERS = Y
		SKIP_BLINE_ACTUAL_PERS = Y
	*END_BADI
*NEXT

Thank you.

Regards,

Leonel S Mario

[former_member186338]

You are using badi in the default.lgf. Debug it using endless loop at the beginning to understand what is wrong.

[former_member679004]

Hello Vadim,

The thing is the error happens before it can get into the logic as per the ABAP consultant who debugged the logic script and the included BADI.

He mentioned that since the incoming transaction data from BW has a record with a member that does not exist in BPC, hence, the job fails as this member is not recognized by BPC. This was the same thing observed in UJKT.

Please find the below for your reference -

*SELECT(%CONV_GRP_ACCTS%,[ID],ACCOUNT,[UOM_CONV_GRP]<>'')
*SELECT(%AUDITS_TO_BE_CONVERTED%,[ID],AUDIT_MARGIN,[UOM_CONV_SRC] = 'Y')
*FOR %CATEG% = %CATEGORY_SET%
	*XDIM_MEMBERSET CATEGORY = %CATEG%
 	*XDIM_MEMBERSET PROFITCENTER = %PROFITCENTER_SET%
	*XDIM_MEMBERSET ACCOUNT = %CONV_GRP_ACCTS%
	*XDIM_MEMBERSET AUDIT_MARGIN = %AUDITS_TO_BE_CONVERTED%
	*XDIM_MEMBERSET FUNCTIONALAREA = BAS(CASC)
	*XDIM_FILTER RPTCURRENCY = [RPTCURRENCY].Properties("ID") = LC
	*START_BADI UOM_CONVERSION
		QUERY = ON
		WRITE = OFF  //BADI will save results by package
		DONT_RUN_ON_CAT_TYPES = ACTUAL	//Don't run on Category type = ACTUAL
		SKIP_FCST_ACTUAL_PERS = Y		//Skip Actual Periods for FORECAST Categories
		SKIP_BLINE_ACTUAL_PERS = Y		//Skip Actual Periods for BASELINE Categories
	*END_BADI
*NEXT

-------------------------------------------------------------------------------------------------------------------------------------
LOG:


FILE:\ROOT\WEBFOLDERS\CASCADESGOLD \ADMINAPP\MARGIN\TEST.LGF
USER:SLEO00364A
APPSET:CASCADESGOLD
APPLICATION:MARGIN


UJK_VALIDATION_EXCEPTION:Member "9789" does not exist.

The ABAP consultant mentioned that it is not entering the BADI at all even after putting a breakpoint in the BADI and executing UJKT.

Right now, I am kind of confused as to what is happening here. Please help.

Regards,

Leonel S Mario

[former_member186338]

sleo00364a

Member "9789" does not exist

Member of what dimension???

P.S.

"The ABAP consultant mentioned that it is not entering the BADI at all even after putting a breakpoint in the BADI and executing UJKT"

UJKT?????????????????

How it's related to this case?