BADI CRM_BP_UIU_DEFAULTS or Component Enhancement?

Hello Experts,
I just came across BADI CRM_BP_UIU_DEFAULTS implementation.
While creating the account, to populate the fields in BP_ADDRESS with default values, this BADI can be used to implement that functionality.
This was the suggestion by our functional consultant.
I was thinking, why not to enhance the component and set the default values in DO_PREPARE_OUTPUT method or using some other methods.
I'm sorry for asking so stupid question. But, it's been a question I was asked a few times. I thought it was becoz of performance issue. But, still I'm not sure.
Can someone please help me find out the reason why to go for BADI and not to enhance the component?
Thanks in advance.
-Ezhno.

If there's a BADI I would go for the BADI, I understand it's a little weird, because the BADI's are placed in the standard component, so if you enhance the component and redefine the methods where the BADI's are called and put your logic there, the result will be pretty similar. Why you should redefine instead of use the BADI?, IMHO I don't think there's an exception, so as I said in the begining I would go for the BADI as the behaviour of the UI can change for notes, SP or ehp, if you you have the component redefined maybe you lose this functionality even if you called the SUPER properly and SAP support you, but, if you are using a BADI and using it as the way is meant, SAP will support you or at least they won't have the excuse to not support you
Cheers!
Luis

Similar Messages

BADI for ME22n - Component Object List

Hi ,
I am working with transaction ME22n. When the item category is L. The material data tab shows a button called Components (Object List). On clicking this button i am taken to another screen which has childeren material items and the related data. I need to capture the values on this screen and compare them with the database values to identify any changes.
I am working with BADI ME_PROCESS_PO_CUST , method CHECK and OPEN. Please tell me in which method parameter those screen values are stored and i can fetch them.
Also please suggest me any other approach possible which i can use to capture the screen field values in the component screen.
Any help would be deeply appreciated.
Thanks in advance.
Moderator message : Duplicate post locked. Continue with thread [BADI for ME22n - Component Object List|BADI for ME22n - Component Object List]
Edited by: Vinod Kumar on Aug 9, 2011 12:25 PM

Hi,
Please check this thread
User exit for component data in ME21n/ME22n
Thanks

Only BADi is used in enhancement spot when customer createion?

Only BADi is used in enhancement spot when customer createion?

Only BADi is used in enhancement spot when customer createion?

Component Enhancement Deletion Problem in WEB UI

Hi All,
I created an enhancement set for component ICMPP_BT_SVT and then I had to delete it. I also deleted the records created by enhancement in tables BSPWD_COMP_EXT and BSPWD_CMP_C_REPL.
But now I am facing exceptions while I run this component. Please tell if I have missed any step for deleting the enhancement for this component.
Please help.
Thanks
Vishal

If you want to delete enhancment follow the steps below. It worked fine for me.
First determine the objects (for example, BSP applications, classes, controller and so on) that were created by the enhancement. You can view these objects using the view cluster BSPWDVC_CMP_EXT (SM34): Select the enhancement set, choose "Enhancement Definition" and then "Controller Substitutes".
Then go to the BSP components in the ABAP workbench (SE80) that are used to store the enhancements. Search for the obsolete objects and delete them:
- Search for controller -> Search for and delete controller class
- Delete controller
- If a view exists -> Delete view
Then delete the Customizing entries ("Controller Substitutes") from the view cluster BSPWDVC_CMP_EXT.
If configurations that contain fields from enhancements that are now deleted were created (BSP_WD_CMPWB), these must also be deleted manually.

BAdI- Call for DataSource Enhancement! - Where?

Hi,
i have a question ... i have implemented a filterbased BAdI to enhance DataSources. I have implemented BADI Definitions, Implentations etc ...
But, where is the Position where i should call this BAdI? Should i call it, in the Customerexit RSAP0001?
I thought, the new BAdI technology replaced the Customerexit RSAP0001.
I appreciate your help
regards
ergin

check the below paper:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/3001894b-b1fb-2910-77ba-e80b6f2053b7?quicklink=index&overridelayout=true
M.

Component enhancement

hello specialists,
I am new to sap crm. Could you please edify the steps for enhancing a standard component and also the post enhancement steps for making the view available in the WebUI ? I am currently working on the Complaints component.

For any customer modifications to the standard components , we need an Enhancement Set.
a) Creation of the Enhancement Set. Go to the trx SM34 and cluster view BSPWDVC_CMP_EXT. Enter the name and descripton
b) Assignment of the Enhancement Set to a client. Go to Trx sm30 and open a maintain BSPWDV_EHSET_ASG. Assign the created enhancement set to the client you require.
After the enhancement set is created do the following
a) In the BSP_WD_CMPWB , choose the component you need to enhance and the enhancement set that you created
b) Click on the button Enhance Component on the Workbench( Extreme TOP Right )
c) When you do that you get an option to enter a new BSP application name( This should be a new name).
d) Once you have done that in sm34 view BSPWDVC_CMP_EXT you will be able to see the enhancement definition.
e) Right click on the view that you want to make the changes to and say enhance.
f) All the methods are marked by colored icons
g) One you have done this you shall be able to see the same view in sm34 view BSPWDVC_CMP_EXT under controller replacements in the Enhancement definitions.
Viola you are done.
Regards
Kavindra

Print Preview texts from event handler of a web UI component enhancement

Hello,
I've enhanced View GSTEXT/List to add Print Preview button. What I've done in the event handler is to read the text with function module READ_TEXT and I have all my text in the lt_lines internal table. Now I want to View this text in PDF format. I just realized I can't call a smartform directly from my event handler and I also can't call an adobe form to do this for me. Can anyone help me on how to resolve this?

Hi Khaya,
I see two things you might have done not quite right:
Why do you use "READ_TEXT" when all the data is already there in the BOL? Did you ever have a look at the logic the WebClient uses to display the text? Go check it now!
Of course you can call an Adobe or Smart Form in an event handler. The bigger problem might be getting the response to the user.
Not knowing your exact logic I would recommend:
Use the BOL to retrieve all data.
In the method where you create the button use CL_CRM_WEB_UTILITY to create the JavaScript code for a client callback handler. Then in the handler create the PDF and return it to the user. You can just set the XSTRING to the response.
cheers Carsten

ERP Central Component Enhancement Package 4

Dear friends,
In my company sap ( ECC 6.00) Enhancement package 4 is applicable, I want to confrim what is new for SAP mm in package 1,2,3,4..
Neeru Dimri
SAP MM

Dear Experts,
any please confrim me what is the extra in ECC 6.0 - to - ECC 6.0 EHP4 for SAP MM.
Neeru

BADI for TLB/DEPLOYMENT - Enhancement for Rounding

Hi Experts;
I'm searching for a Badi/User Exit to modify the deployment order quantities; rounding the quantity up to pallet size multiple if the remaining is greater than 0.5 pallet; down to pallet size multiple if the remaining is less than 0.5 pallet. Any comment will be highly appreciated on which badi/user exit for either ''TLB or Deployment'' makes use to write such modification.
Great Thanks ...
elif

Dear Elif
As per my understanding of your requirement, you would want the deployment orders to generate based on the pallet size.
Solution 1:
You can define the lotsize in product location, Transportation lane and you can make setting in Global SNP setting where you can define which lot size to be considered (either Destination Loc prod or T lane).
This SNP planning profile needs to be set while executing the deployment in background.
Solution2:
This can also be met by designing a macro, where you set the min and max ranges.
Rewards points if it helps
Regards
Nav

Need BADI's for TCode IW3K( Order - Component List )

Hi All,
Please help me in finding the BAdI 's/any other enhancements for TCODE iw3k ( Change Order - Component Overview ).
I need to add a button on the screen layout at item level.
Thanks
Lokesh

Hi,
Did you check BADI <b>WORKORDER_UPDATE</b>?
rEGARDS

Error while deleting enhanced component

Hi,
i have enhanced the component 'ICCMP_BP_CP' and the view 'ICCMP_BP_CP/BuPaContactPersonCreat'. When we enhanced the component, it throwed me the error message that user is not authorized for sicf transaction. after getting the authorization, i enhanced the component. But when we we enhanced the view, it was throwing view bind exception in Web UI. so, we deleted the enhanced view and when we are trying to delete the enhanced component 'ICCMP_BP_CP', its throwing the error that 'run time repositry could not be loaded',
After I tried deleting the component enhancement, I can still open that component with enhancement set from BSP_WD_CMPWB but it doesn't show me any repository.xml. Also, I don't see any entry for the enhanced component in BSPWD_CMP_C_REPL.
I am attaching the screen shots like how I am deleting the enhanced component. Could you please tell me how to delete it.
Thanks & Regards,
Kamesh Bathla

Hello,
Open table BSPWDV_COMP_EXT via SM30 and open it with the Enhancement Set in which you created the enhancement you want to delete. (or the view cluster BSPWDVC_CMP_EXT via SM34)
Look for the component for which you want the enhancement to be deleted. Note down the "Runtime Rep. BSP application" and delete the record.
Open the BSP application you noted down in SE80 and delete the (incorrect) enhancements, then delete the whole BSP application.
Restart enhancing the component.
Hope this helps,
Joost

MB1B / Change profit center in Exit, Badi or Enhancement

Hi guys,
we're doing transfer postings in MB1B with reference to existing returns. In the return item a profit center different from the material master is entered. MB1B is creating the material document with the profit center from the materal master.
The requirement is to get the profit center from the return into the material document.
I have tried various ways to meet the requirement:
- Badi MB_DOCUMENT_BADI
- Badi MB_MIGO_ITEM_BADI
- Exit EXIT_SAPLIE01_007
- Enhancement ENHANCEMENT-POINT SEGMENTDATEN_MAT_SETZEN_03
- Enhancement ENHANCEMENT-POINT MM07MFM0_M_SEGMENTE_GENERIE_04
In MB_DOCUMENT_BADI and EXIT_SAPLIE01_007 the profit center can't be changed, MB_MIGO_ITEM is not run through.
In the 2 enhancements the value can be changed, but the profit center in the material document and the follow up documents is still taken from the material master.
Does anybody know where I can change the profit center in this case? (Badi / Exit / Enhancement).
It's a requirement that MB1B has to be used, so using MIGO for this is not a solution.
Thank you very much!
Best regards, Andreas

Hi,
Enhancement - MB_CF001 Customer Function Exit in the Case of Updating a Mat. Doc. is called in the update task.
This could be useful.
Thanks
Sujay

Upgrade issues in moving Exits and BADI Enhancements to ECC 6.0

Hi All,
I want to know when moving customer enhnacements including badis and exits etc., while upgrading from R/3 to may be ECC 6.0 what kind of issues will be encountered .
Will there be manual efforts required to import all of the ones migrated to this new framework.
To my understanding the ones which exits in the same way can be imported in the new system however what about the ones migrated like conventional badis being included in enhancement-spot.
I belive there would be issues because of the new enhancement framework and not all enhancements rather a good number of them would report issues as they might have got incorporated in this new technique.
Please suggest with some logical explanation.
To be precise let me add here, for example we have a badi implementation in old release. now when we import it to ECC 6 where badi implementation exits only in a container Enhacement implementation. Now my question is whether we have to create an enhacement implementaion for the badi implementation or not? i.e manual efforts will be required or not?
thanks and regards,
Vikas.
Message was edited by:
        Vikas Taneja

Hi Nikunj ,
          Thanks , I have one problem . I now installing AFS 6.3 ADDON in our server , While installing i got the message box given below .
REPEAT      SKIP     CUST.COCKPIT
PHASE CHECK_REQUIREMENTS :EXPLANATION OF ERRORS
"THE SYSTEM HAS FOUND THE NUMBER OF OPEN DATA REQUESTS "
Kindly tell me , what i have to do .
Regards
Selvan

Badi ----FDM_COLL_SEND_ITEMS

Hi friends,
I have got this Badi for performing Implementation with the below requirement for one of my Object . Can any one tell me what needs to be done to get this functionality.
You use this Business Add-In (BAdI) in the component SAP Collections Management. You use it to provide additional data for the distribution of data in Collections Management. This data can be prepared for the collection specialists worklist and displayed there. It can also be used to prioritize the business partners to be contacted.
The BAdI is not active in the standard. The requirements for Frischkorn are summarized as follows:
1.     To display the account clerk in the worklist that is displayed for the collections specialist and collections supervisor. Account Clerk is the field that is stored as information for Branch or the responsible person in the branch for managing the customer.
2.     To display the Credit Management Block status of the customer for the Credit Segment in Display. Credit Master data of the Business Partner records information regarding the open or block status of the customer in the Credit Management which either facilitates or restricts postings to the account.
The Table KNB1 stores the Customer Master along with various other Company Code details. The field BUSAB stores the information regarding the accounting clerk in the customer master. Table UKMBP_CMS_SGM stores the block status of the customer for that segment in the field XBLOCKED. As part of standard collections configuration the following Table is updated to store the following information: It also can be determined from this that
Table: FDM_COLL_SFIELD
TABNAME     FIELDNAME     XINITIAL_LOAD
KNB1     BUSAB     X
UKMBP_CMS_SGM     XBLOCKED
The above table is used to identify the fields that need to be sent to the FSCM-Collections Management from Accounts Receivable.
The method COMPLETE_DATA of BAdI FDM_COLL_SEND_ITEMS is used to send additional attributes of a customer or an open item to Collections Management. The call is per customer in a company code in report FDM_COLL_SEND_ITEMS. The additional attributes must be included in the customer include and are as shown as follows:
1.     CI_UDM_COLL_KEYFIG of table UDM_COLL_KEYFIG is used for the key figures of business partner and
2.      the customer include CI_UDM_S_COLL_ITEM_ATTR of table UDM_COLL_ITEM is used for open items
An enhancement has to be made to the above to the customer include in the system where the worklist is created (ie, . UDM_COLL_KEYFIG )
The following are the parameter of the method COMPLETE_DATA
I_KUNNR
Customer number in FI
I_BUKRS
FI company code
IT_KEY_FIGURES
This table contains the key figures of the customer in the relevant company code. The field XINITIAL_LOAD is particularly important:
If the indicator is set, this is a recreation of this customer.
IT_LAST_PAYMENT
This table contains the last payments of the customer.
IT_ITEMS
In the case of a recreation, this table contains all open items of the customer and otherwise only open items that have to be sent due to a change relevant for Collections Management. For the reference to the open item, see the field OPEN_ITEM_REF.
IT_ITEMS_DEL
This table contains the cleared items of the customer (only relevant in the case of a periodic data transfer according to the delta procedure).
CT_EXT_KEY_FIGURES
You can add customer-specific attributes of a customer to table CT_EXT_KEY_FIGURES in the BAdI:
In the field ATTR_ID, transfer the corresponding field names that you have included in the customer include CI_UDM_COLL_KEYFIG of table UDM_COLL_KEYFIG and the relevant value in the field ATTR_VALUE.
CT_EXT_ITEMS
You can add customer-specific attributes of an open item to table CT_EXT_ITEMS in the BAdI:
In the field ATTR_ID, transfer the corresponding field names that you have included in the customer include CI_UDM_COLL_ITEM of table UDM_COLL_ITEM and the relevant value in the field ATTR_VALUE. You also have to add the reference to the open invoice item, which you can transfer from the table IT_ITEMS.
CT_MESSAGES_FOR_LOG
The table CT_MESSAGES_FOR_LOG can be filled with messages that are then displayed in the application log of the program FDM_COLL_SEND_ITEMS. To output messages, use only this table and do not issue any messages directly.
C_XDO_NOT_SEND
If you set this indicator in the BAdI, you can prevent the data being sent for this customer. Note that this indicator must always be set for error messages that occur that you have returned to the calling program in table CT_MESSAGES_FOR_LOG if the data for this customer is not to be sent.
C_XCUSTOMER_DELETE
By setting this indicator in the BAdI, you ensure that the data of this customer is deleted in Collections Management.
Note the difference between the two indicators C_XDO_NOT_SEND and C_XCUSTOMER_DELETE:
If you set the indicator C_XDO_NOT_SEND, no data is sent for this customer. This can be useful, for example, if you want to exclude complete customer groups from Collections Management.
Setting the indicator C_XCUSTOMER_DELETE has the effect that any data existing for this customer is deleted in Collections Management. This can be useful, for example, if you temporarily do not want to handle customers with certain properties in Collections Management.
CT_ITEMS_EXCLUDE
Using table CT_ITEMS_EXCLUDE, you can exclude certain open items (for example, special G/L transactions) in Collections Management.
Table CT_ITEMS_EXCLUDE can only be filled with entries from table IT_ITEMS.
Notes
The data in the BAdI is available in external format. However, the data added must be provided in internal format. This is particularly important for amounts.

Hi Purushotham,
       We need to add 3 fields to Collection Management. if u have a code please post it or mail to [email protected]
Thanks,
Naresh

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

BADI CRM_BP_UIU_DEFAULTS or Component Enhancement?

Similar Messages

Maybe you are looking for