A data class is a class that contains only fields and crude methods for accessing other classes. Data classes are classified into four types depending on the type of data they contain -

• Master Data: Data change very rarely.
• Transaction Data: Data changes are depending on requirements.
• Organization Data: Data is a customized and entered to the system when the system is configured. It is rarely changed.
• System Data: Data is used by the SAP R/3 system.

Replicate() and SaveReplica().

RFC is the protocol used to call functions in an R/3 system by a caller external to R/3 or to call programs external to R/3 from an R/3 system. BAPI are RFC enabled function modules.

In an RFC, passing data is by value. The reason behind this is, it’s going to access other system while doing the above by reference wouldn't work as we are into another system whose memory id will not match.

The events triggering order in report is -

• Initialization
• At Selection-Screen
• Start-of-Selection
• Get
• Get Late
• End-of-Selection
• Top-of-Page
• End-of-Page
• At Line Selection
• At User Command
• At PF (nn)

The events are as follows -

• Initialization
• At selection-screen
• Start-of-selection
• End-of-selection
• Top-of-page
• End-of-page
• At line-selection
• At user-command
• At PF
• Get
• At New
• At LAST
• AT END
• AT FIRST

The Business Object Repository (BOR) is the object-oriented repository in the R/3 System.

Yes

When we call a function module, an instance of its function group and its data is loaded into the memory area of the internal session. An ABAP program can load several instances by calling function modules from different function groups.