Classic Badi..

Hello to all ,
There is a standard Classic Badi "IMP_ECM_OTHERS_DECO" this is inactive from my side... ho this is can be active .. Please Help me
Regards,
Vandana.

Hi Vandana,
Please do the follwoing
go to se19 -> enter badi name -> display
In the Attributes tab...the box "Within SAP" is ticked which means we cannot create an implementation since it is restriced by SAP and can be used internally only......not for custom changes(not recommended)
A change of standard code has been done and any change in standard code demands an access key...
Recommendations
(1) Do not ever transport the request to quality or production servers...
(2) Try to retrieve the previous active version if transasctions or programs using the badi gives a dump or error because of it's current inactive status
(3) check with the basis for earlier version retrieval incase of serious problems
Hope it helps
Regards
Byju

Similar Messages

Classic badi implementation zac_document not being called

For classic BADI AC_DOCUMENT I had prior and currently have an implementation ZAC_DOCUMENT.
I had this working but now it is not working and I am unable to determine why not. I deleted the implementation and recreated it with SE18.
If I view the implementation in change mode of transaction SE19, I see on the attributes tab that the implementation is activated. On the interface tab it says....
interface name IF_EX_AC_DOCUMENT
name of implementing class ZCL_IM_AC_DOCUMENT
I double click on method CHANGE_AFTER_CHECK to see my code which passes syntax check... I'll abbreviate....
method IF_EX_AC_DOCUMENT~CHANGE_AFTER_CHECK.
data:
loop at IM_DOCUMENT-ITEM into wa_accit.
lc_nomod = 'X'.
substituted alternative account
if ....
if lc_nomod is initial.
append wa_accit_sub to ex_document-item .
endif.
endloop.
endmethod.
The code here is not being triggered, nor is a set break-point. Thanks in advance for any help getting this to work again.

check if you are using the valid data to hit the BADI

I need to create a Classic BADI definition in an ECC 6.0 Environment

Greetings all,
Let me start by saying that I work in a corporation with many SAP landscapes at various versions (4.7, ecc 6 etc.) We have an application developed in an ECC 6.0 environment which needs to be pushed down to some 4.7 environments. This development needs some BADIs defined to give the receiving systems some flexibility. Here comes the problem, 4.7 cannot handle New BADIs and ECC 6.0 will not allow me to create Classic BADI definitions. I've searched through notes to see if there is some kind of quick fix and I have not found any. So I appeal to you the enhancement forum. Is there a note? How else can I create something and give the non original systems the flexibility needed?
Thank You

Yes Michelle, you are misunderstanding. I am the Definer of the BADI, not the implementer. I am setting up the hook in the program. One can still implement a classic BADI in SE19 in ECC 6.0. What we are prevented from doing is defining a new Classic BADI. We are forced to define new BADIs.
Try this: Go to SE18, select BADI name and put in Ztestjunk. Now hit the create button:
Here is the error message you will get:
"Create" operation is possible only for enhancement spots
Message no. ENHANCEMENT269
Diagnosis
You wish to create a BAdI definition on the initial screen of the BAdI Builder.
System Response
It is not possible to directly create a BAdI definition. The BAdI definition can only be created as part of an enhancement spot.
Procedure
Either create an enhancement spot or process an enhancement spot that already exists. There you can create BAdI definitions as part of the enhancement spot.

Classic BADi not being called

Hello Experts... Your kind and expert advice is deeply appreciated...
We had implemented a BADi in CRM4.0 and that is being called and working alright.
We are now upgrading CRM4.0 to CRM7.0. With this change classic BADis is not being called.
Difference I noticed in calling program is that in CRM 4.0 BADIs were pulled/instantiated by factory method. However in CRM 7.0 it uses "GET BADI" command. But since "GET BADI" does not fetch implemented BADi, it throws BADI not found exception.
- I searched and learnt that "Get BADI" can fetch classic BADIs and there is no need to migrate classic BADIs to new BADIs ...(if I am not wrong)..
- Also that I re-activated classic BADi in CRM 7.0 but still "Get BADI" does not pulled/instantiate BADi.
- Also I search to have report "ENH_BADI_ADD_MIGR_INFO" run to create link between Classic and new BADi. Will this work?
Kindly advice to call classic BADi in CRM 7.0? Appreciate it. Thanks!
Warm Regards,
Kalpit

Hi,
Check if this BADI is migrated to enhancement spot (In attributes TAB). If yes, you need create an enhancement implementation for
this BADI.
Thanks,
SKJ

Migration of Standard Classic Badi to New Badi

hi,
Is it mandatory to migrate all standard classic badi's to New badi's in ECC6.0. I have read in the documentation only custom BADi's should be migrated.
Can we migrate Standard Classic badi's to New badi's, please provide the procedure for this.
when i am trying to do this in one way it is not allowing me to use the same class as classic badi used, so i have created custom class for this. Is it going to effect.

Hi Phanindra,
Calling New badi's is much faster than calling clasic badi's. SAP never recommends to convert all classic Badi's to New Badi's rather you convert your own Badi's to New Badi's. You cant convert SAP classical BADI to New Badi. if you want to convert custom Badi, then please go through this below link
http://help.sap.com/saphelp_nw70/helpdata/EN/0e/4d3e42fc94aa04e10000000a1550b0/content.htm
Thanks,
Bishnu Dash

How to undo migration of classic BADI from enhancement spot...

Hello Experts,
Is there a way to "UNDO" if a BADI is migrated to a custom enhancement spot? I want to
revert it back to its "classic" status.
Thank you guys and take care!

hai do u want to undo migration of custom badis or standard badis
if for custom badis then from se18 just u can delete the definition form teh enhancement spot
if for standard badi then i guess it is not advisable
and if u want a classical badi to be created just select utuilites --> create classical badi definition and it wil not ask for spots
m.a

Problems with a manually created Classic BADI

Hello.
When Implementing note 1632640, we manually created a Classic BADI named HRPAYPT_CA_SURCHARG (instead of the correct name HRPAYPT_CA_SURCHARGE).
When we realized this, we've deleted the implementation ZHRPAYPT_CA_SURCHARG and the BADI
Definition. However, when asked to delete (or not) the interface IF_EX_HRPAYPT_CA_SURCHARGE we choosed "NO".
Now, we cannot create the new BADI definition because it's says that interface IF_EX_HRPAYPT_CA_SURCHARGE already exists.
we also cannot delete manually the interface in SE24, because it says that it can only be mantained via Addin Builder.
How can we solve this issue?
Regards,
Valter Oliveira.

Hi Valter,
Try going to SE24 and put in the class name "CL_EX_HRPAYPT_CA_SURCHARG" and then choose "Utilities" -> "Versions" -> "Version Management" -> "Public Section" and see if you can retrieve the old version of the class that was generated when you created the definition. If you are able to retrieve it then you might be able to delete it along with the interface itself. If that doesn't work you may have to resort to some sort of debugging trick to get by the issue.
Regards,
Ryan Crosby

Demo programs of new and classic BADIs - transactions SE18 and SE19

Does SAP supply any demo examples of the new BADI switch framework and/or classic BADIs.
I've been trying to learn how to use SE18 and SE19 from examples on the web and articles in Thomas Weiss blogs. But, I'm still confused.
Thanks
Ed Baker

Thank you for replying.
I did look at that example during my investigations. In fact, I found another page with screen shots for the example at http://www.sapmaterial.com/badi.html
Unfortunately, I'm on ECC 6.0 and the screen shots don't quite line up.
What I'm actually referring to is spots like this in SAP supplied code. Here's a typical example in SAPMV45A during transaction VA01 (sales order create).
How do I get SAP to branch off to user code when it reaches the "ENHANCEMENT-POINT" line.
*       MODULE XVBAP_LESEN                                            *
*       Tabelle XVBAP fuer Bildschirmanzeige lesen, es wird die erste *
*       Einteilung mit Wunschmenge zur Verfügung gestellt             *
MODULE XVBAP_LESEN OUTPUT.
PERFORM XVBAP_LESEN(SAPFV45P) USING CHAR1.
ENHANCEMENT-POINT XVBAP_LESEN_01 SPOTS ES_SAPMV45A.
*$*$-Start: XVBAP_LESEN_01----------------------------------------------------------------------$*$*
ENHANCEMENT 59 /SAPHT/SW_LIC_BU_VERS_SAPMV45A.    "active version
* IS-HT (D45)(D44)
   CALL FUNCTION '/SAPHT/SW_BUMP_ICON_OUTPUT'
      EXPORTING
          i_vbap_posnr       = vbap-posnr
          i_vbap_uepos       = vbap-uepos
          i_vbup_bump        = xvbup-bump
      CHANGING
          c_gg_process_icon = gg_process_icon.
ENDENHANCEMENT.
*$*$-End:   XVBAP_LESEN_01----------------------------------------------------------------------$*$*
ENDMODULE.

Classic BAdi and New BAdi ...

Hi all,
I have a question regarding the new BAdi concept using enhancement spots.
With the classic BAdi's once we create an implementation it will call up our implementation when the BADI class is been called.
But with the new concept we have to explicitly call the BAdi we created right ? doesn't this mean modifiying the standard code ( If there's no ehancement section or point )?
Can someone tell me whether there is another way to call our implementation by using GET BADI and CALL BADI statement without modifying standard code ( by creating an explicit enhancement).
Cheers,
D.

hi,
Classic and new BAdIs differ in a number of features that are important for migration:
1. BAdI object
a. With classic BAdIs, a BAdI object is created by calling a factory method, and referenced via a reference variable of the type of the BAdI interface.
b. With new BAdIs, a BAdI object is created via the ABAP statement GET BADIas a handle for the calls of BAdI methods, and referenced via a reference variable of the type of the BAdI. A BAdI object is an instance of an internal BAdI class, which otherwise is invisible to the outside.
2. Passing comparison values for the filter
a. With the classical BAdIs, the filter values are stored in a structure and passed with the call of the BAdI methods.
b. With the new BAdIs, the comparison values for the filters used to search for implementations are passed when the BAdI object is created with the GET BADIstatement.
There is no way of migrating the call of the factory method one-to-one into the ABAP statement, because GET BADI can also return an existing BAdI object, which is not possible with the factory method.
3. Calling BAdI methods
Passing comparison values for the filter
a. A classic BAdI can be called only once and the call positions are registered centrally.
b. With new BAdIs, multiple calls are possible and the call positions are not registered centrally.
For the above reasons, an automatic call migration is not possible.
Have a look at below link.
http://help.sap.com/saphelp_nw2004s/helpdata/en/ee/6f3b42ea85b26be10000000a155106/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/0e/4d3e42fc94aa04e10000000a1550b0/content.htm
I hope it helps.
Best Regards,
Reshma

New BADI and classic BADI

Hi,
Could anyone post solution for making out that a classic BADI is preferred or a new BADI.
This's not an interview question. I just want to make it out for my requirement.
Could anyone post the exact real time differences between a classic BADi and a new BADI.

Hi,
Use new BAdI over classical BAdI, as performance of new BAdI is better.
Incase of new BAdI you have to create an Enhancement Spot and create BAdI definition under it, and subsequently implement the BAdI. In the code use
GET BADI badi_name to generate BAdI handle, and
CALL BADI badi_name->method.... to call BAdI methods.
Incase of Classical BAdIs adapter class are created in the runtime of the application program.
Check the following link:
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/ee/6f3b42ea85b26be10000000a155106/frameset.htm
Regards,
George
Edited by: George Biswal on May 26, 2009 3:04 PM

Whats is the diff. btw classic badi and new badi

Hi guy,
I just found out that there is classic and new badi implementation in SE19, I would like to check out with u guys on what is the diff btw the two?
thanks.

<b>Differences Between Classic and New BAdIs</b>
Classic and new BAdIs differ in a number of features that are important for migration:
1. BAdI object
a.      With classic BAdIs, a BAdI object is created by calling a factory method, and referenced via a reference variable of the type of the BAdI interface.
b.      With new BAdIs, a BAdI object is created via the ABAP statement GET BADIas a handle for the calls of BAdI methods, and referenced via a reference variable of the type of the BAdI. A BAdI object is an instance of an internal BAdI class, which otherwise is invisible to the outside.
2. Passing comparison values for the filter
a.      With the classical BAdIs, the filter values are stored in a structure and passed with the call of the BAdI methods.
b.      With the new BAdIs, the comparison values for the filters used to search for implementations are passed when the BAdI object is created with the GET BADIstatement.
There is no way of migrating the call of the factory method one-to-one into the ABAP statement, because GET BADI can also return an existing BAdI object, which is not possible with the factory method.
3. Calling BAdI methods
Passing comparison values for the filter
a.      A classic BAdI can be called only once and the call positions are registered centrally.
b.      With new BAdIs, multiple calls are possible and the call positions are not registered centrally.
For the above reasons, an automatic call migration is not possible.
Have a look at below link.
http://help.sap.com/saphelp_nw2004s/helpdata/en/ee/6f3b42ea85b26be10000000a155106/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/0e/4d3e42fc94aa04e10000000a1550b0/content.htm
I hope it helps.
Best Regards,
Vibha
*Please mark all the helpful answers

Import variable from classical BADI to workflow

Hi Experts,
I have created a BADI containing the function GET_COMMENT so that a popup appears and an approver enters a comment after they click on the reject button in transaction ME54N. The text that they enter should should be exported the workflow and also should be sent to the mail notification sent to the creator (initiator) of the PR. Definition name is ME_COMMTMNT_REQ_RE_C, interface is IF_EX_ME_COMMTMNT_REQ_RE_C. How do I export the variable so that it can be seen in the workflow? Can I have a step by step procedure as I am quite new to workflow.
Regards,
Darlington

Please take a look at my code implemented in the BADI. Is what I have done correct? The first IF statement is just so that the popup does not appear when it's not needed.
DATA: l1(120) TYPE c,
        l2(120) TYPE c.
DATA : lt_cont TYPE TABLE OF swr_cont.
DATA : ls_cont TYPE swr_cont.
CLEAR: l1,l2.
IF sy-ucomm = 'MESAVE' OR
     sy-ucomm = 'OK'.
    EXIT.
ELSE.
    INCLUDE <swfcntn01>.
    CALL FUNCTION 'GET_COMMENT'
      EXPORTING
        ref               = '123'
*   IM_VALUE          = ' '
     IMPORTING
       tech_name         = l1
       description       = l2
     EXCEPTIONS
       cancelled         = 1
       OTHERS            = 2
    IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    ls_cont-element = 'l2'.
    ls_cont-value = l2.
    Append ls_cont TO lt_cont.
    CALL FUNCTION 'SAP_WAPI_START_WORKFLOW'
      EXPORTING
        TASK                      = 'TS20000161'
*   LANGUAGE                  = SY-LANGU
*   DO_COMMIT                 = 'X'
*   USER                      = SY-UNAME
*   START_ASYNCHRONOUS        = ' '
*   DESIRED_START_DATE        =
*   DESIRED_START_TIME        =
*   DESIRED_START_ZONLO       = SY-ZONLO
*   IFS_XML_CONTAINER         =
* IMPORTING
*   RETURN_CODE               =
*   WORKITEM_ID               =
*   NEW_STATUS                =
* TABLES
*   INPUT_CONTAINER           =
*   MESSAGE_LINES             =
*   MESSAGE_STRUCT            =
*   AGENTS                    =
ENDIF.
Regards,
Darlington

Looking for the classic "Bad Take" transition.

My problem is, I don't even know what the proper technical search terms would be for this. So let me describe.
You've seen the transition effect countless times where someone on camera makes a mistake and the screen goes black (or white) for a split second and you hear a short (a fraction of a second) "BEEP," to signify that what follows is a retake. It's a comic effect.
Is it an electronic clapper tone?
It may be the same tone you hear when at the beginning of old films, you'd see the clock hand sweep around a huge 5, 4, 3, 2... and at each one, there'd be a "BEEP"
I think I just need the tone. I can add a solid black or white still for the visual part. I tried looking through my iMovie/iLife files and didn't see anything. I also tried Freesound.org
Any ideas?

and in addendum (searching for the right english expression):
it is not a plain fade-to-white, but a socalled light-leak
(as if the 'film' was taken out of camera)
it's a bit complex, therefor a commercial product, as
http://www.crumplepop.com/?page_id=1032
$69 ...

Control extended classic mode BADI

Hi,
I am trying to setup the system to work in the extended classic scenario.
I have activated the extended classic switch and i am using the BADI control extended classic badi.
For product categories that i want to use in extended classic mode, the logic inside the BADI returns a "X"
For Eg: I have a product cat "Boards" for whcih the BADI returns "X"
When i add this pruduct category to my shopping cart, there is a dump in ITS.
However, I remove the product cat "Board" from the BADI, I am able to add this product cat to the shopping cart without a dump.
Please let me know why this is happening.
Dump:
Runtime Errors           UNCAUGHT_EXCEPTION
Except.                  CX_BBP_PD_ABORT
Date and Time            04/21/2010   06:07:37
Short dump has not been completely stored (too big)
What happened?
The exception 'CX_BBP_PD_ABORT' was raised, but it was not caught anywhere
       along
the call hierarchy.
Since exceptions represent error situations and this error was not
      adequately responded to, the running ABAP program 'SAPLBBP_PDH' has to be
      terminated.
Please help
Thnaks,
Vignesh

Hi Laurent,
I am getting the foloowing error. Can you identify what is going on ?
Information on where terminated
    Termination occurred in the ABAP program "SAPLBBP_PDH" - in "BBP_PD_ABORT".
    The main program was "SAPLBBP_SC_UI_ITS ".
    In the source code you have the termination point in line 73
    of the (Include) program "LBBP_PDHU08".
Source Code Extract
Line SourceCde
   43
   44   READ TABLE lt_callstack INTO ls_callstack2 INDEX 4.
   45   CONCATENATE   '/' ls_callstack2-eventtype
   46                 ls_callstack2-eventname ls_callstack2-progname
   47                 INTO lv_msgarg3 SEPARATED BY space.
   48
   49   CALL FUNCTION 'BBP_ALERT_INTERNAL_OT'
   50     EXPORTING
   51       msgid   = gc_msgid_bbp_pd
   52       msgno   = 047
   53       msgarg1 = lv_msgarg1
   54       msgarg2 = lv_msgarg2
   55       msgarg3 = lv_msgarg3.
   56
   57   MESSAGE ID gc_msgid_bbp_pd TYPE c_msgty_i NUMBER iv_msg_no
   58           WITH ls_callstack1-eventtype
   59                ls_callstack1-eventname
   60                ls_callstack1-progname.
   61
   62   rollback work.
   63
   64 * get the messages from the application log
   65   TRY.
   66       CALL FUNCTION 'BBP_PD_LOG_GET_MESSAGES'
   67         TABLES
   68           e_messages = lt_messages.
   69     CATCH cx_bbp_pd_abort.
   70       REFRESH lt_messages.
   71   ENDTRY.
   72
>>>>>   RAISE EXCEPTION TYPE cx_bbp_pd_abort EXPORTING
   74       worked_on_document = lv_guid
   75       t100_msgid = gc_msgid_bbp_pd
   76       t100_msgno = iv_msg_no
   77       t_appl_log_messages = lt_messages.
   78
   79 ENDFUNCTION.
Pls help

New BADI concept in ECC 6.0

I am trying to gain an understanding of how I would implement one of the new BADIs in ECC 6.0 (badis implmented through and enhancement spot , get badi, call badi concept).
I am not looking for information on how to implement a classic badi through se18/se19.
I have also ready through the SAP help on the new badis and it is still not clear to me. So, please do not provide links to the standard SAP help. I have that.
I am wondering if anybody has a whitepaper, example, etc. that explains the details of how to implement, use, trigger the new badis linked to an enhancement spot.

Hi J.J,
enhancement spot
A repository object for the administration of explicitly created enhancement options. Enhancement spots are components of a tree structure hierarchy, of which the branches represent composite enhancement spots and the leaves are simple enhancement spots. Implicitly available enhancement options do not have any enhancement spots.
composite enhancement spot
Semantic combination of simple and other composite enhancement spots with the aim of providing structure.
simple enhancement spot
Reference to a set of enhancement spot element definitions. A simple enhancement spot can occur independently or as a component of a composite enhancement spot.
ENHANCEMENT-POINT
Defines a position in an ABAP program as an enhancement option,
at which one or more source code plug-ins can be inserted.
the syntax will be like
ENHANCEMENT-POINT enh_id SPOTS spot1 spot2 ...
STATIC
INCLUDE BOUND.
Enhancement Options
Definition
Enhancement options are positions in Repository objects where enhancements can be made. These options are either explicitly defined (by the developer) or exist implicitly. Explicit enhancement options are generally defined in a central initial system. Enhancements are made in follow-on systems.
Use
Explicit enhancement options can currently be defined by:
1. Explicitly flagging source code points or sections in ABAP programs. For an enhancement, these can be enhanced or replaced by source code plug-ins.
2. Including Business Add-Ins (BAdIs) in ABAP programs. These programs are then enhanced by object plug-ins with predefined interfaces.
Explicit enhancement options are managed by enhancement spots and enhanced by enhancement implementations.
Currently, implicit enhancement options are:
1. Specific options in ABAP programs such as the end of the program which can be enhanced by source code plug-ins.
2. Parameter interfaces of function modules, which can be enhanced with parameters.
3. Attributes and parameter interfaces of global classes, which can be enhanced with attributes or parameters.
Implicit enhancement options always exist and do not require enhancement spots. They are also enhanced by enhancement implementations.
BAdIs Embedded in the Enhancement Concept
Use
The definition of BAdIs is managed by enhancement spots. A simple enhancement spot for BAdIs can contain several BAdI definitions as enhancement spot element definitions. BAdIs that would otherwise be spread out in the system can be grouped together semantically.
This structuring is mirrored on the implementation side through the enhancement implementations. A BAdI can be implemented by several BAdI implementations that are managed by enhancement implementations. A simple enhancement implementation for object plug-ins can contain several BAdI implementations of an enhancement spot as enhancement implementation elements and can implement a BAdI multiple times. Therefore, several enhancement implementations can be assigned to one enhancement spot.
A BAdI is always assigned to the same package, like the enhancement spot, to which it belongs.
Example
The structuring features of BAdIs in enhancement spots can be of a technical or a subject nature.
If, in the definition of several BAdIs, you have the provision that they are to be used in the same context (this is a feature known only by the person who defines the BAdIs), they must be used by the same simple enhancement spot.
From a subject point of view, all BAdIs must then be grouped together by affiliation to functional units for example, payroll in combined enhancement spots.
Thanks and regards
suma sailaja pvn

Classic Badi..

Similar Messages

Maybe you are looking for