ALE settings for Quality Management Master Data

 ALE Settings for Quality Management

1 Basic ALE Settings

1.1 Define Logical System

Run Transaction SALE in Development environment.

Follow menu path IDoc Interface / Application Link Enabling (ALE) >> Basic Settings >> Logical Systems >> Define Logical System.

It is a cross client configuration.

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 Profile. If don’t perform this activity, system will not allow you to create partner profile with logical system with this naming.

 

1.2 Create RFC Connection:

Run Transaction SM59 – Configuration 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,

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.

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

Or follow the menu path

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,

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

Now, Save.

 

1.4 Create Partner Profiles

Run the transaction code WE20

Or follow the menu path

Select the Partner type LS and Click on create

If you do not enter the logical system defined in step 1 then you will be facing following error

Enter the Partner number as per the logical system 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.

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

Now, Save.

The Partner profile is created. You can create Partner profile in each system as follows

System	Partner Profile	Purpose / Data flow
Development system	QLTCLNT201 (for Quality Client)	Development to Quality
	PRDCLNT301 (for Production Client)	Development to Production (caution)
Quality system	DEVCLNT101 (for Development Client)	Quality to Development (caution)
	PRDCLNT301 (for Production Client)	Quality to Production
Production system	DEVCLNT101 (for Development Client)	Production to Development (caution)
	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 Profiles) select the required partner profile (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

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

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

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

Maintain inbound parameter as below screenshot

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

Outbound parameter in development server for QLTCLNT201

Inbound parameter in Quality server for DEVCLNT101.

2.4.1 Set outbound parameter in development server for QLTCLNT201

Maintain outbound parameter as below screenshot

2.4.2 Set inbound parameter in Quality server for DEVCLNT201

Maintain inbound parameter as below screenshot

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

Outbound parameter in development server for QLTCLNT201

Inbound parameter in Quality server for DEVCLNT101.

2.5.1 Set outbound parameter in development server for QLTCLNT201

Maintain outbound parameter as below screenshot

2.5.2 Set inbound parameter in Quality server for DEVCLNT201

Maintain inbound parameter as below screenshot

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 define 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 define 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.

Source: https://community.sap.com/t5/enterprise-resource-planning-blogs-by-members/ale-settings-for-quality-management-master-data/ba-p/13303257

Setting Up Scheduling Agreements in SAP MM

 This document provides an overview of how to set up and use scheduling agreements with release documentation in SAP MM for forecast and just-in-time (JIT) delivery schedules. It covers creating the necessary master data, generating the different schedule types, and how creation profiles control schedule aggregation.

Key Sections from the document are:

• Material master data setup with JIT indicator
• Creation profiles for release documentation
• Assigning creation profile to vendor master
• Creating a scheduling agreement with release documentation
• Generating forecast and JIT delivery schedules
• How creation profile controls aggregation of forecast vs JIT schedules
• Reviewing schedule release documents

Download PDF – Setting Up Scheduling Agreements in SAP MM

You might also be interested in these posts

• SAP PP MRP User Training Document
• SAP User Manual for Preventive Maintenance Plan Creation and Scheduling
• SAP MM: End User Training Manual
• SAP HCM Personnel Administration Manual for Noobs
• Source List in SAP MM: Step-by-Step Guide to Preferred Vendors & Time-Bound Ordering

Source: https://www.sapdocs.info/14058/setting-up-scheduling-agreements-in-sap-mm/

Generation of QR code in SAP S/4 HANA

 

Significance of QR code in SAP industry

Nowadays QR codes are everywhere, from products to websites and their marketing. Many businesses and applications have increased the use of QR readers and scanners. Smartphones and tabs come with built-in QR readers these days. Unlike barcodes which are vertical stripes, QR codes are made up of square-shaped patterns. Barcodes are read in one direction from top to bottom hence only a small amount of information can be stored. QR codes are read in two directions which makes it two -dimensional from top to bottom and right to left. This means it can store more data. When compared to bar codes, QR codes are protected against duplication and less error-prone. Consumer-facing marketing campaigns have increased usage as smartphones and tabs with digital cameras can easily read and interpret using this technology. It is also because of the major advantage of QR code that it can be scanned from both papers and from a screen, unlike barcode which can be only scanned from paper.

QR code has also become popular and is used in applications including the automotive industry, product tracking, item identification, plant maintenance, time tracking, warehouse management, document management, and general marketing. Thus, most of the organizations using SAP solutions have stepped up and are using a QR Code generator and readers in their warehousing applications for enterprise management solutions. It has empowered the warehouse workers and operators with efficiency, data accuracy, and stock estimation by quick data entry with no manual errors.

Brief on SAPscript

SAPscript programming is a special code that enables SAP systems to print the content to specific printers. Each model of the printer has a specific script developed that supports the required formats. SAPscript programming very transparent to users because of its seamless integration. It is very beneficial for organizations that rarely change their printer and label formats. For any additional label output, the organization might need an additional solution which might be a drawback.

Steps to generate QR code in SAP S/4 Hana

In this blog, I will show you the steps to generate a QR code with the help of S/4 Hana screens. Although it is a technical solution, it does not require knowledge of ABAP or programming. I have covered all the steps to create a QR code in SAPscript and print it. So, to print a QR code, let us begin with creating one.

Step 1: Go to transaction SE73 (SAPscript Font Maintenance) then select the radio button for “System Bar Codes” and click the “Display” button as per the below screen.

This will open a new screen with a list of all the existing Bar code templates as shown in the below screenshot.

Step 2: Now click on the “Create” button. It will open a pop-up to choose the Barcode methods to be created. Here click on the “New” button to create a new Barcode.

Step 3: Provide the new “Bar code name” in the input box and a suitable description in the input box provided for “Short Text” and click on the “Continue” button as shown in the screenshot.

For Example: ZQRCODE and QR Code-2021

Step 4: In this step, select the supported Bar Code Symbologies as “QR Code 2005” in the pop-up and click on the “Continue” button.

Step 5: Next pop-up appears on the screen to select the Bar code alignment. Select the radio button for “Normal” and click on “Continue”.

Step 6: This is next pop-up for setting up the QR code 2005 Bar code Parameters. For the input box for Mode, I have provided “A” as in Automatic. There are other modes available as below:

A – AUTOMATIC

N – NUMERIC

L – ALPHANUMERIC

B – BYTE_LATIN1

K – KANJI

U – BYTE_UTF8

1 – FNC1_POS1 (FNC1 in first position)

2 – FNC1_POS2 (FNC1 in second position)

For the Module Size input, provide a Numeric Entry such as “00025”.

In the Error Correction Level input, I have provided H, below are the other options.

L – 7 % Error Correction capability

M – 15% Error Correction capability

Q – 25% Error Correction capability

H – 30% Error Correction capability

Click the “Continue” button to proceed.

Step 7: Save the Bar Code definition by clicking on “Yes” button then click “Continue”.

This will ask for a Workbench TR to capture the configuration. Provide a TR or create a new TR and save.

Step 9: In this step you will see the created QR code in the list as you can see in the below screenshot. Select the QR code you have created and click “Test Bar code.

Step 10: In this step, you can see your Bar code Name and Bar code Data. Click “Execute”.

Step 11: Provide the output device as ‘LP01” and click “Print preview” button.

It will create the QR code as you can see on the preview screen.

Finally we have created a QR code in SAPscript.

Conclusion

The QR code is a versatile at the same time beneficial in terms of security and effieciency for both customers as well as vendors. It can quickly and easily connect the users to the information. The best QR code generator depends on different parameters and needs of your products as you can find many different online.

Source: https://community.sap.com/t5/enterprise-resource-planning-blogs-by-members/generation-of-qr-code-in-sap-s-4-hana/ba-p/13503832#:~:text=Steps%20to%20generate%20QR%20code%20in%20SAP%20S/4%20Hana&text=So,%20to%20print%20a%20QR,as%20per%20the%20below%20screen

Vendor consignment with SAP Extended warehouse management EWM

 Vendor consignment is a procurement process when the vendor is not needed to be paid immediately on goods receipt of the materials. Vendor still owns the goods after it is delivered from its own premises and received in customer’s premises as consignment stock. Liability to pay (to the vendor) arises only when the goods are withdrawn from the consignment stock and taken into ‘Own stock’. Vendor consignment is used to optimize the inventory and reduce the liability towards the vendor.A typical vendor consignment process is depicted in below image.

Standard SAP ERP supports vendor consignment from very early days of R/3 or ECC . SAP Extended warehouse management (EWM) also supports vendor consignment as illustrated in this blog.

A typical process flow for vendor consignment with SAP ERP or S/4HANA and EWM is depicted in below image and described as below.

(1)   A purchase order with item category K (consignment) is created. Price is nil as the item category is K (consigment).

(2)   An inbound delivery is created in ERP with reference to that purchase order .

(3)   An inbound delivery is created in EWM with item usage as C(Consignment stock) and stock type F1 (Received on dock).

(4)   Good receipt is completed in EWM inbound delivery which triggers PPF message towards ERP updating the ERP inbound delivery .

And a warehouse task is created for movement of goods from the goods receipt zone to the destination bin.

(5)   ERP stock gets updated as vendor consignment corresponding to the vendor with storage location ROD (Received on dock).

A material document is created in ERP with movement type 101 as displayed in purchase order history of the purchase order.

The material document has no accounting document (and hence no liability to pay to the vendor on goods receipt of stock as vendor consignment) .

(6) Stock is subsequently putaway to the destination bin and the stock appears as consignment stock in EWM warehouse monitor .

(7) Stock now appears as consignment stock in ERP storage location (Available for sale).

Stock is still in consignment stock (with no liability to pay) as is evident from MB51.

(8) When the material is required, posting change is carried out in EWM for the transfer of ownership from the vendor to the own stock (plant or party entitled to dispose) with reference to the corresponding handling unit.

With the creation of warehouse task for the stock to be used for own consumption.

(9) Ownership of stock is then transferred from the vendor to own stock as depicted in the material document created in ERP with movement type 411 K . Material document has now an accounting document to create the liability for the vendor .

Value in the accounting document matches with the purchasing info record for material for consignment.

Vendor consignment is supported in both embedded and decentralized deployments.

This blog is based on my personal insights, observation, and tests. Will appreciate your views / comment and feedback.

Source: https://www.linkedin.com/pulse/vendor-consignment-sap-extended-warehouse-management-ewm-mrinal-k-roy-bazbf/?utm_source=share&utm_medium=member_ios&utm_campaign=share_via