RECN_NOTICE_X SAP (Notice and Additional Fields (VICNNT)) Structure details
Description: Notice and Additional Fields (VICNNT)
Related tables to RECN_NOTICE_X
Access table RECN_NOTICE_X
Structure field list including key, data, relationships and ABAP select examples
RECN_NOTICE_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 "Notice and Additional Fields (VICNNT)" 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_RECN_NOTICE_X TYPE RECN_NOTICE_X.
The RECN_NOTICE_X table consists of various fields, each holding specific information or linking keys about Notice and Additional Fields (VICNNT) data available in SAP. These include MANDT (Client), INTRENO (Internal Key of Real Estate Object), NTNO (Number of Notice), NTCATE (Subject of Notice).. 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 RECN_NOTICE_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 | ||||
NTNO | Number of Notice | RECNNTNO | NUMC | 4 | RECNNTNO | ||||
NTCATE | Subject of Notice | RECNNTCATE | CHAR | 1 | Assigned to domain | RECNNTCATE | |||
NTACTIVE | Notice Active | RECNNTACTIVE | CHAR | 1 | RECABOOL | ||||
NTACTIVATEDON | Notice: Date of Activation | RECNNTACTIVATEDON | DATS | 8 | RECADATE | ||||
NTREVERSEDON | Reversal date | RECNNTREVERSEDON | DATS | 8 | RECADATE | ||||
RERF | Entered by | RERF | CHAR | 12 | SYCHAR12 | ||||
DERF | First Entered on | DERF | DATS | 8 | DATUM | ||||
TERF | Time of Initial Entry | TERF | TIMS | 6 | TIMES | ||||
REHER | Source of initial entry | REHER | CHAR | 10 | CHAR10 | ||||
RBEAR | Employee ID | RBEAR | CHAR | 12 | SYCHAR12 | ||||
DBEAR | Last Edited on | DBEAR | DATS | 8 | DATUM | ||||
TBEAR | Last Edited at | TBEAR | TIMS | 6 | TIMES | ||||
RBHER | Editing Source | RBHER | CHAR | 10 | CHAR10 | ||||
NTPER | Contract Notice Per | RECNNTPER | DATS | 8 | RECADATE | ||||
NTRECEIPT | Date of receipt of notice | RECNNTRECEIPT | DATS | 8 | RECADATE | ||||
NTPARTY | Notice Given By | RECNNTPARTY | CHAR | 1 | RECNNTPARTY | ||||
NTEXTRAORD | Reason for Extraordinary Notice | RECNNTEXTRAORD | CHAR | 1 | RECABOOL | ||||
NTREASON | Reason for Notice | RECNNTREASON | NUMC | 2 | TIVCNNTRE | RECNNTREASON | RECNNTREASON | ||
NTREASONREJ | Reason for Rejection | RECNNTREASONREJ | NUMC | 2 | TIVCNNTRR | RECNNTREASONREJ | |||
NTAPPROVEDON | Date notice approved | RECNNTAPPROVEDON | DATS | 8 | RECADATE | ||||
NTREJECTEDON | Date notice rejected | RECNNTREJECTEDON | DATS | 8 | RECADATE | ||||
NTOBJECTIONON | Date of objection to notice | RECNNTOBJECTIONON | DATS | 8 | RECADATE | ||||
NTLEGALDEPTON | Date notice submitted to legal department | RECNNTLEGALDEPTON | DATS | 8 | RECADATE | ||||
NTWITHDRAWALON | Date of withdrawal of notice | RECNNTWITHDRAWALON | DATS | 8 | RECADATE | ||||
NTREQUESTON | Tenant's notice request date | RECNNTREQUESTON | DATS | 8 | RECADATE | ||||
NTFOLLPOSTDUE | Due date for follow-up postings | RECNNTFOLLPOSTDUE | DATS | 8 | RECADATE | ||||
NTREQUESTUSE | Consider Notice Request When Creating Offer | RECNNTREQUESTUSE | CHAR | 1 | RECABOOL | ||||
NTCALCULATED | Date of Calculated Notice | RETMNTCALCULATED | DATS | 8 | RECADATE | ||||
XNTCATE | Name of Subject of Notice | RECNXNTCATE | CHAR | 30 | RECAXMDESCRIPTION | ||||
XNTPARTY | Name of Party Giving Notice | RECNXNTPARTY | CHAR | 30 | RECAXMDESCRIPTION | ||||
XCNPARTNER | Contracting partner | RECNXCNPARTNER | CHAR | 80 | TEXT80 | ||||
XNTREASON | Name of Notice Reason | RECNXNTREASON | CHAR | 30 | RECAXMDESCRIPTION | ||||
XSNTREASON | Name for Notice Reason | RECNXSNTREASON | CHAR | 15 | RECAXSDESCRIPTION | ||||
XNTREASONREJ | Text for Rejection Reason | RECNXNTREASONREJ | CHAR | 30 | RECAXMDESCRIPTION | ||||
XSNTREASONREJ | Name of Rejection Reason | RECNXSNTREASONREJ | CHAR | 15 | RECAXSDESCRIPTION | ||||
HASNOTE | Memo Exists? | RECAHASNOTE | CHAR | 1 | RECABOOL | ||||
ICONHASNOTE | Icon: Memo Exists? | RECAICONHASNOTE | CHAR | 4 | Assigned to domain | ICON | |||
ICONNTCATE | Subject of Notice Icon | RECNICONNTCATE | CHAR | 137 | RECAICON | ||||
ICONNTPER | Icon - Notice Given for Contract On | RECNICONNTPER | CHAR | 137 | RECAICON |
Key field | Non-key field |
How do I retrieve data from SAP structure RECN_NOTICE_X using ABAP code?
As RECN_NOTICE_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 RECN_NOTICE_X as there is no data to select.How to access SAP table RECN_NOTICE_X
Within an ECC or HANA version of SAP you can also view further information about RECN_NOTICE_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