1.6.3 Structure of basic type ZKNVHM01
■ Customer Hierarchy
· Z1KNVHM : Customer Hierarchy
Status : Essential
min. number : 1 , max. number : 1
■ Segment structures
· Z1KNVHM : Customer Hierarchy
SAP ALE IDOC EDI-Kor_11.6.2 Structure of basic type WMMBID02
11.6.2 Structure of basic type WMMBID02
■ Stock movements from ext. systems
· E1MBXYH : Goods movements for mobile data entry (header data)
Status : Essential
min. number : 1 , max. number : 1
o E1MBXYI : Add goods movement from external system: Item
Status : Essential
min. number : 1 , max. number : 9999
§ E1MBXYJ : Create Goods Movement from Non-SAP System: Item++
Status : Optional
min. number : 1 , max. number : 1
SAP ALE IDOC EDI-Kor_11.6.1 Structure of basic type ALEAUD01
11.6 IDOC Type Structures 예제
11.6.1 Structure of basic type ALEAUD01
■ Confirmations of the processing status of inbound IDocs
· E1ADHDR : Message Type etc. of Confirmed IDocs
Status : Essential
min. number : 1 , max. number : 9999999999
o E1STATE : Status Information of IDoc for ALE Audit
Status : Essential
min. number : 1 , max. number : 99999
§ E1PRTOB : IDoc number and application object in receiving system
Status : Optional
min. number : 1 , max. number : 1
SAP ALE IDOC EDI-Kor_11.5.3 Status record
11.5.3 Status record
■ General
IDoc status record from the IDoc interface in the SAP R/3 System to an external system. The record contains information about the processing status of an IDoc.
■ Status record structure
· TABNAM : Name of table structure
internal data type : CHAR
Internal length : 000010 characters
Position in Segment : 001, Offset : 0000. external length : 000010
SAP ALE IDOC EDI-Kor_11.5.2 Data record
11.5.2 Data record
■ General
IDoc data record from the IDoc interface in the SAP R/3 System to an external system.
The data record for Release 4.0 has the structure EDI_DD40. Each IDoc consists of exactly one control record, which is followed by several data records. The data record has organizational information in the first fields, which determines the syntactical construction of an IDoc and assigns the data record to an IDoc. The record also contains structural information about the application data. The field SDATA includes application data (up to 1000 bytes), interpretation occurs field by field via the segment. The segment is in the field SEGNAM.
SAP ALE IDOC EDI-Kor_11.5.1 Control Record
11.5 Control, Data, Status Record
11.5.1 Control record
■ General
IDoc control record for the IDoc interface of the SAP System R/3 to an external system.
The control record for Release 4.0 has the structure EDI_DC40. Each IDoc is initiated by exactly one control record. The record contains control information about outgoing and incoming IDocs as well as their processing in the SAP system and an external system.
SAP ALE IDOC EDI-Kor_11.4 ALE & EDI의 Authorization (Security) Objects
11.4 ALE & EDI의 Authorization (Security) Objects
다음은 ALE와 EDI 개발에 사용되는 몇가지의 authorization objects 목록이다. ALE와 EDI 작업을 하기 위해서 여러분의 user ID에 필요한 것을 권한을 설정하기 위해서 Basis 관리자와 의논해 보기 바란다.
Object ALE/EDI: Maintaining logical systems
Authorization B_ALE_LS_ALL
SAP ALE IDOC EDI-Kor_11.3 Status Codes
11.3 Status Codes
다음은 status codes 목록과 그들에 대한 설명이다.
전달방향(direction): 1 = Outbound,
2 = Inbound
처리계층(processing Layer): A = SAP application
I = IDOC Interface
S = External system / EDI subsystem
SAP ALE IDOC EDI-Kor_11.2 Message Type과 IDOC Type
11.2 Message Type과 IDOC Type
SAP에서 지원하고 있는 message type 목록을 확인하려면, transaction WE81 을 실행하거나 또는 transaction WEDI à Development à Message Types을 실행해 보면 된다. SAP 상에서 IDOC type에 대한 message type 할당 내용을 확인해 보려면 transaction WE82 을 실행하거나 또는 transaction WEDI à Development à IDoc Type / Message 을 실행해 보면 된다. 이러한 Messge Type 및 IDOC type의 숫자는 SAP Version이 올라감에 따라 점차 증가할 것이다.
다음 목록은 SAP에 있는 내용 중 일부를 예로서 제시하는 것이며, 여기에 제시되지 않은 것은 위에서 제시된 방법을 이용하여 SAP R/3에서 직접 그 내용을 확인해 볼 수 있다.
SAP ALE IDOC EDI-Kor_11.1 자주 사용되는 ALE/EDI Transactions
11.1 자주 사용되는 ALE/EDI Transactions
다음은 자주 사용되는 ALE and EDI transactions 목록이다. 시작메뉴에서 다음 transaction을 그대로 사용하거나, 특정 화면을 종료하고, 원하는 transaction을 실행하려면 /N + transaction (example /nBALE)의 형태을 사용하거나 또는 새로은 session을 열어 원하는 transaction을 실행하려면 /O + transaction (example /oBD21) 형태를 사용하라.