topic Re: badi --------------- in Application Development and Automation Discussions

badi ---------------

Former Member — Fri, 12 Oct 2007 12:57:52 GMT

The purpose of this enhancement is to flag shipments where the Loading End status has failed to be set during RF loading . This flag can then be used to identify these shipments so that a scheduled job can attempt to re process them.

This process is Key to the business as the Loading End status triggers the PGI (post goods issue) that issues stock out of the DC into stock in transit.

Currently manual processes are in place to check that shipments have had the Load End status set and that all the deliveries have been PGI. This enhancement will automate the process leaving only the genuine queries to resolve.

This is checking that the shipment is being updated via RF This is the circumstance that we want to add our new code to, we do not want this enhancement to be active for shipments updated manually via VT02N.

HOW TO DEACTIVE THE ENHACE MENT WEN NOT UPDATED BY RF AND DONE MANUALLY

can any one help

Re: badi ---------------

Former Member — Sun, 14 Oct 2007 12:37:19 GMT

Hi abcdef,

try the following suggestion

Please put a breakpoint in the enhancement and see if the the transaction code is getting captured eg: in the debugger find value of sy-tcode...for manual and automated...

if we are having 2 different sy-tcodes catured for manual and automated case..in the exit/enhancement..put all the codes in the if statement

if sy-tcode <> 'Manualtcode' ...code...endif

or we will have to find a unique number or data or field which helps user differentiate whether it is a manual or automated process(shipments updated manually)..eg: in FI we have cases where a field is filled with a particular data (eg: Document type field with 'KR'..just an example)

Pls check,revert and reward if helpful

Regards

Byju

Re: badi ---------------

Former Member — Mon, 15 Oct 2007 03:00:07 GMT

Exits are basically the hooks whcih SAP has provided to add your own code. There are two types of Exits:

1. Customer exits: Implemented as Function Modules within z includes. Anybody can change it and no access key is required.

2. User Exit: Implemented as subroutines within includes (any include except y or z includes). You need access for the specific include and then you can any subroutine (user exit) within that Include.

BADIs are the enhanced version of user exits where the same logic is implemented via classes and object (OOP)

Enchancement point is the latest once introduces with ECC6.0 . Not very sure about that but you can change it without any access key.

Please go through the following link which will help you understand the exits in a much better way:

http://help.sap.com/saphelp_nw04/helpdata/en/bf/ec07a25db911d295ae0000e82de14a/content.htm

http://www.sap-img.com/abap/what-is-the-difference-between-smod-and-cmod.htm

http://sap.niraj.tripod.com/id21.html

http://help.sap.com/saphelp_nw04/helpdata/en/c8/1975cc43b111d1896f0000e8322d00/frameset.htm

http://www.sap-img.com/ab038.htm

User Exits.

http://www.erpgenie.com/sap/abap/code/abap26.htm

http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm

http://www.sapgenie.com/abap/code/abap26.htm