BADI: BADI_SD_SALES( SAP says it was only for internal use)

[Former Member]

Hi Experts,

Badi:BADI_SD_SALES(SAP says it is for internal use): But i was implemented this badi. It is legal or not.

I was implemented badi: BADI_SD_SALES . But it is for SAP internal use.

For implementing this i was changed the field u2018internalu2019 in Standard table: SXS_ATTR.

I removed the X in that field.

All these things done for Creating Return order with reference to invoice. The client requirement is to was external number range instead of internal number rangees.

For this thing I was implement the method t u2018TRANSACTION_INITu2019. I passed the

Our external number in that vbak-vbeln..

It works correctly in development. I am not yet tested in quality and production.

This way is correct one or not. When I removed the u2018Xu2019(Internal use) in field:

SXS_ATTR. In future it gives any other problems or it is legally correct or not.

Helpful answers definitely rewarded.

Regards

Pratap.M

[uwe_schieferstein]

Hello Pratap

Labelling this BAdI as "Internal Use only" SAP can do whatever they want with this BAdI - they may even remove it !!!

Thus, your development relies on something very unreliable.

Perhaps SAP releases this BAdI for general use in the future - or not.

Therefore, I would recommend to use the enhancement framework instead if already available in your SAP system.

Final remark: If you set your implementation of this internal BAdI productive and the customer runs into trouble later on when SAP changes or deletes this BAdI with support packages YOU are liable - and not SAP.

Regards

Uwe

[Former Member]

Hi,

Is there any solution for getting the external number instead of internal number. I am using the Custom BAPI for return order creation.

I passesd the import parameter as a return order number(External number) coming non-sap system.

My team-lead copied the whole all standard bapis in Z-bapis and Standard includes(VA01) in z-includes.

and he achieve that requirement.

I thought this is not a best approach. In future SAP changes in Standard includes this might not be work.

If there any simple solution for this one

Regards

Pratap.M