Intra company STO with in the plant between two EWM Managed warehouses

 Introduction:

Now a days multiple warehouses are connected to a single plant where stock transfer happens from one storage location to another storage location which helps in efficient procurement strategies. Here we can usually post without value since the transferred material is managed with in the same plant and therefore has the same valuation data as before. In this blog post, I will be discussing Intra Company STO with in the plant between two EWM managed warehouses i.e. supplying as well as receiving plant are same.

We can Transfer the goods between Storage locations in two ways:

• Without Shipping Point in the Purchase Order, we can transfer the goods/products by using MM – STO. (Without Delivery and Without Billing)
• With Shipping Point in the Purchase Order, we must maintain some Configurations Settings. (With Delivery and Without Billing)

Configuration:

• Define Shipping Data for Plants
• Configure Delivery Type & Availability Check Procedure by Plant
• Assign Document Type, One-Step Procedure, Underdelivery Tolerance
• Activate Stock Transfer Between Storage Locations
• Assign Delivery Type and Checking Rule According to Storage Location
• Define Shipping Data for Stock Transfers Between Storage Locations
• Define Rule for Determination of Shipping Point
• Assign Shipping Points According to Storage Location
• Assign Warehouse Number to Plant and Storage Location
• Assign Warehouse Numbers from Logistics Execution
• Map Storage Locations from ERP System to EWM

STO FLOW:

• Create PO in the supplying plant (here supplying and receiving plants are same)
• Create outbound Delivery in VL10B.
• Check for the available stock in the Storage location.
• Go to Outbound Delivery Request of the supplying plant warehouse & complete GI process.
• Check for the stock in the supplying plant which must have been reduced.
• Check for the Inbound delivery number which got generated automatically in the background w.r.t outbound.
• Then go to inbound delivery request and complete the WH process in the receiving plant.
• Check for the stock report in the receiving plant.

Below mentioned three steps are mandatory fields to obtain the shipping tab in the PO:

• Define Shipping Data for Plants
• Configure Delivery Type & Availability Check Procedure by Plant
• Assign Document Type, One-Step Procedure, Under delivery Tolerance

These are the mandatory steps we need to maintain to get the shipping tab.

Configuration Path:

Define Shipping Data for Plants:

SPRO –> IMG –> Material Management –> Purchasing –> Purchase order –> Set up Stock Transport order –> Define Shipping Data for Plants

We can assign the customer in the supplying Plant for this process. (i.e., the supplying and Receiving Plant are same for this process.)

Configure Delivery Type & Availability Check Procedure by Plant:

SPRO –> IMG –> Material Management –> Purchasing –> Purchase order –> Set up Stock Transport order –> Assign Delivery Type and Checking Rule

Assign Document Type, One-Step Procedure, under delivery Tolerance:

SPRO –> IMG –> Material Management –> Purchasing –> Purchase order –> Set up Stock Transport order –> Assign Document Type, One-Step Procedure, Under delivery Tolerance

Activate Stock Transfer Between Storage Locations:

SPRO –> IMG –> Material Management –> Purchasing –> Purchase Order –>Set up Stock Transport Order–>Set Up Stock Transfer Between Storage Locations–>Activate Stock Transfer Between Storage Locations

Configure Delivery Type & Availability Check Procedure by Storage Location:

SPRO –> IMG –> Material Management –> Purchasing –> Purchase Order –> Set up Stock Transport Order –> Set Up Stock Transfer Between Storage Locations –>Configure Delivery Type & Availability Check Procedure by Storage Location

In this Step we can maintain

• Purchase document category 'F' , here use PO type UB, supplying plant, issue storage location and delivery type(prefer to create new delivery type by copying delivery type 'NL' replenish delivery.)

In this step we can create new delivery type by copying from the standard delivery type.

SPRO –>IMG –> Logistics Execution –> Shipping –> Deliveries –>Define Delivery Types

Here I create the new delivery Type as “SL” by copying from the standard one “NL”.

Here I am assigning the Supplying Plant, Supplying storage location and Delivery Type to Document Type.

Define Shipping Data for Stock Transfers Between Storage Locations:

SPRO –> IMG –> Material Management –> Purchasing –> Purchase Order –> Set up Stock Transport Order –> Set Up Stock Transfer Between Storage Locations –>Define Shipping Data for Stock Transfers Between Storage Locations

In this step we can assign Sales organization, Distribution Channel, Shipping Point and Division to the Plant and later select the Plant and click on the Storage location.

By maintaining the data click on the save button.

Define Rule for Determination of Shipping Point:

SPRO –> IMG –> Logistics Execution –>Shipping –> Basic Shipping Functions –>Shipping Point and Goods Receiving Point Determination–>Set Up Storage-Location-Dependent Shipping Point Determination–>Define Rule for Determination of Shipping Point

Assign Shipping Points According to Storage Location:

SPRO –> IMG –> Logistics Execution –> Shipping –> Basic Shipping Functions –>Shipping Point and Goods Receiving Point Determination –>Set Up Storage-Location-Dependent Shipping Point Determination –>Assign Shipping Points According to Storage Location

Assign Warehouse Number to Plant and Storage Location:

SPRO –> IMG –> Enterprise Structure –> Assignment –> Logistics Execution–>  Assign Warehouse Number to Plant and Storage Location

Assign Warehouse Numbers from Logistics Execution

SPRO –> IMG –> SCM Extended Warehouse Management–> Extended Warehouse Management–> Interfaces –> ERP Integration –> General Settings –> Assign Warehouse Numbers from Logistics Execution

Map Storage Locations from ERP System to EWM

SPRO –> IMG –> SCM Extended Warehouse Management–> Extended Warehouse Management–> Interfaces –> ERP Integration –> Goods Movements–> Map Storage Locations from ERP System to EWM

Testing:

 

	Details	Supplying Plant	Receiving Plant
1	Plant	5PL1	5PL1
2	Warehouse no	5EWM	4EWM
3	Product	7243	7243
4	Shipping point	5SP1	5SP1
5	Purchase organization	5POR
6	Customer	1029900577
7	Sales Area (Sorg/D.ch/Div)	5SPO/01/01
8	Storage Location	AFS	AFS1

 

	ECC Delivery type	ECC Item Category	EWM Doc Category	EWM Doc type	EWM Item type	EWM Item Category
Outbound	SL	NLN	PDO	OUTB	ODLV	DLV
Inbound	EL	ELN	PDI	INB	IDLV	DLV

Step:1

Now create the Material.

Material – 7244

Step:2

The Material is Extended to both Storage locations in MMSC.

Step:3

Now Create the Purchase Order in ME21N:

• Document Type – UB
• Enter Supplying Plant – 5PL1
• Enter PO Creating Storage Location and Material Issuing Storage location.
• As you can see in the Item Details the Shipping Tab is triggered which is mandatory for STO process.

Stock Transp. Order created under the number 4500006531.

Step 4:

Check the stock in Stock overview in MMBE.

• We have 100 Quantity in Plant – 5PL1 and Storage location AFS.

Step 5:

Here I am creating the Outbound Delivery in VL10B Transaction Code.

• Enter the Shipping Point and Purchase order Number and click on Execute Button.

Select the PO Number and click on the Background button.

Another line will be generated with Green Mark. Select that line and click on the Delivery log creation Tab.

Place the Cursor and click on the documents button the Outbound Delivery Number will be displayed.

The Outbound Delivery Number is – 80004086.

Step 6:

Check the delivery with Plant and storage location got triggered and successfully distributed to EWM  in VL02N

Step 7:

Go to /N/SCWM/PRDO

Create the warehouse task and confirm the warehouse task

Confirm the warehouse order

After clicking on the Goods Issue the Status changed to “Completed” and Outbound delivery was generated

Step :8

We have maintained Output type SPED to  trigger inbound delivery after GoodsIssue has been completed for intra-company STO's outbound delivery 

Step 9:

Check the stock has deducted from the AFS storage location in MMBE

Step:10

Check for the PO history using ME23N & can check the Outbound delivery number in the Reference column i.e. 80004086

Step:11

Check the inbound delivery got created with reference to reference to outbound delivery in the PO confirmations tab

Step:12

Check the inbound delivery in VL32N whether it is successfully distributed to EWM or not.

Step:13

Go to /N/SCWM/PRDI and process the delivery

Create the warehouse task and confirm the warehouse task

Confirm the warehouse order

Step:14

Check the stock in MMBE for material 7244 in AFS1 storage location

Conclusion:
This blog post walks you through the creation of the Intra STO with in the plant process and the key parameters that need to be checked and referred to while performing an Intra STO with in the plant between Two EWM managed warehouses and various steps involved in performing the scenario.

Thank you for reading the post, please share thoughts and feedback.

This is my personal observation based on requirements I worked on, and this blog is based on S4 HANA 2020 version sandbox.
Reference-

Some of the blog posts can be referred to in the forum for the STO process to trigger the output type for inbound delivery

https://community.sap.com/t5/enterprise-resource-planning-blogs-by-members/output-type-sped-trigger-...

 

• SAP Managed Tags:
• SAP Extended Warehouse Management,
 
• EWM - Delivery Processing,
 
• EWM - Goods Movement,
 
• MM (Materials Management)

Labels:

• Extended Warehouse Management(EWM)

Source: https://community.sap.com/t5/supply-chain-management-blogs-by-members/intra-company-sto-with-in-the-plant-between-two-ewm-managed-warehouses/ba-p/13589169

How to Get the Latest SAP Fiori Design in Your SAP System

 Since its release, SAP Fiori has been constantly evolving, improving the UX and implementing the latest design standards. The current version is SAP Fiori 3.

 

In this blog post, we’ll walk through a sample SAP Fiori upgrade process.

 

Preupgrade Considerations

The first prerequisite you need to take into account is component versions. The central component is SAP_UI, but it’s dependent on the following components:

• SAPUI5
• SAP Fiori launchpad
• SAP Fiori frontend server

There are some minimal requirements that can be found in the online documentation, but the optimal versions are shown in this figure.

 

 

In the documentation, you also can find information about key capabilities and prerequisites.

 

Note: The current documentation can be found at http://s-prs.co/v544908. From there, navigate to Set Up and Configure SAP Fiori > Setup of SAP Fiori System Landscape.

 

Upgrading an Existing SAP Fiori Landscape

The recommended approach for any SAP software maintenance, including SAP Fiori upgrades, is to use Maintenance Planner and SUM.

 

Maintenance Planner will determine the required packages and their dependencies, and you will execute the upgrade process in SUM. For the upgrade itself, SUM uses the stack XML file generated by Maintenance Planner.

 

Note: More details about SUM can be found at https://support.sap.com/sltoolset.

 

Sometimes, an upgrade of SAP Fiori frontend components requires an upgrade of the backend as well. A combined upgrade of the frontend and backend is also supported and can be executed in one run using Maintenance Planner. But before executing the upgrade, it’s recommended that you familiarize yourself with the release SAP Notes for your specific SAP S/4HANA version.

 

 

For example, if you want to upgrade the frontend in version 1909, SAP Note 2769531 will offer information about dependencies with the backend version, as shown below (see highlighted text).

 

 

To access the Maintenance Planner, go to https://support.sap.com/mopz. This opens the Maintenance Planner home page (see figure below), which contains a lot of useful information, including links to navigate to more detailed documentation.

 

 

From here, navigate to the next page by clicking the Access Maintenance Planner link. The resulting page looks as shown in the next figure. This is the new, recently updated Maintenance Planner dashboard.

 

 

Next, you’ll select the system on which you want to perform the upgrade via the Explore Systems tile. In the example shown below, the system ID is S19.

 

 

The next screen presents lifecycle options for the selected system, as shown here.

 

 

From here, navigate to Plan to reach the screen shown in the next figure.

 

 

In the left part of this screen, you’ll see the current information about your system, and to the right, you’ll see the different maintenance options available for this system. Among other options, in the example above, you can see Plan an SAP S/4HANA Upgrade, as this system is on SAP S/4HANA 1909. But the option you’re looking for to proceed is Install or Maintain an Add-on. If you click this option, you’ll navigate to the screen shown in the next figure.

 

 

Flags to the right show which add-ons are already installed and can be patched. Now select the component you want to upgrade, and then select the Support Package Stack (SPS) from the dropdown to the right (see below).

 

 

Once you confirm the selection, Maintenance Planner will calculate the necessary files. Once the calculation is done, Maintenance Planner will bring you back to the planning screen. Now we have the option to select additional components to be installed or patched, or proceed to the next step by clicking Next.

 

After that, Maintenance Planner will navigate you through a series of screens where you can see selected and add additional files—first OS/DB files, and then ABAP/non-ABAP files.

 

 

Clicking Next takes you to a screen with a list of files to be downloaded, as shown in this figure.

 

 

On this screen, you have the option to download the stack XML file that will be used by SUM and to push files to a download basket. After you push files to a download basket, you can use Download Manager for mass file download.

 

Editor’s note: This post has been adapted from a section of the book SAP Fiori: Implementation and Development by Souvik Roy, Aleksandar Debelic, and Gairik Acharya.

Source: https://blog-sap--press-com.cdn.ampproject.org/c/s/blog.sap-press.com/how-to-get-the-latest-sap-fiori-design-in-your-sap-system?hs_amp=true