IDoc_Interface_Overview

SAP AG 1999 IDocEnjoy (Th. Becker) / 1

The IDoc InterfaceOverview

R/3 Release


Introduction/Expectations

Name

Expectations from this class

Any prior experience in ALE/IDOC or other Interface technologies


Course Objectives

Course Objectives

After completing this course, you will be able to:

Understand the concept of distributed and it’s pros & cons

SAP Interface technologies and scenarios

IDOC and it’s structure

Detailed overview on ALE/EDI concepts and technology

Perform simple master data distribution using ALE scenario


Agenda

Agenda

Day 1 – IDOC overview

Distributed Architecture

Business scenarios

IDOC and it’s structures

Interfacing scenarios – Outbound / Inbound


2

Distributed Applications

Org HQ Central Ref

Plant

Sales Center

Distribution Center

One central system is not One central system is not always optimal for unifying always optimal for unifying business processes with business processes with integrated applicationsintegrated applications


3

Technical bottlenecks

Too much time required for a group-wide implementation of R/3 central systems

Influences on the market

Company units become independent

Optimization of cross-company business processes

Integrated information exchange across system frontiers

Profiting from a high degree of freedom in a homogeneous system environment

Comprehensible step by step implementation of complex SAP R/3 projects

Why distribute Applications ?Why distribute Applications ?



9

Master Data

Control Data (Customizing)

What is Distributed?

Master Data

Control/Customizing Data

Transaction Data

Statistical Data (Infosystem)



Electronic Commerce

Document

SAP System R/3 SAP System R/3IDoc

EDI SubsystemEDI Subsystem TransactionMessage

IDocIDoc


EDI Standards in the World

EDIFACT

EDIFACT

EANCOMGENCODTRADACOMSUCS II, WINSSEDAS

HL7

ARUAGALIAODETTEVDA

ATA SPEC2000AECMA SPEC2000M

BAI, BAI2MultiCashS.W.I.F.T.HBCI

EDIFER

EDIFICEEIAJ

EANCOMGENCODTRADACOMSUCS II, WINSSEDAS

CEFIC

PHOENIX

EDIFICEELFEX12

X12


IDOC


Why Intermediate Documents ?

Messages must have a defined structure

Easy technical handling ( "Data Container" )

Easy transfer from/to non-SAP systems

Possibility to build complex data structures

Possibility for extension

Possibility for documentation

Link to standard processing ( EDI )

Intermediate Document (IDOC)


The key concepts of IDoc (i.e. Intermediate Document) are: communication is asynchronous and related to one document, i.e. transaction.

Following these concepts IDoc facilitates distributed processes rather simply invoking functions.

IDoc is the SAP standard interface to link application systems via messaging. Whereas one system is asumed to be SAP system R/3, the other system could be

EDI subsystem, system R/3, system R/2 or any third-party application software.

IDoc is available for system R/3 from release 2.1A on.

IDoc is available for system R/2 from release 5.0F on.

Intermediate Document (IDOC)


IDoc Concept

Asynchronous

Document-related

R/3 System

System 1

SAPDocument

EDI subsystem R/3 System R/2 System 3rd party software

System 2

Document Transaction Message

IDoc



IDOC Structure


IDoc Record Types

Status Record IDoc-IDStatus information

Data Record IDoc-IDSequence/HierarchySegment Format definition for

• header data• item data

Control Record IDoc-IDSender-IDReceiver-IDIDoc type and logical messageExternal structure


IDoc Types

Control Record

Status Records

Data Records

Tree of Segments

E1HDDOC

M 1

E1TLSUM

C 1

E1HDADR

C 5

C 99

E1ITSCH

C 5

E1ITDOC

M 1



IDOC Type – MATMAS03


IDoc Data Flow

FiletRFCXML

...

Application

Message Control

IDoc Interface &ALE Services

System 2e.g. EDI subsystem

MMSD...

IDoc

Application

Workflow

IDoc Interface &ALE Services


Outbound Data Inbound


Outbound Data Flow

IDoc

NASTRecord

Document

Document

SAP Application

Message Control (NAST)

System 2, e.g. EDI subsystem

IDoc Interface & ALE Services


IDoc View Concept

An IDoc view is a selection of segments of a given IDoc type and is compatible with the IDoc type‘s syntax.

IDoc views are applied in outbound processing of selected applications.

Advantages of views:

Enhancing the performance by restricting the number of tables read

Reducing the data volume in internal tables at run time


4

ALE (Application Link Enabling)

ALE enables integrated configurations, in which applications are loosely coupled, i.e. asynchronously and not via a common database.

Message-based Architecture

Business Scenarios

Communication Technology

Tools

Methodology

ALE Infrastructure encompasses:

The method and technique for supporting distributed applications.


5

ALE Objectives

Scenarios:

R/3 and R/3

SAP and non-SAP

systems

Support for different application releases

Integration of distributed applications Consistency and synchronization of distributed data

with respect to available database technology

Support for the configuration of distributed applications


6

Using the EDI functionality

Using IDOCs to define the data to be distributed

Using aRFC, TCP/IP, EDI subsystem

Using workflow functions for error handling

Integration into message control (condition technique)

Integration into the application

Integration into customizing

ALE Technique


7

Messaging with ALE

HEAD QUARTERS

PRODUCTION

•Financials•Central purchasing•Purchasing Info. system

•Local purchasing, Invoice verification

BLAOR Blanket order/changesBLAREL Release statisticsEKSEKS Purchasing informationFIDCMT A/C recivableFIROLL G/L rollup

BLAORD-BLAOCH

BLAREL

EKSEKS

FIDCMT

FIROLL


8

Communication between Applications

ALE handles the communication between business applications, not the applications processes themselves

ALE focuses on business requirements, not on technical solutions


10

The Distribution Model

The model tells the applications which messages are to be sent to which partner systems.

SAP supplies a distribution reference model, the documents that may be distributed

From the reference model the customer distribution model is derived. This model defines what will be distributed

The customer distribution model is created in one R/3 system and distributed from there to the other systems

The model directly controls distribution


11

Distribution Reference Model

InventoryControlling

InventoryControlling

InventoryManagement

InventoryManagement

INVCONINVCON

change stockanalyse

stock change

PlantPlantDivDiv BusAreaBusAreaMaterialMaterialFilterObject type

Applicationtype

Functiontype

Messagetype


12

Customer Distribution Model

InventoryControl

InventoryControl

InventoryManagement

InventoryManagement

InventoryControl

InventoryControl

InventoryManagement

InventoryManagement

InventoryManagement

InventoryManagement

DivDiv BusAreaBusArea

Folsom, CA Tsukuba, Japan

100001

INVCON INVCONINVCONKU OR CH


16

Scenarios supported by ALE

Distribution of accounting and logistics

Reallocation between distributed systems

Seperate sales and shipping

Purchasing: distributed contacts

Profitability analysis

Sales and Operations Planning

Logistics Information systems

Warehouse management

Master data distribution

Control data distribution


37

ALE Features Summary

Provides for input and Output Processing

Provides for Communication Control Mechanism

Helps Achieve a Virtual View of a Multi-Client Corporation/Enterprise

Provides Reference Models

Requires a Completed Detailed Enterprise Design

Business Segments

Geographical Area

Business Function

Based on Distribution Model


Message Handling: Output processing: direct

Application posting

Need to create IDOC?

Create master IDOC

Customer Distribution Model

Receiver determination

Segment filter

Field value conversion

Version change

ALE layer

Dispatch controlDatabase

M

Application document posted simultaneously with IDOCs

Comm. layer

asynch. RFCor

EDI

CLinks C


Input processing

Application posting

Field value conversion

ALE layer

Input control

Database

A

Simultaneously update IDOC's status

Comm. layer

asynch. RFCor

EDI

Version change

Segment filter

C

A

Post application document

Process IDOCSerialization


Cross-system application links

IDOC

Sending system Plant 1

4711

Application posting

ALE layer

Sourceapplication document, No. 4711

CRS9876

Link toappl. doc.

Link toappl. doc.

CRSReceiver:

Plant14711

1234

IDOC

Receiving system CRS

9876

Application ALE layer

CRS9876

IDOC: Link toappl. doc.

Plant14711

5678

Link toappl. doc.

Plant11234

Resultant applicationdocument No. 9876

C


Message Control

SAP Application Processing

Application data

Message proposal

NAST-Record

Output, e.g. as IDoc

Output Determination

Processing Programe.g. RSNASTED

Processing acc/ TNAPR


Message Control - Call Sequence

SAP Applicationscommunication

structuresmessagedefault

outputdetermination

message trigger and message status

MessageControl

tableTNAPR

formatting program

... printout fax ALE EDI E-mail ...

conditiontables

conditionelement evaluate

pass suggest

relation

write

statusprocess

call


Message Control - EDI related

Single IDoc

Transfer accordingto output mode

Batch of IDocsby RSEOUT00

RSNASTEDCall ALE Service

Call Selection Module(application)

Read Partner Profile

Check NAST-Reord


Outbound Status Transitions

4237

29

26

02

20

31

01 39

18

03

30

25

4140 12

10

08

06

24

22

04

11

09

07

05

16

14 15

17


Inbound Data Flow

SAP Application

SAP Business Workflow

System 2, e.g. EDI subsystem


Document

IDoc +Process

IDoc

IDoc +Function Module


Inbound Status Transitions

74

52

66

53

62

51

63

56

65

60

68

50

64

61

Notificationsfrom theEDI subsystem prior toIDoc creation,can be received via message TXTRAW.


Process Code, Port and Partner Profile


SAP Application

ProcessCode Port

PartnerProfile


Partner Profile

PartnerMessage

NAST-Key

Process codeLogical message

Outbound

PartnerLogical message

Process codeRecipient of notifications

Inbound

Partner

Recipient of notifications

General

PartnerLogical message

PortIDoc typeEDI structureRecipient of notifications


Port Types of the IDoc Interface

SAP Application


IDocIDoc

MIME

Internet

CPI-C

IDoc &IDoc &statusstatus

R/2

IDocIDoc

tRFC

ALEAny

IDoc &IDoc &statusstatus

File+ RFC

EDIAny

IDocIDoc

ABAP

Any

IDocIDoc

XML

ECAny

2.1 on 3.0 on 3.0 on 3.1 on 4.5 on 4.6 on


Triggering with Port Type „File“

1

Write

IDoc file

4

Read

2

RFC

3

Call

rfcexec

out.script

IDoc Interface

EDI subsystem

1

Write

IDoc fileStatus report

startrfc

in.scriptstatus.script

3

RFC

2

Call

4

Read


Port Type „ABAP“

Own_program

?

Own_function

IDoc InterfaceIDOC_INBOUND_ASYNCHRONOUS


Port Type „XML“

The port type XML isavailable in release 4.6A.

The port type

creates files with data in IDoc/XML format (rendering)

processes files with data in IDoc/XML format (parsing)

For documentation of the format and validation by XML parsers document type definition (DTD) is available for each IDoc type. DTDs are available by IDoc type documentation, transaction WE60.

Measurements for EDI supply-chain messages compared with port type file

XML file is 1.5 to 2 times smaller

XML file inbound to IDoc database is about 10 times slower

Communication, e.g. via http, is not yet available.


Port Type „XML“, ORDERS (Header)

<?xml version = "1.0"?> <ORDERS01> <IDOC BEGIN="1"><EDI_DC40 SEGMENT="1">

<TABNAM><![CDATA[EDI_DC40]]></TABNAM><MANDT>004</MANDT> <DOCNUM>0000000000307013</DOCNUM> <DOCREL>46B</DOCREL><STATUS>30</STATUS> <DIRECT>1</DIRECT> <OUTMOD>3</OUTMOD> <IDOCTYP>ORDERS01</IDOCTYP><MESTYP>ORDERS</MESTYP> <STD>X</STD> <STDVRS>3/70</STDVRS> <STDMES>850</STDMES><SNDPOR>SAPQ99</SNDPOR> <SNDPRT>LS</SNDPRT> <SNDPRN>Q99CLNT004</SNDPRN><RCVPOR>WTBXML</RCVPOR> <RCVPRT>LI</RCVPRT> <RCVPFC>LF</RCVPFC> <RCVPRN>WTBLIEF</RCVPRN><CREDAT>19990622</CREDAT> <CRETIM>074519</CRETIM> <SERIAL>19990622074509</SERIAL> </EDI_DC40>

<E1EDK01 SEGMENT="1"><CURCY>DEM</CURCY> <WKURS>1.00000</WKURS> <ZTERM>0001</ZTERM><BSART>NB</BSART> <BELNR>4500000328</BELNR> <RECIPNT_NO>WTBLIEF</RECIPNT_NO> </E1EDK01>

<E1EDK14 SEGMENT="1"><QUALF>014</QUALF> <ORGID>0001</ORGID> </E1EDK14>


<E1EDK14 SEGMENT="1"><QUALF>013</QUALF> <ORGID>NB</ORGID> </E1EDK14>


<E1EDK03 SEGMENT="1"><IDDAT>012</IDDAT> <DATUM>19990622</DATUM> </E1EDK03>

<E1EDK03 SEGMENT="1"><IDDAT>011</IDDAT> <DATUM>19990622</DATUM> </E1EDK03>

<E1EDKA1 SEGMENT="1"><PARVW>AG</PARVW> <PARTN>WTBKUND</PARTN> <TELF1>06227/341285</TELF1><BNAME>Einkaeufer 1</BNAME><PAORG>0001</PAORG> <ORGTX>Einkaufsorg. 0001</ORGTX> <PAGRU>001</PAGRU> </E1EDKA1>

<E1EDKA1 SEGMENT="1"><PARVW>LF</PARVW> <PARTN>WTBLIEF</PARTN> </E1EDKA1>

<E1EDKA1 SEGMENT="1"><PARVW>WE</PARVW> <LIFNR>0001</LIFNR> <NAME1>Werk 0001</NAME1> <NAME2>Walldorf</NAME2><STRAS>Neurottstrasse 16</STRAS> <ORT01>Walldorf</ORT01> <PSTLZ>69190</PSTLZ><LAND1>DE</LAND1> </E1EDKA1>

<E1EDK02 SEGMENT="1"><QUALF>001</QUALF> <BELNR>4500000328</BELNR><DATUM>19990622</DATUM> <UZEIT>074509</UZEIT> </E1EDK02>

<E1EDK17 SEGMENT="1"><QUALF>001</QUALF> <LKOND>CFR</LKOND> <LKTEXT>Kosten und Fracht</LKTEXT> </E1EDK17>


Port Type „XML“, ORDERS (Item 10)

<E1EDP01 SEGMENT="1"><POSEX>00010</POSEX> <ACTION>001</ACTION> <PSTYP>0</PSTYP><MENGE>7.000</MENGE> <MENEE>PCE</MENEE> <BMNG2>7.000</BMNG2><PMENE>PCE</PMENE> <VPREI>17.77</VPREI> <PEINH>1</PEINH> <NETWR>124.39</NETWR><NTGEW>5.53</NTGEW> <GEWEI>KGM</GEWEI><MATKL>004</MATKL> <BPUMN>1</BPUMN> <BPUMZ>1</BPUMZ><E1EDP20 SEGMENT="1">

<WMENG>7.000</WMENG> <EDATU>19990622</EDATU> </E1EDP20><E1EDP19 SEGMENT="1">

<QUALF>002</QUALF> <IDTNR>WTBMATERIAL</IDTNR> </E1EDP19><E1EDP19 SEGMENT="1">

<QUALF>001</QUALF> <IDTNR>WTBMATERIAL</IDTNR><KTEXT>Testmaterial Thomas Becker</KTEXT> </E1EDP19>

<E1EDP17 SEGMENT="1"><QUALF>001</QUALF> <LKOND>CFR</LKOND><LKTEXT>Kosten und Fracht</LKTEXT> <LPRIO>00</LPRIO> </E1EDP17>

<E1EDPT1 SEGMENT="1"><TDID>BEST</TDID> <TSSPRAS>D</TSSPRAS> <TSSPRAS_ISO>DE</TSSPRAS_ISO><E1EDPT2 SEGMENT="1">

<TDLINE>Dies ist der Einkaufsbestelltext</TDLINE> </E1EDPT2><E1EDPT2 SEGMENT="1">

<TDLINE>Ein schoenes deutsches Wort.</TDLINE> </E1EDPT2></E1EDPT1></E1EDP01>


Port Type „XML“, ORDERS (Item 20 + Trailer)

<E1EDP01 SEGMENT="1"><POSEX>00020</POSEX> <ACTION>001</ACTION> <PSTYP>0</PSTYP><MENGE>17.000</MENGE> <MENEE>PCE</MENEE> <BMNG2>17.000</BMNG2><PMENE>PCE</PMENE> <VPREI>18.33</VPREI> <PEINH>1</PEINH> <NETWR>311.61</NETWR><NTGEW>1588.65</NTGEW> <GEWEI>KGM</GEWEI><MATKL>001</MATKL> <BPUMN>1</BPUMN> <BPUMZ>1</BPUMZ><E1EDP20 SEGMENT="1">

<WMENG>17.000</WMENG> <EDATU>19990622</EDATU> </E1EDP20><E1EDP19 SEGMENT="1">

<QUALF>002</QUALF> <IDTNR>WTBMATERIAL2</IDTNR> </E1EDP19><E1EDP19 SEGMENT="1">

<QUALF>001</QUALF> <IDTNR>WTBMATERIAL2</IDTNR><KTEXT>Materialvariante Thomas Becker</KTEXT> </E1EDP19>

<E1EDP17 SEGMENT="1"><QUALF>001</QUALF> <LKOND>FOB</LKOND><LKTEXT>Frei on Board</LKTEXT> <LPRIO>00</LPRIO> </E1EDP17>

<E1EDPT1 SEGMENT="1"><TDID>BEST</TDID> <TSSPRAS>D</TSSPRAS> <TSSPRAS_ISO>DE</TSSPRAS_ISO><E1EDPT2 SEGMENT="1">

<TDLINE>Will man das Material bestellen, so wird der Einkaufsbestelltext</TDLINE> </E1EDPT2>

<E1EDPT2 SEGMENT="1"><TDLINE>sicherlich bei der Entscheidung helfen.</TDLINE>

</E1EDPT2><E1EDPT2 SEGMENT="1">

<TDLINE>Oder auch nicht!?</TDLINE> </E1EDPT2></E1EDPT1></E1EDP01>

<E1EDS01 SEGMENT="1"><SUMID>002</SUMID> <SUMME>436</SUMME> <SUNIT>DEM</SUNIT> </E1EDS01>

</IDOC></ORDERS01>


Port Type „XML“, DTD for IDoc type ORDERS01

<!ELEMENT ORDERS01 (IDOC+) ><!ELEMENT IDOC (EDI_DC40, E1EDK01, E1EDK14*, E1EDK03*, E1EDK04*, E1EDK05*, E1EDKA1*, E1EDK02*, E1EDK17*, E1EDK18*, E1EDKT1*, E1EDP01*, E1EDS01*) ><!ELEMENT EDI_DC40 (TABNAM, MANDT?, DOCNUM?, DOCREL?, STATUS?, DIRECT, OUTMOD?, EXPRSS?, TEST?, IDOCTYP, CIMTYP?, MESTYP, MESCOD?, MESFCT?, STD?, STDVRS?, STDMES?, SNDPOR, SNDPRT, SNDPFC?, SNDPRN, SNDSAD?, SNDLAD?, RCVPOR, RCVPRT, RCVPFC?, RCVPRN, RCVSAD?, RCVLAD?, CREDAT?, CRETIM?, REFINT?, REFGRP?, REFMES?, ARCKEY?, SERIAL?) ><!ELEMENT E1EDK01 (ACTION?, KZABS?, CURCY?, HWAER?, WKURS?, ZTERM?, KUNDEUINR?, EIGENUINR?, BSART?, BELNR?, NTGEW?, BRGEW?, GEWEI?, FKART_RL?, ABLAD?, BSTZD?, VSART?, VSART_BEZ?, RECIPNT_NO?, KZAZU?, AUTLF?, AUGRU?, AUGRU_BEZ?, ABRVW?, ABRVW_BEZ?, FKTYP?, LIFSK?, LIFSK_BEZ?, EMPST?, ABTNR?, DELCO?, WKURS_M?) >...<!ELEMENT E1EDP01 (POSEX?, ACTION?, PSTYP?, KZABS?, MENGE?, MENEE?, BMNG2?, PMENE?, ABFTZ?, VPREI?, PEINH?, NETWR?, ANETW?, SKFBP?, NTGEW?, GEWEI?, EINKZ?, CURCY?, PREIS?, MATKL?, UEPOS?, GRKOR?, EVERS?, BPUMN?, BPUMZ?, ABGRU?, ABGRT?, ANTLF?, FIXMG?, KZAZU?, BRGEW?, PSTYV?, EMPST?, ABTNR?, ABRVW?, WERKS?, LPRIO?, LPRIO_BEZ?, ROUTE?, ROUTE_BEZ?, LGORT?, VSTEL?, DELCO?, MATNR?, VALTG?, HIPOS?, HIEVW?, E1EDP02*, E1EDP03*, E1EDP04*, E1EDP05*, E1EDP20*, E1EDPA1*, E1EDP19*, E1EDP17*, E1EDP18*, E1EDPT1*) ><!ELEMENT E1EDP02 (QUALF?, BELNR?, ZEILE?, DATUM?, UZEIT?, BSARK?, IHREZ?) >...<!ELEMENT MESTYP (#PCDATA) ><!ELEMENT MFRNR (#PCDATA) >...<!ATTLIST IDOC BEGIN (1) #REQUIRED ><!ATTLIST EDI_DC40 SEGMENT (1) #REQUIRED ><!ATTLIST E1EDK01 SEGMENT (1) #REQUIRED >...<!ATTLIST E1EDP01 SEGMENT (1) #REQUIRED ><!ATTLIST E1EDP02 SEGMENT (1) #REQUIRED >...<!ATTLIST E1EDS01 SEGMENT (1) #REQUIRED >


Error Processing______________________________


Outbound Data Flow w/ Notification Points

IDoc

NASTRecord

Document

SAP application

Message Control

IDoc Interface

EDI subsystem

EDIM Message

EDIX IDoc w/syntax error

EDIP

EDIO IDoc

IDoc batch

EDIN Message w/NAST record

Status report

EDIS

EDIRCustomer

EDIL Message forStatus report


Inbound Data Flow w/ Notification Points

EDIM Message

EDII IDoc

EDIY IDoc w/syntax error

ApplicationIDoc w/oapplication document

TXTRAW IDoc message

SAP application

IDoc Interface

IDoc

EDI subsystem

IDoc


Table of Notification Tasks

Roleresolution

30000001 Administrator, system profile

70000141 Partner profile, system profile30000001 Administrator, system profile 30000013 Representative, partner profile30000013 Representative, partner profile 30000013 Representative, partner profile 30000013 Representative, partner profile00000134 Representative, partner profile

30000001 Administrator, system profile 30000001 Administrator, system profile30000001 Administrator, system profile

30200013 Party from selection screen

Task

TS30000020

TS70008037TS60001307TS00007989TS00008070

TS00008068TS00008074TSnnnnnnnn

TS70008373 TS30000078TS70008125

TS30200108

EDIM

EDINEDIPEDIOEDIX

EDIIEDIYapplication

EDILEDISEDIR

RSEIDOCM

Processcode

All application tasks can be found by the logical message as search term!


Error Processing via Workflow

Application posting

ALE layer

M

Comm. layer

asynch. RFCor

EDI

C

A C

!?

!?

!?

!?

Error-processing Workflow

Outbound

Inbound


Error Processing

Errors are processed locally within the system in that the error occurred

Standard tasks exist for all ALE errors

If an error occurs, an event triggers the standard task which starts the error processing workflow

The responsible people obtain a workitem in their inbox

The error message attached to the IDOC is displayed

The IDOC can be resubmitted at the end of error processing

The standard tasks supplied by SAP have got the default name '<message type>_error'.


Who is responsible?

The system finds the responsible persons by:

determination of persons by using the staffing schedule of the organizational unit or position with which the standard task is linked

determination of persons defined in the partner profile (by means of their user ID, position or organizational unit)

The overlap of the two groups of persons makes up the pool of employees who receive a work item

Responsible

Org. unit

Responsible

Partner profile


Assigning People to Error Tasks

Create an organizational unit

Create a position for the organizational unit

Assign a user to the position

Assign the error standard task to the position

Transaction: OOOE


Manual Resubmission

There also exist a possibility to reprocess IDOCs without using the workflow

For this you have to detect the IDOCs that produced an error manually

You can resubmit IDOCs with ALE-outbound errors

ALE-inbound errors

Application errors

For ALE-outbound errors (status:02, 04, 05, 25,29):Menu: Logistics -> Central functions -> Distribution -> Period.work -> IDoc, ALE output ->

Process ALE error For ALE-inbound errors (status: 56, 61, 63, 65):

Menu: Logistics -> Central functions -> Distribution -> Period.work -> IDoc, ALE input ->

Process ALE error For application errors:

Menu: Logistics -> Central functions -> Distribution -> Period.work -> IDOC, ALE input -> Edit error


Questions ...