7/25/2019 Ale or Edi Business Process

1/4

Electronic Data Interchange(EDI) andApplication Link Enabling(ALE) are used to exchange business

data between systems. The IDoc interface consists of the definition of a data structure, along with

rocessing logic for this data structure. The integration ser!iceApplication Link Enabling(ALE) enables

the integration of business rocesses that ha!e been de!eloed across multiple"A# systems or external

systems. The data structure is the IDoc. The IDoc is the exchange format common to all the

communicating systems.

The Interface Adviserprovides support for designing and implementingpermanent interfaces between SAP components and external components.

You can access the Interface Adviserin SAPNet.

The outut or follow u rocessing of artner$deendent messages is automated !ia %essage

&ontrol. The alication then calls the Message Controlusing the secified interfaces.

The RFCis an SAP interface protocol, which simplifies the programming of communication

processes between systems. The RFCsenable you to call and execute predefined functions in a

remote system, or in the same system. The RFCsmanage the communication process, parameter

transfer, and error handling. n the !"## #ngine the RFCfunctions are implemented by the !Co

RFCPro$ider ser$ice, which is used for processing A%AP to !a$a re&uests. A feature is pro$ided

for recei$ing calls from the SAP systems ' this is done by registering the !"## #ngine as a RFC

destination. Technically, the ser$ice is based on the !Co (SAP !a$a Connector).

The scenarios are intended to describe a wor* process as simply and as realistically as

possible. They are templates or starting points for the business processes you are setting

up, but do not necessarily represent your indi$idual procedure. The #+ scenarios do notco$er con$ersion of the +oc standard into an #+ standard (such as #+FACT,

+#TT#, or A-S . /"). This con$ersion is performed by an external #+ subsystem.0ou therefore remain in the +oc standard when testing the scenario.

7/25/2019 Ale or Edi Business Process

2/4

#+ business processes are usually modeled according to the following procedure1

+efault settings and usage are described first on the sender side, then on the recipient side.

To use the Test Toolof the +oc interface to test the processes in onesystem, you can

con$ert the outbound message (outbound +oc) into an inbound message (inbound +oc). Todo this, you need to swap the sender and recipient in the control record.

0ou can use the +oc displayto call and chec* the generated +ocs in the system.

') The legacy system can, of course, be an * system or + system with industry

materials. During data transfer, the system con!erts the industry materials into retail

articles. owe!er, this only alies in the case of different systems. To con!ert industry

materials into retail articles in the same system, you must use rogram %%%%#-I.

+)

The following master data ob2ects can be distributed1 Change numbers (f a change number is

distributed using the message type #C33AS, it contains1 Change master record (in long text if

a$ailable), Alternati$e dates, 4alidity, b2ect types for change master record, b2ect

management records (in long text if a$ailable)), Article master record

http://link25.click%28%29/http://link26.click%28%29/http://link26.click%28%29/http://link25.click%28%29/

7/25/2019 Ale or Edi Business Process

3/4

5ser master record

Purchasing info record

%usiness process

Classification, class and characteristics

Conditions

Cost center

Cost center group

Cost element group

Cost element

Customer master record

Acti$ity type

Acti$ity master record

Acti$ity type group

4endor master record

3aterial master record

5nit of measure for cost center and cost element combination

Source list

6uman Resources1 6R 3aster +ata, rgani7ational +ata

Profit Center

89: Account

%ill of material (materials and documents)

Acti$ity price of cost center and cost element combination

7/25/2019 Ale or Edi Business Process

4/4

4alue Scale and ;uota Scale

A:# business process library, #+ application scenarios.