Activate standard badi - prompts for Object Key?

[RyanK]

In SE19 when trying to activate an SAP delivered implementation of a badi I'm prompted for an object key for the implementation class.

fyi Running ECC6 on Basis 7 kb14.

Go to SE19

Display badi FIAA_BW_DELTA_UPDATE

Go to environment menu, choose activate.

Notice that the activate option is greyed out?

Go back and change the FIAA_BW_DELETA_UPDATE badi implementation. Go to environment menu, choose activate. You'll be prompted for an object key for the implementing class - CL_IM_FIAA_BW_DELTA_UPDATE.

Is this correct behavior? We don't want to change the class - just activate it. Could I get around this by copying the class changing the implementation class to a ZCL_IM_FIAA_BW_DELTA_UPDATE?

Thanks in advance for any help on this topic.

[Former Member]

FI-AA: Transactions

Technical name: 0FI_AA_11

Before you can use the delta extraction, you have to activate the FIAA_BW_DELTA_UPDATE BAdI. This BAdI ensures that the change tables – BWFIAA_AEDAT_TR, BWFIAA_AEDAT_AB and BWFIAA_AEDAT_AS – are updated when you update transactions, or create and change master data and annual values for assets.

Go to SE19 using the implementatio name as FIAA_BW_DELTA_UPDATE. GO in change mode and then activate the BADI impl.

You may need to get the access key to activate the impl.

BAdI definition FIAA_BW_DELTA_UPDATE is only provided for SAP internal use. The BADI definition is provided for internal usage only. No BADI implementation can be created or copied by a customer.

Check the SAP Note: 535016. The BADI implementations for FIAA_BW_DELTA_UPDATE contained in the note are delivered inactive. These must be activated. See point 6 in the note.

Also check the below link for more details.

http://help.sap.com/saphelp_nw70/helpdata/en/a4/f4153c4eb5d82ce10000000a114084/content.htm

Hope it helps.

Thanks,

Balaji

Edited by: Balaji Ganapathiraman on Mar 26, 2008 10:21 AM

[Former Member]

Hi Ryan.

You need to apply an OSS note for this

Please check the extract below..it will solve the problem

check the following Notes.

Check these OSS Notes - 828240, 688477 and 590034,599896

Note Pasted below :

When you load the delta-enabled InfoSources of asset accounting, no time stamp information is updated in the OLTP system if you have selected "Simulation of the delta process initialization" (initialization without data transfer; technical mode 'S') as the update mode.

This affects the InfoSources:

1. 0ASSET_ATTR_TEXT

2. 0ASSET_AFAB_ATTR

3. 0FI_AA_11

4. 0FI_AA_12

As a result of the error, you cannot start delta extraction after the initialization without data transfer because the delta extractor does not find any time stamp information it can use.

Other terms

RSA3, BWOM2_TIMEST, delta, DeltaInit, BWFIT, 0FI_GL_4, BWFIT_GET_TIMESTAMPS, BWFIT_RESET_TIMESTAMPS, BWFIT_UPDATE_TIMESTAMPS

Reason and Prerequisites

a) The problem is caused by a program error.

b) The 'FIAA_BW_DELTA_UPDATE' BADI is not active.

Solution

For a: Implement the source code corrections to create a correct time stamp for the initialization without data transfer.

For b: For a data extraction to the BW system according to the delta method, the 'FIAA_BW_DELTA_UPDATE' BADI must be active. When assets are changed, this BADI writes the corresponding change entries which are read by the extractors to determine the delta values. If this BADI is not active, the extraction terminates with error BWFIAA 001 (BAdI implementation FIAA_BW_DELTA_UPDATE inactive in source system). During a DeltaInit extraction with data transfer, the system flags the data request as incorrect or canceled in the monitor and issues the error message. However, during the DeltaInit extraction without data transfer, the system does not issue an error in the BW system even though the extractor triggered an error message and the termination of the extraction in the OLTP system. The data request in the BW system has the status 'successful' and the user cannot see that an error has occurred. However, a time stamp is not created in these cases since the following delta extractions would cause inconsistencies because the BADI would not be able to log all changes that have occurred since the last extraction.

Regards

Byju

[RyanK]

Thanks for the helpful information. I don't understand why SAP would deactivate this badi in previous notes....

My root problem still persists: It wants an object key for the implemention class even though we're not changing it.

Is this fairly much the behavior I would expect? I'll get an object key if absolutely necessary but my company wants to avoid object keys like the plague.

Thanks,

-Ryan

[Former Member]

Hi Ryan,

We are facing the same issue here i.e the BADI:FIAA_BW_DELTA_UPDATE is inactive and when we try to activate it asks for the access key.Could you do delta after getting the object key and activation of the BADI? Were there any more steps that you had to do after activation of this BADI?

Regards,

Rinal

[Former Member]

Hello experts,

Have any of you resolved your issue of getting prompted for an access key when trying to activate FIAA_BW_DELTA_UPDATE? I have not seen a solution for this problem on SDN. Did you get an access key from SAP to activate it? Is there another way of activating it (SE38 program, SPRO transaction)? Thanks for you help!

Jose

[former_member181995]

Because of this BADi is only made for SAP internal use.

Try to use some other BADi or exit instead.