SAPTechnical Idoc & Ale

  • View
    29

  • Download
    5

Embed Size (px)

DESCRIPTION

SAP- setting of idoc and ale.

Text of SAPTechnical Idoc & Ale

SAPTechnical.COM - Step-by-step guide to ALE and IDOCs

15 September 2014

PM 11:30

Home Trainings Quiz Tips Tutorials Functional Cert Q's Interview Q's Jobs Testimonials Advertise Contact Us

SAP Virtual/Onsite TrainingsDocument Categories:

ABAPTM Adobe Forms ABAP-HR ALE & IDocs ALV BAPI BASIS BSP Business Objects Business Workflow CRM NEW LSMW SAP Script/Smart Forms BI/BW eXchange Infrastructure (XI) Enterprise Portals (EP) eCATT Object Oriented Programming SAP Query Userexits/BADIs WebDynpro for Java/ABAPTM OthersWhat's New?

ABAP Test Cockpit HOT SAP ABAP Pragmas Understanding SE32 (ABAP Text Element Maintenance) Creating an IDoc File on SAP Application Server Understanding Advance with dialog option of SAP Workflow SAP Workflow Scenario: Maintenance Notification Approval Enhancements to a standard class Working with Floating Field in Adobe Forms Inserting data from Internal Table into the step Send Mail Display GL Account long text using enhancement framework Differences between polymorphism in JAVA and ABAP Passing multiline parameters from an ABAP Class event to a Workflow container Concept of Re-evaluate agents for active work items in SAP Workflow Dynamic creation of component usage in ABAP WebDynpro Adobe Forms: Display symbols like copyright and others Deactivate Hold functionality in Purchase order (ME21N) Quiz on OOABAP Add fields in FBL5N using BADIs Tutorial on Wide casting Defining a Range in Module Pool Program Copy fields from one structure/table into another structure/table Side Panel Usage in NWBCContribute?Sample SpecsWhat's Hot?

Web Dynpro for ABAP TutorialsJoin the Mailing List

Enter name and email address below:

Name:

Email:

Subscribe Unsubscribe Step-by-step guide to ALE and IDOCs

By Shankar Reddy Chamala, ITChamps Software

Introduction to EDI and ALE:

EDI (Electronic Document interchange) - EDI is the electronic exchange of business documents between the computer systems of business partners, using a standard format over a communication network.

EDI is also called paperless exchange.

Advantages:

Reduced Data entry errors

Reduced processing time

Availability of data in electronic form

Reduced paperwork

Reduced Cost

Reduced inventories and better planning

Standard means of communications

Better business process

EDI has two process

1. Outbound process

2. Inbound process

Outbound Process:

1.Application document is created.

2. IDOC is generated

3.Idoc is transferred from SAP to Operating system layer

4.Idoc is converted into EDI standards

5.Edi document is transmitted to the business partner

6.The Edi Subsystem report status to SAP

Inbound Process:

1.EDI transmission received

2.EDI document is converted into an IDOC

3.IDOC is transferred to the SAP layer

4.The application document is created

5.The application document can be viewed.

IDOC:

IDOC is a container that can be used to exchange data between any two processes.

Each IDOC is assigned a unique number for tracking and future reference.

IDOC consists of several segments, and segments contain several fields.

IDOC contains the following three types of records...

1. One Control Record.

2. One or many Data Record

3. One or many Status record.

In IDOCs the following terms are to be known.

PORT:

Port is used in the outbound process to determine the name of the EDI subsystem program, the directory path where the IDOC file will be created at the operating system level, the IDOC file names and the RFC destinations.

RFC Destination:

Used to define the characteristics of communication links to a remote system on which a functions needs to be executed.

Partner Profile:

Partner profile specified the various components used in an outbound process (Partner number, IDOC type, message type, Port, Process code), the mode in which it communicates with the subsystem (batch or immediate) and the person to be notified in case of errors.

Message Control

Used in pricing, account determination, material determination, and output determination. The message control component enables you to encapsulate business rules with out having to write ABAP programs.

TO Process IDOCS the following TCODES will be used.

On both sides:

Logical System Names SALE

Setup RFC destinations SM59

Port Destinations WE21

In Source system:

Segment Creation WE31

Basic IDOC Type Creation WE30

Message Type Creation WE81

Assign Message Type To Basic IDOC Type WE82

Distribution Model BD64

Writing Report Program SE38

Partner Profile WE20

Message control NACE

Check IDOCs WE02, WE05

In Destination System:

Creating FM SE37

Assign FM to Logical Message WE57

Define I/P method for Inbound FM BD51

Create Process Code WE42

Generate Partner Profile BD64 IDOC processing in the same instance of R/3 Clients.

For example two clients in the same R/3 instance.

Client 900.

Client 800.

To transfer the data between two clients the table structures and their data types should be match.

In this example, Client 900 is Source system, and Client 800 is destination system.

In Client 900 I have created a customized table and inserted some records.

In Client 800 I have created only table.

Common Steps in Both Clients: Creating the Logical System Names and Assigning to Clients:

Go to TCODE SALE.

IMG path IDoc Interface / Application Link Enabling (ALE) -> Basic Settings -> Logical Systems -> Define Logical System

Click on Display / Change Button

Click on New Entries

Specify the Logical System name and description.

Note: Logical System Naming convention is CLNT

Click on Save and Back buttons

Now you will come back to the IMG path screen. Click on Assign Logical System to client.

Click on Display / Change Button

Click on New Entries

Click on Save and Back. Click here to continue...

SAPTechnical.COM - Step-by-step guide to ALE and IDOCs

15 September 2014

PM 11:31

Home Trainings Quiz Tips Tutorials Functional Cert Q's Interview Q's Jobs Testimonials Advertise Contact Us

SAP Virtual/Onsite TrainingsDocument Categories:

ABAPTM Adobe Forms ABAP-HR ALE & IDocs ALV BAPI BASIS BSP Business Objects Business Workflow CRM NEW LSMW SAP Script/Smart Forms BI/BW eXchange Infrastructure (XI) Enterprise Portals (EP) eCATT Object Oriented Programming SAP Query Userexits/BADIs WebDynpro for Java/ABAPTM OthersWhat's New?

ABAP Test Cockpit HOT SAP ABAP Pragmas Understanding SE32 (ABAP Text Element Maintenance) Creating an IDoc File on SAP Application Server Understanding Advance with dialog option of SAP Workflow SAP Workflow Scenario: Maintenance Notification Approval Enhancements to a standard class Working with Floating Field in Adobe Forms Inserting data from Internal Table into the step Send Mail Display GL Account long text using enhancement framework Differences between polymorphism in JAVA and ABAP Passing multiline parameters from an ABAP Class event to a Workflow container Concept of Re-evaluate agents for active work items in SAP Workflow Dynamic creation of component usage in ABAP WebDynpro Adobe Forms: Display symbols like copyright and others Deactivate Hold functionality in Purchase order (ME21N) Quiz on OOABAP Add fields in FBL5N using BADIs Tutorial on Wide casting Defining a Range in Module Pool Program Copy fields from one structure/table into another structure/table Side Panel Usage in NWBCContribute?Sample SpecsWhat's Hot?

Web Dynpro for ABAP TutorialsJoin the Mailing List

Enter name and email address below:

Name:

Email:

Subscribe Unsubscribe Step-by-step guide to ALE and IDOCs

...Previous Creating the RFC Connection Names:

Go to TCODE SALE. Direct TCODE SM59

IMG Path IDoc Interface / Application Link Enabling (ALE) -> Communication -> Create RFC Connections

Click on Create button.

Specify all the details in RFC connection screen

Click on Logon Security tab and specify the details.

Click on the Special options tab and specify the details which you want.

Now click on Test Connection button

It show the connection log in next screen

Click on Back

Click on Remote Logon Button

Depends upon your settings the destination client will open. If you check the Current user option under Logon/ Security tab, then it will show the screen directly without asking the user name and password details.

Creating RFC ports:

Go to TCODE WE21

Select the Transactional RFC in left side tree and click on Create button

In dialog box you can select either Generate port name or own port name. If you select Generate Port name system will generate automatically. Here I selected Own port name. Click on continue.

Specify the description and RFC destination name.

Click on Save.

Repeat the same above process in other client. By using opposite client instead of 900 specify 800. In Client 900 steps: Creating table structure:

Go to TCODE SE11.

Specify table name as ZSTUDENTS.

In Delivery and Maintenance tab set attributes as Display Maintenance Allowed

The table fields are.

Insert some rec