The user needs to find out from the purchase order (PO) workflow log who the required approver is and why it is not approved. The material to be transported is required in a critical business operation or process, and the receiving location is pressing hard to get this material. So what should the user do? In most cases the demand from the receiving plant is urgent and important. If the Release indicator box has a status of X Blocked, this means the STO is still not approved and cannot be processed further.
#Sto master key code#
If the user can see the Release strategy tab at the STO header level after executing transaction code ME23N, this means the STO is subject to a release strategy ( Figure 1). With each transaction, time and overhead costs are involved, so many organizations think it is a good idea to use a release strategy to control overhead costs and reduce wasted time. According to this strategy, the organization monitors the system to ensure that no unnecessary documents are created. Perhaps this organization is using a release strategy for STOs. This user has the required access, but still is unable to create a delivery for the STO. The STO Is Subject to a Release StrategyĬonsider a scenario in which an organization has established that a user is the correct person to execute transaction code VL10G (Documents Due for Delivery) or VL10B (Purchase Orders Due for Delivery).
#Sto master key how to#
I explain how to identify which type of issue your system has and also how to eliminate it. It can be caused by security, training, or configuration issues. The problem of being able to create an STO, but not being able to create an outbound delivery can occur in a new implementation, rollout, or even a mature system. Many users in a supply chain organization in a warehouse or as part of the purchasing team perform these transactions daily. Medium-sized to large organizations complete many intercompany and intracompany transactions. I do not cover the details related to authorization and configuration in this blog.)Ī User Can Create an STO, But Cannot Create an Outbound Delivery I also assume that all the required system configurations are in place for the STO scenario to function.
(Note: I assume that the user has the required authorization access to all the necessary transactions for the process. So what went wrong? I describe several business problems faced during STO delivery processing and then explain how to solve them. These problems are common to all types of STO processes, such as intracompany, intercompany, and STO at storage location level. There was no configuration change or process change, but suddenly things became stuck. In this example, the user is able to see the stock in the system, but still the system is not enabling the user to post a goods issue. In another scenario the system allowed the user to create an outbound delivery for an STO, but the system is not allowing the user to post a goods issue for the delivery. The user was able to create a delivery a day before, but today the user is stuck. In most cases, the most common transactions involving delivery of materials are the ones that become stuck. Sometimes users can even see the stock in the system, but still the system is not creating a delivery. Often after users create a stock transport order (STO) in SAP ERP Central Component (SAP ECC), they are not able to create an outbound delivery for the STO.įor example, there might be an urgent delivery to be loaded on a truck, but the truck is standing still because the user cannot create a delivery. By Vineet Pandey, Lead Consultant, SAP Practice, Infosys, Ltd.
0 kommentar(er)
