COOI_EAML SAP (Data Transfer Within FGroup BWOMO/BWOMR) Structure details
Description: Data Transfer Within FGroup BWOMO/BWOMR
Structure field list including key, data, relationships and ABAP select examples
COOI_EAML 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 "Data Transfer Within FGroup BWOMO/BWOMR" 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_COOI_EAML TYPE COOI_EAML.
The COOI_EAML table consists of various fields, each holding specific information or linking keys about Data Transfer Within FGroup BWOMO/BWOMR data available in SAP. These include MANDT (Client), REFBT (Reference document category (conversion exit; c.f. REFBTYP)), REFBN (Reference Document Number), RFPOS (Item number of reference document).. 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 COOI_EAML 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 | T000 | MANDT | |||
REFBT | Reference document category (conversion exit; c.f. REFBTYP) | CO_REFBTYP | NUMC | 3 | REFBT | BELEGTYP | |||
REFBN | Reference Document Number | CO_REFBN | CHAR | 10 | ALPHA | BELNR | |||
RFPOS | Item number of reference document | CC_RFPOS | NUMC | 5 | NUMC05 | ||||
RFKNT | Account assignment number of reference document | CC_RFKNT | NUMC | 5 | NUMC05 | ||||
RFTRM | Deadline item of reference document | CC_RFTRM | NUMC | 5 | NUMC05 | ||||
RFART | Reference document type | CC_RFART | CHAR | 1 | CHAR1 | ||||
LIFNR | Account Number of Vendor or Creditor | LIFNR | CHAR | 10 | LFA1 | ALPHA | LIFNR | LIF | KRED_C |
LEDNR | Ledger for Controlling objects | LEDNR | CHAR | 2 | ALPHA | LEDNR | |||
OBJNR | Object number | J_OBJNR | CHAR | 22 | ONR00 | J_OBJNR | ONR | ||
HRKFT | CO key subnumber | CO_SUBKEY | CHAR | 14 | Assigned to domain | CO_SUBKEY | |||
RFORG | Reference Organizational Units | AWORG | CHAR | 10 | AWORG | ||||
RFTYP | Reference Transaction | AWTYP | CHAR | 5 | TTYP | AWTYP | |||
RFSYS | Logical system of source document | AWSYS | CHAR | 10 | TBDLS | ALPHA | LOGSYS | ||
VRGNG | CO Business Transaction | CO_VORGANG | CHAR | 4 | Assigned to domain | J_VORGANG | |||
GJAHR | Fiscal Year | GJAHR | NUMC | 4 | GJAHR | GJAHR | GJR | ||
WRTTP | Value Type | CO_WRTTP | CHAR | 2 | CO_WRTTP | ||||
VERSN | Version | VERSN | CHAR | 3 | TKA09 | ALPHA | COVERSI | KVS | |
SAKTO | Cost element | SAKTO | CHAR | 10 | Assigned to domain | ALPHA | SAKNR | ||
VBUND | Company ID of trading partner | RASSC | CHAR | 6 | T880 | ALPHA | RCOMP | PGS | |
PARGB | Trading partner's business area | PARGB | CHAR | 4 | TGSB | GSBER | GSB | ||
BEKNZ | Debit/credit indicator | BEKNZ | CHAR | 1 | BEKNZ | BEKNZ | |||
TWAER | Transaction Currency | TWAER | CUKY | 5 | TCURC | WAERS | FWS | ||
UNAME | User Name | UNAME | CHAR | 12 | UNAME | ||||
BLDAT | Document Date | CO_BLDAT | DATS | 8 | DATUM | ||||
BUDAT | Expected debit date | CO_PODAT | DATS | 8 | DATUM | ||||
PERIO | Period | CO_PERIO | NUMC | 3 | PERBL | VPE | |||
BUKRS | Company Code | BUKRS | CHAR | 4 | T001 | BUKRS | BUK | C_T001 | |
KOKRS | Controlling Area | KOKRS | CHAR | 4 | TKA01 | CACCD | CAC | ||
MATNR | Material Number | MATNR | CHAR | 18 | MARA | MATN1 | MATNR | MAT | S_MAT1 |
MATKL | Material Group | MATKL | CHAR | 9 | T023 | MATKL | MKL | S_WBWG | |
SGTXT | Segment text | CO_SGTXT | CHAR | 50 | TEXT50 | ||||
GESMNG | Planned quantity | MENGE1 | QUAN | 15(3) | MENGV8 | ||||
MEINH | Unit of Measure | CO_MEINH | UNIT | 3 | T006 | CUNIT | MEINS | ||
MEGBTR | Total Quantity | MEGXXX | QUAN | 15(3) | MENGV8 | ||||
MBGBTR | Total quantity entered | MBGXXX | QUAN | 15(3) | MENGV8 | ||||
MEINB | Posted Unit of Measure | MEINB | UNIT | 3 | T006 | CUNIT | MEINS | ||
WKURS | Exchange Rate | WKURS | DEC | 9(5) | EXCRT | KURSP | |||
ORGWTH | Planned value in local currency | WERTH1 | CURR | 15(2) | WERTV8 | ||||
WHGBTR | Total value in local currency | WHGXXX | CURR | 15(2) | WERTV8 | ||||
ORGWTK | Planned value in controlling area currency | WERTK1 | CURR | 15(2) | WERTV8 | ||||
WKGBTR | Total Value in Controlling Area Currency | WKGXXX | CURR | 15(2) | WERTV8 | ||||
ORGWTT | Planned value in transaction currency | WERTT1 | CURR | 15(2) | WERTV8 | ||||
WTGBTR | Total Value in Transaction Currency | WTGXXX | CURR | 15(2) | WERTV8 | ||||
ORGWTO | Planned value in object currency | WERTO1 | CURR | 15(2) | WERTV8 | ||||
WOGBTR | Total Value in Object Currency | WOGXXX | CURR | 15(2) | WERTV8 | ||||
ORGWTL | Planned value in ledger currency | WERTL1 | CURR | 15(2) | WERTV8 | ||||
WLGBTR | Total value in ledger currency | WLGXXX | CURR | 15(2) | WERTV8 | ||||
LOEKZ | Deletion Indicator in Purchasing Document | ELOEK | CHAR | 1 | ELOEK | ||||
DABRZ | Reference Date for Settlement | DABRBEZ | DATS | 8 | DDAT | ||||
TIMESTMP | Seconds since 1.1.1990,0:00 GMT * 10000 | RKE_TSTMP | DEC | 16 | RKE_TSTMP | ||||
.INCLU--AP | 0 | ||||||||
START_POINT | Start Point | EAML_START_POINT | CHAR | 18 | EAML_POINT | ||||
END_POINT | End Point | EAML_END_POINT | CHAR | 18 | EAML_POINT | ||||
LINEAR_LENGTH | Length in SI Unit | EAML_LINEAR_LENGTH_SI | FLTP | 16(16) | EAML_POINT_SI | ||||
LINEAR_UNIT | Unit of Measurement for Linear Data | EAML_LINEAR_UNIT | UNIT | 3 | Assigned to domain | CUNIT | MEINS | EAML_H_T006 |
Key field | Non-key field |
How do I retrieve data from SAP structure COOI_EAML using ABAP code?
As COOI_EAML 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 COOI_EAML as there is no data to select.How to access SAP table COOI_EAML
Within an ECC or HANA version of SAP you can also view further information about COOI_EAML 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