ALE Settings For Quality Management Master Data

9/27/2019 ALE settings for Quality Management Master Data | SAP Blogs
Community
Ask a Question Write a Blog Post
Dipeshkumar Bhavsar
March 30, 2016 7 minute read
ALE settings for Quality Management Master Data

Following RSS feed Liked
6 Likes 4,261 Views 2 Comments
ALE Settings for Quality Management
1 Basic ALE Settings
1.1 De ne Logical System
Run Transaction SALE in Development environment.
Follow menu path IDoc Interface / Application Link Enabling (ALE) >> Basic Settings >> Logical Systems >>
De ne Logical System.
It is a cross client con guration.
https://blogs.sap.com/2016/03/30/ale-settings-for-quality-management-master-data/ 1/30
Click on New Entry
Enter Logical System as following naming convention
SYSCLNTXXX
Here,
SYS – System name e.g. DEV- Development, QLT-Quality, PRD-Production
CLNT – Client (keep the text CLNT as it is)
XXX – Number of Client e.g. 101, 102, 103 etc.
Now, Save. It will ask for transport request. Create/assign the transport request and get this transport
request transported to all the required environments. This is required activity because it will be used while
creating Partner Pro le. If don’t perform this activity, system will not allow you to create partner pro le with
logical system with this naming.
1.2 Create RFC Connection:

Run Transaction SM59 – Con guration of RFC connections
Or follow the menu path
Select ABAP Connections and click on Create
Enter the RFC Destination, Description, Target Host and instance number. System will pick the IP address
automatically.
RFC destination as per following naming convention (as per logical system)
SYSCLNTXXX
Here,
In Logon and Security Tab, Maintain the Logon Procedure, put destination client, User (ALEUser) and
Password. And Save.
This is the procedure to create RFC Connection. You need to perform this activity in both the Sending and
Receiving System. E.g. in Development Server you need to maintain Quality Server’s RFC and in Quality
Server you need to maintain Development Server’s RFC.
1.3 Port Maintenance

Run the transaction WE21

Select Port Type Transactional RFC and click on Create
Select the radio button for own port name and enter port as following naming convention (Same as logical
system) on the pop up dialog box.
SYSCLNTXXX
Here,
Enter the description and select the RFC destination
Now, Save.
1.4 Create Partner Pro les

Run the transaction code WE20
Select the Partner type LS and Click on create
If you do not enter the logical system de ned in step 1 then you will be facing following error
Enter the Partner number as per the logical system naming convention
SYSCLNTXXX
Here,
Enter Type as US – User, Agent as user ID.
Now, Save.
The Partner pro le is created. You can create Partner pro le in each system as follows
System Partner Pro le Purpose / Data ow

Development QLTCLNT201 (for Quality Client) Development to Quality
system PRDCLNT301 (for Production Development to Production (caution)
Client)
Quality DEVCLNT101 (for Development Quality to Development (caution)
system Client)
PRDCLNT301 (for Production Quality to Production
Client)
Production DEVCLNT101 (for Development Production to Development (caution)
system Client)
QLTCLNT201 (for Quality Client) Production to Quality (caution)
2 Message Types Settings for Quality Management
There are following standard message types available in SAP for Quality Management Master Data.
Message Type Description

QPGR Replication of QM Code Groups/Catalogs
QPMK Replication of QM master inspection characteristics
(ALE)
QSMT Replication of QM inspection methods
MATQM Replication of QM inspection setup
INSPECTIONPLAN_CREATE Create inspection plan
2.1 Code Groups (Message Type QPGR)

We have to following to manage ALE for message type QPGR
Outbound parameter in development server for QLTCLNT201
Inbound parameter in Quality server for DEVCLNT101.
2.1.1 Set outbound parameter in development server for QLTCLNT201
Now, login to development server
In Transaction WE20 (Partner Pro les) select the required partner pro le (e.g. QLTCLNT201 Quality Client
201) under the Logical system.
Click on create outbound parameter
In the next screen enter message type QPGR, Select Transfer IDOC immediately. Enter basic type QPGR01.
And press enter.
After Enter
Now, Save. E.g. in development client you have set outbound parameter for QLTCLNT201.
2.1.2 Set inbound parameter in Quality server for DEVCLNT201
Now, login to Quality System to set inbound parameter.
Scroll down and click on create inbound parameter
Enter Message Type QPGR and Process Code BAPI and select Trigger immediately option.
Now, Save.
2.1.3 Send Code Group
Now, you can send the code groups using QL41 (Send Code Group) from Development server to Quality
Server.
2.2 Master Inspection Characteristics (Message Type QPMK)
We have to following to manage ALE for message type QPMK
Maintain outbound parameter as below screenshot
Maintain inbound parameter as below screenshot
2.2.3 Send Master Inspection Characteristics
Now, you can send the code groups using QL21 (Send Master Inspection Characteristics) from Development
server to Quality Server.
2.3 Inspection Methods (Message Type QSMT)
We have to following to manage ALE for message type QSMT
2.3.3 Send Inspection Methods
Now, you can send the code groups using QL31 (Send Inspection Methods) from Development server to
Quality Server.
2.4 Material Inspection Setup (Message Type MATQM)
We have to following to manage ALE for message type MATQM
2.4.3 Send Inspection Setup
Now, you can send the code groups using QL11 (Send Inspection Setup) from Development server to Quality
Server.
2.5 Inspection Plan (Message Type INSPECTIONPLAN_CREATE)
We have to following to manage ALE for message type INSPECTIONPLAN_CREATE
2.5.3 Send Inspection Plan
There is no transaction code available for sending inspection plan.
But, there is an executable Program (RQ_PLAN_CREATE_SAMPLE_FILE) available in SAP. You can execute it
using transaction SE38.
The Program has a limitation. The parameter ‘receiver’ (logical system) in the program is set as no display.
So, when the user run the program, the user will not be able to de ne the destination logical system and
when you execute the program without destination, the IDoc will get failed. As the IDoc doesn’t have the
destination address. (see the below screenshot)
If you run the program in debugging mode (by putting break point), you will be able to change the parameter
‘receiver’ and IDoc will get processed successfully.
There are few alternatives to achieve sending of inspection plan with the help of Developer.
Option 1: The developer can enhance (implicit enhancement spot available to have additional screen
parameters) the program and put an additional screen parameter (logical system) and then pass the value
of the parameter to ‘receiver’. This will allow the user to de ne destination.
Option 2: The Developer can create a custom program with additional parameter and then call the standard
program within the same with passing all the parameter.
Option 3: The Developer can copy the standard program into a custom program and have this parameter
‘receiver’ as display.
Alert Moderator
Assigned tags
PLM Quality Management (QM) | SAP ERP | ale | ale sap qm | enterprise resource planning |
View more...
Related Blog Posts
Key Quality Management Con guration for Integration with Other Logistic Modules
By Former Member , Nov 19, 2013
Useful QM documents on SCN

By Nancy Guo , Apr 01, 2015
Quality Management - Certi cate of Analysis - Step by Step

By Former Member , Aug 19, 2016
Related Questions
Production Against Sales Order

By Imran Khan , May 09, 2019
By Product quality inspection for HU Managed materails

By Mohan Madaiah , Feb 01, 2018
Inspection lot getting generated even after "No Inspection" is set in Quality Info Record
By Madan Rajen , May 08, 2018
2 Comments
Arijit Banerjee
April 2, 2016 at 7:47 pm

Nice Document. Keep up posting such good documents in future
Like (0) Reply Alert Moderator
Leo Li
August 8, 2016 at 3:33 am

Wonderful , it is very helpful to send the ALE
Like (0) Reply Alert Moderator
Add Comment
Share & Follow
Privacy Terms of Use
Legal Disclosure Copyright
Trademark Cookie Preferences
Sitemap Newsletter

ALE Settings For Quality Management Master Data - SAP Blogs

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ALE Settings For Quality Management Master Data - SAP Blogs

Uploaded by

Copyright:

Available Formats

9/27/2019 ALE settings for Quality Management Master Data | SAP Blogs

Ask a Question Write a Blog Post

6 Likes 4,261 Views 2 Comments

ALE Settings for Quality Management

1 Basic ALE Settings

1.1 De ne Logical System

Run Transaction SALE in Development environment.

It is a cross client con guration.

Click on New Entry

Enter Logical System as following naming convention

SYS – System name e.g. DEV- Development, QLT-Quality, PRD-Production

CLNT – Client (keep the text CLNT as it is)

XXX – Number of Client e.g. 101, 102, 103 etc.

1.2 Create RFC Connection:

Or follow the menu path

Select ABAP Connections and click on Create

SYS – System name e.g. DEV- Development, QLT-Quality, PRD-Production

CLNT – Client (keep the text CLNT as it is)

XXX – Number of Client e.g. 101, 102, 103 etc.

1.3 Port Maintenance

Or follow the menu path

Select Port Type Transactional RFC and click on Create

SYS – System name e.g. DEV- Development, QLT-Quality, PRD-Production

CLNT – Client (keep the text CLNT as it is)

XXX – Number of Client e.g. 101, 102, 103 etc.

Enter the description and select the RFC destination

1.4 Create Partner Pro les

Or follow the menu path

Select the Partner type LS and Click on create

SYS – System name e.g. DEV- Development, QLT-Quality, PRD-Production

CLNT – Client (keep the text CLNT as it is)

XXX – Number of Client e.g. 101, 102, 103 etc.

Enter Type as US – User, Agent as user ID.

System Partner Pro le Purpose / Data ow

2 Message Types Settings for Quality Management

Message Type Description

2.1 Code Groups (Message Type QPGR)

Outbound parameter in development server for QLTCLNT201

Inbound parameter in Quality server for DEVCLNT101.

2.1.1 Set outbound parameter in development server for QLTCLNT201

Now, login to development server

Click on create outbound parameter

2.1.2 Set inbound parameter in Quality server for DEVCLNT201

Now, login to Quality System to set inbound parameter.

Scroll down and click on create inbound parameter

2.1.3 Send Code Group

2.2 Master Inspection Characteristics (Message Type QPMK)

We have to following to manage ALE for message type QPMK

Outbound parameter in development server for QLTCLNT201

Inbound parameter in Quality server for DEVCLNT101.

2.2.1 Set outbound parameter in development server for QLTCLNT201

Maintain outbound parameter as below screenshot

2.2.2 Set inbound parameter in Quality server for DEVCLNT201

Maintain inbound parameter as below screenshot

2.2.3 Send Master Inspection Characteristics

2.3 Inspection Methods (Message Type QSMT)

We have to following to manage ALE for message type QSMT

Outbound parameter in development server for QLTCLNT201

Inbound parameter in Quality server for DEVCLNT101.

2.3.1 Set outbound parameter in development server for QLTCLNT201

Maintain outbound parameter as below screenshot

2.3.2 Set inbound parameter in Quality server for DEVCLNT201