REYC_SF_DOC_AYC5 SAP (Document: CAM Expense Recovery) Structure details
Description: Document: CAM Expense Recovery
Related tables to REYC_SF_DOC_AYC5
Access table REYC_SF_DOC_AYC5
Structure field list including key, data, relationships and ABAP select examples
REYC_SF_DOC_AYC5 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 "Document: CAM Expense Recovery" 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_REYC_SF_DOC_AYC5 TYPE REYC_SF_DOC_AYC5.
The REYC_SF_DOC_AYC5 table consists of various fields, each holding specific information or linking keys about Document: CAM Expense Recovery data available in SAP. These include BUSTYPE (Object Type), BUSKEY (Object key), XMBUSOBJ (Complete Object Identification, for Example BE 1000/123), BUKRS (Company Code).. 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 (Deep)
SAP REYC_SF_DOC_AYC5 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 |
BUSTYPE | Object Type | SWO_OBJTYP | CHAR | 10 | Assigned to domain | OJ_NAME | OBJ | ||
BUSKEY | Object key | SWO_TYPEID | CHAR | 70 | SWO_TYPEID | ||||
XMBUSOBJ | Complete Object Identification, for Example BE 1000/123 | RECAIDENT | CHAR | 50 | CHAR50 | ||||
BUKRS | Company Code | BUKRS | CHAR | 4 | T001 | BUKRS | BUK | C_T001 | |
RESPONSIBLE | Person Responsible | RECARESPONSIBLE | CHAR | 12 | Assigned to domain | XUBNAME | USER_COMP | ||
INTRENO | Internal Key of Real Estate Object | RECAINTRENO | CHAR | 13 | RECAINTRENO | ||||
OBJNR | Object Number | RECAOBJNR | CHAR | 22 | Assigned to domain | J_OBJNR | ONR | ||
OBJRELGUID | GUID: Business Partner Object Relationship | REBPOBJRELGUID | RAW | 16 | RECAGUID | ||||
PARTNER | Business Partner Number | BU_PARTNER | CHAR | 10 | BUT000 | ALPHA | BU_PARTNER | BPA | BUPA |
ROLE | Business Partner: Role | REBPROLE | CHAR | 6 | TB003 | BU_ROLE | |||
ADDRTYPE | Address Type | REBPADDRTYPE | CHAR | 10 | TB009 | BU_ADRKIND | |||
XPARTNER | Name/Address of Business Partner | REBPXPARTNER | CHAR | 80 | TEXT80 | ||||
PARTN_CAT | Business partner category | BU_TYPE | CHAR | 1 | BU_TYPE | BPY | |||
PARTN_GRP | Business Partner Grouping | BU_GROUP | CHAR | 4 | Assigned to domain | BU_GROUP | BPP | ||
SEARCHTERM1 | Search term 1 for business partner | BU_SORT1 | CHAR | 20 | BU_SORT1 | ||||
SEARCHTERM2 | Search term 2 for business partner | BU_SORT2 | CHAR | 20 | BU_SORT1 | ||||
COMM_TYPE | Communication Method (Key) (Business Address Services) | AD_COMM | CHAR | 3 | TSAC | AD_COMM | |||
CPACT | Correspondence Activity | RECPCPACT | CHAR | 4 | TIVCPCT | RECPCPACT | |||
FMSEQNO | Sequence No. of Entry in Correspondence Activity | RECPFMSEQNO | NUMC | 4 | NUMC4 | ||||
RECIPGRP | Recipient Group for Exactly One Document | RECPRECIPGRP | CHAR | 2 | CHAR2 | ||||
RECIPCATE | Selection of Recipient in Corresp. Activity | RECPRECIPCATE | CHAR | 1 | RECPRECIPCATE | ||||
RECIPROLE | Role of Recipient | RECPRECIPROLE | CHAR | 6 | TB003 | BU_ROLE | |||
RECIPSUBROLE | Role Type of Recipient | RECPRECIPSUBROLE | CHAR | 4 | TIVBPSUBROLE | REBPSUBROLE | |||
RECIPFINDHIER | Search for Recipients in Superior Objects | RECPRECIPFINDHIER | CHAR | 1 | RECABOOL | ||||
FNAME | Form | RECPFNAME | CHAR | 15 | TIVCPFM | RECPFNAME | |||
XFNAME | Name of Form | RECPXFNAME | CHAR | 30 | RECAXMDESCRIPTION | ||||
FORMTYPE | Form Formatting Type | FPTOOLTYPE | CHAR | 1 | FPTOOLTYPE | ||||
SFNAME | Smart Form or PDF-Based Form | RECPSFNAME | CHAR | 30 | FPNAME | ||||
TDCOPIESFM | Number of Copies | RECPTDCOPIESFM | NUMC | 3 | TDCOPIES | ||||
TDDEVICETYPE | Output Type | RECPTDDEVICETYPE | CHAR | 1 | RECPTDDEVICETYPE | ||||
TDDEVICEICON | Icon for Output Type | RECPTDDEVICEICON | CHAR | 137 | RECAICON | ||||
XMAILORFAXNO | E-mail Address or Fax Number | RECPXMAILORFAXNO | CHAR | 241 | SO_STRI241 | ||||
TDNEWID | New Spool Request | RECPTDNEWID | CHAR | 1 | RECABOOL | ||||
TDCOVTITLE | Spool Description | SYPRTXT | CHAR | 68 | SYCHAR68K | ||||
SUBTYPE | Correspondence-Dep. Identification for Output Activity | RECPSFSUBTYPE | CHAR | 32 | CHAR32 | ||||
LANGU | Language for Document Creation | RECPSFLANGU | LANG | 1 | Assigned to domain | ISOLA | SPRAS | ||
.INCLU-_SP | 0 | ||||||||
BUKRS_SP | Company Code | BUKRS | CHAR | 4 | T001 | BUKRS | BUK | C_T001 | |
RECNNR_SP | Contract Number | RECNNUMBER | CHAR | 13 | ALPHA | RECNNUMBER | RECNNR | RECNCN | |
RECNTYPE_SP | Contract Type | RECNCONTRACTTYPE | CHAR | 4 | TIV26 | SMVART | RECNTYPE | RECNCONTRACTTYPE | |
RECNBEG_SP | Date of contract start | RECNCNBEG | DATS | 8 | RECADATE | ||||
RECNENDABS_SP | Term End Date | RECNCNENDABS | DATS | 8 | REDAT | RECADATEEND | |||
RECNTXT_SP | Contract name | RECNTXT | CHAR | 80 | XTEXT80 | ||||
RECNDACTIV_SP | Contract activation | DAKTV | DATS | 8 | DATUM | ||||
RECNNOTPER_SP | Contract Notice Per | RECNNTPER | DATS | 8 | RECADATE | ||||
RECNNOTRECEIPT_SP | Date of receipt of notice | RECNNTRECEIPT | DATS | 8 | RECADATE | ||||
RECNNOTREASON_SP | Reason for Notice | RECNNTREASON | NUMC | 2 | TIVCNNTRE | RECNNTREASON | RECNNTREASON | ||
RECNDAKTKU_SP | Notice: Date of Activation | RECNNTACTIVATEDON | DATS | 8 | RECADATE | ||||
BENOCN_SP | Site That Belongs to Contract | RECNBENOCN | CHAR | 8 | Assigned to domain | SWENR | REBDBENO | REBDBENO |
Key field | Non-key field |
How do I retrieve data from SAP structure REYC_SF_DOC_AYC5 using ABAP code?
As REYC_SF_DOC_AYC5 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 REYC_SF_DOC_AYC5 as there is no data to select.How to access SAP table REYC_SF_DOC_AYC5
Within an ECC or HANA version of SAP you can also view further information about REYC_SF_DOC_AYC5 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