J1SORDER SAP (CH Interface) Structure details
Description: CH Interface
Structure field list including key, data, relationships and ABAP select examples
J1SORDER 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 "CH Interface" 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_J1SORDER TYPE J1SORDER.
The J1SORDER table consists of various fields, each holding specific information or linking keys about CH Interface data available in SAP. These include MANDT (Client), LFNGNR (IS-M: Sequence Number for Delivery), NACHLFNGNR (Sequence number of subsequent delivery), VBELN (IS-M/SD: Publishing Sales Order).. 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 J1SORDER 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 | |||
LFNGNR | IS-M: Sequence Number for Delivery | LFNGNR | NUMC | 12 | Assigned to domain | LFNGNR | LFG | ||
NACHLFNGNR | Sequence number of subsequent delivery | NACHLFNGNR | NUMC | 2 | NUM2 | ||||
VBELN | IS-M/SD: Publishing Sales Order | AVNR | CHAR | 10 | Assigned to domain | ALPHA | AVNR | JK1 | MJK1 |
POSNR | Sales Order Item | APNR | NUMC | 6 | Assigned to domain | APNR | |||
ETENR | Sales Order Schedule Line | JAENR | NUMC | 4 | Assigned to domain | AENR | |||
JPARVW | IS-M: Business Partner Role | JPARVW | CHAR | 2 | Assigned to domain | PARVW | JPARVW | JGR | |
PARZA | IS-M: Partner Role Counter | JPARZA | NUMC | 3 | JPARZA | ||||
GUELTIGVON | Date from Which Partner Data in Sales Order is Valid | JKPAVON | DATS | 8 | DATUM | ||||
GUELTIGBIS | Date to Which Partner Data in Sales Order is Valid | JKPABIS | DATS | 8 | DATUM | ||||
ADRNR | IS-M: Address Number | JADRNR | CHAR | 10 | Assigned to domain | ALPHA | JADRNR | ||
PLZ_ORDER | IS-M: Postal Code | PLZ_ISP | CHAR | 10 | PSTLZ | ||||
MENGEINZUO | Sch.line qty in order-delivery assignment for partial susp. | MENGEINZUO | DEC | 9 | STMENGE | ||||
ETART | Schedule Line Type for Internal Sales Order Schedule Line | ETART_ISP | CHAR | 2 | Assigned to domain | ETART_ISP | JAE | ||
ETMENGE | IS-M: Sales Order Schedule Line Quantity | ETMENGE | QUAN | 10 | MENGGPOS | ||||
ETMEINS | IS-M: Sales Unit for Sales Order | ETMEINS | UNIT | 3 | Assigned to domain | CUNIT | MEINS | ||
ADRESSVAR | IS-M: Address Variant | ADRESSVAR | CHAR | 1 | ERSTADR | ||||
LAND1 | Country Key | LAND1 | CHAR | 3 | Assigned to domain | LAND1 | LND | ||
ORIGIN | IS-M/SD: Origin of order | JV_ORDER_ORIGIN | CHAR | 1 | JV_ORDER_ORIGIN | ||||
SHIPORDNBR | Address-Based Shipping Order Number | SHIPORDNBR | CHAR | 10 | Assigned to domain | ALPHA | SHIPORDNBR | JVSON | MJVSOA |
SHIPORDPOSNBR | Address-Based Shipping Order Item Number | SHIPORDPOSNBR | NUMC | 8 | Assigned to domain | ALPHA | SHIPORDPOSNBR | JVSOPN | |
POSTEINORT | IS-M: City Number (Unique) | JALORT | CHAR | 8 | Assigned to domain | ALPHA | ALORT | JSO | |
POSTEINSTR | IS-M: Street Number | STRASSENNR | CHAR | 10 | Assigned to domain | ALPHA | STRASSENNR | JSS | |
STRAS | Street Name | STRAS_ISP | CHAR | 35 | TEXT35 | ||||
HAUSN | IS-M: House Number | HSNMR1 | CHAR | 10 | HAUSNUMMER | ||||
HSNMR2 | IS-M: House Number Affix | HSNMR2 | CHAR | 8 | CHAR8 |
Key field | Non-key field |
How do I retrieve data from SAP structure J1SORDER using ABAP code?
As J1SORDER 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 J1SORDER as there is no data to select.How to access SAP table J1SORDER
Within an ECC or HANA version of SAP you can also view further information about J1SORDER 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