RETM_POSTING_PY_SPLIT_X SAP (Posting Term: Split for Posting Rules) Structure details
Description: Posting Term: Split for Posting Rules
Related tables to RETM_POSTING_PY_SPLIT_X
Access table RETM_POSTING_PY_SPLIT_X
Structure field list including key, data, relationships and ABAP select examples
RETM_POSTING_PY_SPLIT_X is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "Posting Term: Split for Posting Rules" Information within sap ABAP programs.
This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.
i.e. DATA: wa_RETM_POSTING_PY_SPLIT_X TYPE RETM_POSTING_PY_SPLIT_X.
The RETM_POSTING_PY_SPLIT_X table consists of various fields, each holding specific information or linking keys about Posting Term: Split for Posting Rules data available in SAP. These include MANDT (Client), INTRENO (Internal Key of Real Estate Object), TERMTYPE (Term Category), TERMNO (Term Number).. See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .
Delivery Class:Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Can be enhanced (character-type or numeric)
SAP RETM_POSTING_PY_SPLIT_X structure fields - Full list of fields found in SAP data dictionary
Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
MANDT | Client | MANDT | CLNT | 3 | Assigned to domain | MANDT | |||
INTRENO | Internal Key of Real Estate Object | RECAINTRENO | CHAR | 13 | RECAINTRENO | ||||
TERMTYPE | Term Category | RETMTERMTYPE | CHAR | 4 | TIVTMTERMTYPE | RETMTERMTYPE | |||
TERMNO | Term Number | RETMTERMNO | CHAR | 4 | VITMTERM | ALPHA | RETMTERMNO | ||
VALIDFROM | Valid-From Date of Term | RETMTERMVALIDFROM | DATS | 8 | RECADATEBEG | ||||
CDSPLITNO | Number of Condition Split | RETMCDSPLITNO | NUMC | 4 | NUMC4 | ||||
VALIDTO | Valid-To Date of Term | RETMTERMVALIDTO | DATS | 8 | REDAT | RECADATEEND | |||
EQUINUM | Equivalence Number | RECAEQUINUM | INT4 | 10 | |||||
HASROUNDDIFF | Rounding Differences | RETMHASROUNDDIFF | CHAR | 1 | RECABOOL | ||||
PARTNER | Business Partner Number | BU_PARTNER | CHAR | 10 | Assigned to domain | ALPHA | BU_PARTNER | BPA | BUPA |
PYMTMETH | Payment Method | RERAPYMTMETH | CHAR | 4 | CHAR4 | ||||
PYMTBLOCK | Payment block key | RERAPYMTBLOCK | CHAR | 4 | CHAR4 | SPE | |||
PYMTTERM | Terms of Payment Key | RERAPYMTTERM | CHAR | 4 | ZTERM | ||||
DUNNAREA | Dunning Area | RERADUNNAREA | CHAR | 4 | CHAR4 | ||||
DUNNBLOCK | Dunning Block | RERADUNNBLOCK | CHAR | 4 | CHAR4 | ||||
BANKDETAILID | Bank Details ID | RERABANKDETAILID | CHAR | 15 | CHAR15 | ||||
TERMNOOA | Term Number | RETMTERMNO | CHAR | 4 | ALPHA | RETMTERMNO | |||
SEPAMNDID | SEPA Mandate: Unique Reference to Mandate per Vendor | RETMSEPAMNDID | CHAR | 35 | RETMSEPAMNDID | ||||
SEPARECCRDID | SEPA Mandate: Creditor ID | RETMSEPARECCRDID | CHAR | 35 | RETMSEPACRDID | ||||
XPARTNER | Name/Address of Business Partner | REBPXPARTNER | CHAR | 80 | TEXT80 | ||||
COUNTRY | Country Key | LAND1 | CHAR | 3 | Assigned to domain | LAND1 | LND | ||
ISDEBITCN | General Yes/No Field | RECABOOL | CHAR | 1 | RECABOOL | ||||
ISCREDITCN | General Yes/No Field | RECABOOL | CHAR | 1 | RECABOOL |
Key field | Non-key field |
How do I retrieve data from SAP structure RETM_POSTING_PY_SPLIT_X using ABAP code?
As RETM_POSTING_PY_SPLIT_X is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on RETM_POSTING_PY_SPLIT_X as there is no data to select.How to access SAP table RETM_POSTING_PY_SPLIT_X
Within an ECC or HANA version of SAP you can also view further information about RETM_POSTING_PY_SPLIT_X and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects