SAP /SCMTMS/CL_ADDR_BUFFER_MOCKING OO Class - Address Buffer Mocking
/SCMTMS/CL_ADDR_BUFFER_MOCKING is a standard SAP object class available within R/3 SAP systems depending on your version and release level. You can view/maintain the class details by entering its name into the relevant SAP transactions such as SE24, SE80 or even SE84. Below is the documentation available for class /SCMTMS/CL_ADDR_BUFFER_MOCKING including details of:
- Interface class implementations
- Inheritance details
- Methods defined within class ( including link to full details )
- Attributes ( including initial values )
- Class Events
Interface Implementation
This OO class is an Interface Implementation, which means it will implement its own version of the methods from implementation class /BOBF/IF_FRW_BUFFERMethod list of /SCMTMS/CL_ADDR_BUFFER_MOCKING SAP class
A method is a coding block that performs a certain procedure (i.e. ABAP functionality) on an object within the overall SAP class. In simple terms if the object is an SAP database table a method could be the procedure to add a record or to delete a record. If you are new to OO in many respects, the implementation of a method is similar to a function module and can be called in a very similar way using CALL METHOD.
Instead of "CALL FUNCTION", Methods are referenced using the following syntax: CALL METHOD =>methodname EXPORTING/IMPORTING...
| Method Name | Description | Visability |
| CONSTRUCTOR | Private | |
| CALL METHOD /scmtms/cl_addr_buffer_mocking=>CONSTRUCTOR...more details | ||
| GET_KEY | Private | |
| CALL METHOD /scmtms/cl_addr_buffer_mocking=>GET_KEY...more details | ||
| MAP_ADDR_NODE_KEY | Map address instance key | Public |
| CALL METHOD /scmtms/cl_addr_buffer_mocking=>MAP_ADDR_NODE_KEY...more details | ||
| TRANSLATE_STATE_TO_BEF_IMG | Private | |
| CALL METHOD /scmtms/cl_addr_buffer_mocking=>TRANSLATE_STATE_TO_BEF_IMG...more details | ||
/SCMTMS/CL_ADDR_BUFFER_MOCKING attributes
List of attributes within class CL_ABAP_CHAR_UTILITIES. These can be referenced using the following syntax CL_ABAP_CHAR_UTILITIES=>. Although depending on where you are inserting the ABAP code you do need to check if the attribute is public or private.
| Name | Level | Description | Initial Value | Type | Visability |
| MO_ADDR_ENCODE | Static Attribute | Encoding routines for BAS Node Ids | LIKE /BOFU/CL_ADDR_ENCODE | Private | |
| MO_CONF | Instance Attribute | Interface for Configuration | LIKE /BOBF/IF_FRW_CONFIGURATION | Private | |
| MS_NODE | Instance Attribute | Configuration: Node | LIKE /BOBF/S_CONFRO_NODE | Private | |
| MV_BO_KEY | Instance Attribute | Business Object | LIKE /BOBF/OBM_BO_KEY | Private | |
| SO_INSTANCE | Static Attribute | Address Buffer Mocking | LIKE /SCMTMS/CL_ADDR_BUFFER_MOCKING | Private |
/SCMTMS/CL_ADDR_BUFFER_MOCKING types
TY_KEYS -Links to Related Class(s)
/SCMTMS/...Full list of available SAP object classes
Search for further information about these or an SAP related objects