If a user exit is to be implemented, simply copy the sample function module which has a naming standard of /BTI/TE_EXIT_SAMPLE_XXXX (where XXXX = 4 digit user exit number) into the customer name space. This copies across the signature of the function module (Importing, Exporting, Changing, Tables and Exception parameters).

The copied function module should then be implemented to the client’s requirement.

Once implemented, an entry must be added to table /BTI/TE_EXITC. Note that a corresponding entry may also need to be added to /BTI/TE_EXIT if it does not already exist and has been shipped. The entry in /BTI/TE_EXITC requires:

Field Description
EXITID This is the User Exit identifier such as 0010, 0020, etc.
COUNTER This is just the sequence number, starting from 01. However, if the user-exit allows multiple exits to be defined, then this can be incremented for each implemented user-exit (i.e. 01, 02, 03, etc).
EXITFUNC The function module name defined in the customer namespace (e.g. ZABC_TE_EXIT_0010).

Please note the that the following can have impacts across Transport Expresso and should be avoided:
(i) A non active exit added to table /BTI/TE_EXITC.
(ii) A non active exit created in a Function Group which has an existing FM in use.


Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment