SAP CL_BSP_BP_TAX_NATPERSON OO Class - Natural Person indicator for BP
CL_BSP_BP_TAX_NATPERSON 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 CL_BSP_BP_TAX_NATPERSON 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 IF_CRM_BSP_INIT_ILInterface Implementation
This OO class is an Interface Implementation, which means it will implement its own version of the methods from implementation class IF_CRM_BSP_MODEL_ACCESS_ILInterface Implementation
This OO class is an Interface Implementation, which means it will implement its own version of the methods from implementation class IF_CRM_BSP_PROCESS_ILMethod list of CL_BSP_BP_TAX_NATPERSON 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 | Public | |
| CALL METHOD cl_bsp_bp_tax_natperson=>CONSTRUCTOR...more details | ||
CL_BSP_BP_TAX_NATPERSON 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 |
| GC_MODEL_ADDRESS | Instance Attribute | BSP IL Account: Addresses (ODC1) | LIKE CL_BSP_BP_ACCMOD_ADDR_MIX | Private | |
| GC_NATPERS | Constant | LIKE | Private | ||
| GC_PROCESS_CLASS | Constant | Model Access Class | 'CL_BSP_BP_PROMOD' | LIKE CRMT_MODELACCESSCLASS | Private |
| GC_SCREEN_STRUCTURE_NAME | Static Attribute | Name of DDIC Structure Assigned to Layout | 'COMT_BSP_BP_TAX_NATPERS' | LIKE CRMT_BSP_SCREENSTRUCTURE | Protected |
| GC_SPACE | Constant | Space constant | ' ' | LIKE BU_BOOLEAN | Private |
| GC_X | Constant | Boolean Type, Do Not Use in Interfaces! | 'X' | LIKE BU_BOOLEAN | Private |
| GV_LOCKED | Instance Attribute | Boolean Type, Do Not Use in Interfaces! | 'X' | LIKE BU_BOOLEAN | Private |
| GV_NATURAL_PERSON | Instance Attribute | Boolean Type, Do Not Use in Interfaces! | LIKE BU_BOOLEAN | Private | |
| GV_PARTNER | Instance Attribute | Business Partner Number | LIKE BU_PARTNER | Private |
Links to Related Class(s)
CL_BSP_B...Full list of available SAP object classes
Search for further information about these or an SAP related objects