You need to change standard sales processing logic and your requirement cannot be met in Customizing. What options will ensure there are no changes to SAP-delivered objects? Note: There are 3…

Question

Options

• ACustomer exit
• BBusiness transaction event (BTE)
• CEnhancement point
• DSAP Best Practices
• EModification

• A
  81% (46)
• D
  12% (7)
• E
  7% (4)

Explanation

Options A, B, and C represent SAP's user exit and enhancement framework - mechanisms designed specifically to let customers extend or override standard logic by adding code in separate, customer-owned objects, leaving SAP-delivered code untouched. Customer exits (A) use predefined include programs and function modules that SAP ships empty for customer use. Business Transaction Events (B) provide a publish-and-subscribe interface where you register a custom function module that gets called at predefined points in standard processing. Enhancement points (C), part of the SAP Enhancement Framework, let you insert custom code at explicit spots in standard programs via enhancement implementations stored separately from the source object.

D (SAP Best Practices) is wrong because it refers to pre-configured business content and templates - it's a starting point for configuration, not a technique for extending processing logic. E (Modification) is explicitly the opposite of what the question asks: a modification directly alters the SAP-delivered object, breaks the upgrade safety guarantee, and requires re-application after every support package.

Memory tip: Think of A, B, and C as "hooks without touching" - they all work by SAP providing a designated slot, interface, or injection point where your code plugs in around the standard, while E (Modification) means you've put your hands directly on SAP's code. If you can't Customize and don't want to Modify, you Enhance.

No community discussion yet for this question.