Product Assistance For SAP Yard Logistics For SAP S/4Hana: Operations Information
Product Assistance For SAP Yard Logistics For SAP S/4Hana: Operations Information
SAP Yard Logistics for SAP S/4HANA | SAP Yard Logistics 2009 for SAP S/4HANA
PUBLIC
Warning
This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product documentation. The information included in custom
documentation may not re ect the arrangement of topics in the SAP Help Portal, and may be missing important aspects and/or correlations to other topics. For this reason,
it is not for productive use.
Operations Information
Certain administrative activities are required for the proper functioning of the SAP Yard Logistics solution. This component provides the operations information, which
covers the following topics:
Monitoring Concept
SAP Yard logistics is based on SAP Extended Warehouse Management 9.3 and SAP NetWeaver 7.40.Therefore, the general operations information that is covered in the
related operations guides also applies to SAP Yard logistics.
For more information about related guides, see the following resources on SAP Help Portal:
Resource Location
This is custom documentation. For more information, please visit the SAP Help Portal 1
2/24/2022
Resource Location
Operations Guide for SAP EWM 9.3 Visit the product information page for SAP EWM on the SAP Help Portal at
https://help.sap.com/ewmand select the appropriate product version from the version
dropdown.
On top of the database layer, SAP Yard Logistics uses SAP EWM9.3 (with SP03 as minimum requirement) as technical basis (without the need to implement warehousing
speci c processes) as well as software components from SCM Basis (in more detail: SAP Alert Management, SAP condition technique, PPF printing). To reuse existing EWM
functionalities, SAP Yard Logistics uses a simpli ed setup of a (technical) warehouse number and its related layout (later to be used as a yard layout) and master data
(especially, master data for EWM shipping and receiving). This need not to be confused with the linked warehousing processes that runs on independent EWM business
systems used for the EWM-related processes. These are "real" EWM warehousing systems that will be triggered from the yard processes at dock to EWM warehousing door
or departure from door. For details, see the multiple warehouse scenario in SAP Yard Logistics described in a later chapter.
A special case is the SAP Dock Appointment Scheduling (SAP DAS for short). This application can be used independently (of EWM) but is a software component as part of
SAP EWM. In the SAP Yard Logistics processes, an integration to SAP DAS is offered as well (see details in a later chapter). However, to allow the business user a seamless
user interface between SAP Yard Logistics and SAP DAS, we only offer the SAP DAS application to run on the SAP Yard Logistics system.
The business documents for SAP Yard Logistics are modelled in the BOPF Business Object layer. A business object is a semantic entity that represents the smallest data unit
in a business scenario within SAP Yard Logistics. You use a BOPF business object to de ne data structures and business logic. To de ne the data structure part of such a
business object, you create nodes, elements, and associations between nodes. To de ne the business logic, you create entities such as actions, determinations, or
validations. The business documents created for SAP Yard Logistics are listed in the table below.
For the modeling of yard processes, SAP Extended Warehouse Management (SAP EWM release 9.3 SP03) has largely been re-used as a technical foundation (as already
mentioned above). This comprises of the following:
Interfaces to other SAP components like SAP TM and SAP EWM warehouse billing
Business documents like EWM TUs and its functionality, as part of shipping and receiving
Yard Request /SAPYL/YARD_ORDER A yard request is a planning document for the yard
coordinator to control the workload for a speci c yard that is
represented as a yard number. It can be entered manually
into the SAP Yard Logistics application or can be sent via a
web service (LDAP request) from an external system.
Yard Order /SAPYL/YARD_ORDER A yard order represents the workload to be executed within a
certain period based on the planning from the yard requests.
The document structure of a yard order is the same as that
of a yard request with the following exceptions – it uses a
different key eld, DOC_CAT and supports status
management.
Yard Task /SAPYL/YARD_TASK A yard task describes the activity that should be performed
on the item(s) belonging to a yard order (container, trailer)
within the yard. The activity can constitute either a
movement from a source storage bin to a destination storage
bin, or a non-movement activity, for example, cleaning of
containers.
Yard Transportation Unit /SAPYL/YARD_TU A yard transportation unit is a business object for wrapping
SAP EWM Transportation Units and enhancing them by SAP
Yard Logistics-speci c functionality like TU grouping, storing
of seals and measurements.
Based on the modelled business objects, the user interface layer is also NetWeaver-based. For the expert business user, all user interfaces are de ned using Floorplan
Manager (FPM), based on Web-Dynpro for ABAP for the single document applications and Personal Object Worklist (POWL for short) for lists of document applications. To
allow a graphical representation of the operations within a speci c yard, a yard cockpit has been de ned (also based on ABAP FPM as ActiveX control. This needs a local
This is custom documentation. For more information, please visit the SAP Help Portal 2
2/24/2022
installation of SAP Visual Business 2.1 on the business user's PC), and SAP Visual Business shows the schematic model of the yard and its parts based on 3D geographical
data.
For one speci c role, that is, yard operations, a mobile user interface is provided. This mobile app is developed using SAP UI5. The UIs of the mobile app are called using the
SAP Fiori Launchpad from the web browser of your choice. It allows for a unique mobile experience via browser, as well as through hardware independent apps, which can be
consumed through the SAP Fiori client.
Note
You can nd more information about the underlying NetWeaver platform technology in the SAP NetWeaver Administrator's Guide – Technical Operations Manual in the
SAP Library on SAP Help Portal at http://help.sap.com/nw_platform .
The SAP Yard Logistics application is built on top of SAP EWM, which is based on SAP NetWeaver technology. Therefore, the monitoring tools from SAP NetWeaver, such
as the Computing Center Management System (CCMS), are reused.
We recommend that you set up the Monitoring Infrastructure as described in the section on Monitoring Concept.
You nd this documentation on the SAP Library for SAP NetWeaver 7.4. Go to SAP Help portal at http://help.sap.com and choose Technology Platform SAP
NetWeaver SAP NetWeaver 7.4 Application Help . Go to Function-Oriented View Solution Lifecycle Management Solution Monitoring .
Note
Important information about installing or upgrading to SAP EWM 9.3 is provided in SAP Note 2126732 . This note is updated on a regular basis. Therefore, make sure
you have the current version of this note before you start the installation.
There are two different client implementations of SAP Visual Business that you can choose between for displaying your yard cockpit in SAP Yard Logistics for SAP S/4HANA;
SAP Visual Business 2.1 (ActiveX Plug-In) and SAP Visual Business (SAPUI5).
The SAP Visual Business front-end component used on the SAP Yard Logistics' FPM user interface is a client component. The client-side installation is integrated into the
SAP front-end installer, also known as SAPSetup, which is available for download from the SAP Support Portal .
For use on NetWeaver platform release 7.4, SAP Visual Business release 2.1 is recommended.
The corresponding local user interface linked to this release is NetWeaver Business Client 5.0 PL12 (or higher) or NetWeaver Business Client 6.0 PL05.
The SAP UI5 control for SAP Visual Business does not require any separate installation, but needs the appropriate UI5 stack in the system to run properly.
SAP Visual Business documentation on the SAP Help Portal at: https://help.sap.com/viewer/50d59fa70a4544239619259ca8efc2ec/7.51.10/en-
US/6e6cfdb0d20946d591eb620c906a4784.html
This is custom documentation. For more information, please visit the SAP Help Portal 3
2/24/2022
For detailed information about the con guration tasks for the SAP Fiori launchpad, see the following documentation – For SAP NetWeaver 7.4, go to SAP Help Portal at
http://help.sap.com/nw74 and choose Application Help. Go to UI Technologies in SAP NetWeaver SAP Fiori Launchpad Setting Up the Launchpad . The SAP Fiori Search
is not supported in SAP Yard Logistics 2.0.
Note
You nd this documentation on the SAP Library for SAP NetWeaver 7.4. Go to SAP Help portal at http://help.sap.com and choose Technology Platform SAP
NetWeaver SAP NetWeaver 7.4 Application Help . Go to Function-Oriented View Application Server Application Server ABAP Other Services . Select Services for
Business Users SAPconnect .
SAP Note 455140 for Con guration of e-mail, fax, paging/SMS via SMTP
Create and deploy interactive forms that look exactly like their paper counterparts
Generate dynamic PDF documents from data contained in the SAP system
Note
For the con guration of the ADS Services, please consult SAP Note 894009 - Adobe® Document Services: Con guration.
In addition to that, SAP Yard Logistics allows assigning a yard speci c "door" storage type to a docking location and loading point. Once a yard task is targeting to such a
storage type or targeting from such a storage type, the arrival and departure at dock events in the DAS appointment are updated based on the appointment that is
assigned to this yard task.
Note
Go to https://help.sap.com/EWM93. Select the Application Help. Choose SAP Extended Warehouse Management SAP Dock Appointment Scheduling .
This is custom documentation. For more information, please visit the SAP Help Portal 4
2/24/2022
Putting legal holds on data that is relevant for legal cases so it cannot be deleted or destroyed. Legal holds affect the data in the database as well as the data in the
ILM store.
Grouping data objects that are to be stored or queried together in audit areas.
ILM rules for time-based management of data objects, for the following purposes:
Adherence to legal requirements for retention periods for tax auditing and product liability purposes.
Deleting data for which the retention period has expired and for which there is no legal hold.
To activate SAP ILM, you need to set the central switch ILM in Customizing for business functions.
Note
See Using ILM Retention Management in the Application System at
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/09/ec83476f0942bcaea4481bc02ddf23/content.htm?
frameset=/en/09/ec83476f0942bcaea4481bc02ddf23/frameset.htm¤t_toc=/en/35/aaef16745644c397ec0024b31fb191/plain.htm&node_id=36&show_children=tru
You run this report once at the time of upgrading to the current version of the solution.
The report can be run in both Test and Execution mode. To run the report, use transaction /SAPYL/LOAD_SCH_MIGR.
Technically, the database table /SAPYL/TU_BIC is no longer used but is replaced by database table /SAPYL/CNT_BIC containing the owner code and the equipment
category. As this Customizing table is delivered without any entries, the change should not have an impact but you have to maintain the entries in the changed table
manually.
Use
The following sections contain information that is related to the operation of the web-based applications provided in SAP Yard Logistics:
These applications are based on the Web Dynpro for ABAP technology. Therefore, we strongly recommend that you read the operations information available for this UI
technology rst. This information is provided with the documentation for your SAP NetWeaver release. You can access this information on SAP Help Portal at
http://help.sap.com/nw .
You must also activate the corresponding SICF nodes to the applications (mentioned in brackets).
This is custom documentation. For more information, please visit the SAP Help Portal 5
2/24/2022
For more information, see Activating ICF Services. Go to http://help.sap.com/nw74 and choose Application Help UI Technologies in SAP NetWeaver . Go to Web Dynpro
ABAP and Floorplan Manager Web Dynpro ABAP Web Dynpro ABAP Administration Initial System-Wide Con guration Settings for Web Dynpro ABAP .
Features
Yard Visualization Using SAP Visual Business
To see the yard visualization, the SAP Visual Business front-end component needs to be installed (see section 5.2). Based on this technical setup, the yard objects to be
visualized need to be completed using the yard object editor.
To enable the usage of the SAP Fiori Launchpad, rst it must be set up in a proper way as described in section on Installation and Setup. Once you have done this, you must
provide role-speci c authorizations to your business users to access the Fiori Launchpad applications. To this end, you have to assign the following pre-de ned roles to the
users:
/SAPYL/YTASK_APP SAP Yard Logistics – Backend Role for Fiori App – Yard Task Only relevant for the SAPUI5 user interface
Con rmation
/SAPYL/SELFCHECKIN_APP SAP Yard Logistics - Back end role for Fiori App – Self Only relevant for the SAPUI5 user interface
Check-In
/SAPYLUI/BCR_YARDOPERATOR_T SAP Yard Logistics – Business Role for Yard Operator Only relevant for the SAPUI5 user interface
/SAPYLUI/BCR_GATEAGENT_T Business Role for Yard Gate Agent Only relevant for the SAPUI5 user interface
/SAPYLUI/TCR_T SAP YL – Technical Role for Fiori Launchpad Only relevant for the SAPUI5 user interface
After that, populate the launchpad with the right apps. For this, you can use transaction /UI2/FLP_CONF – Fiori Launchpad Designer.
SAP Yard Logistics provides the following catalogs available in the launchpad:
Catalog ID Description
To be able to start the mobile apps, semantic objects YardTask and YardOrderSelfCheckIn have been de ned.
You must also activate the SICF nodes /default_host/sap/bc/ui5_ui5/sapylui/ytask (for this mobile app) and the SICF node
/default_host/sap/opu/odata/sapyl/das_yard_operator_srv (for the ODATA service in the SAP Yard Logistics backend).
For the self check-in app, you must activate the SICF node /default_host/sap/opu/odata/sapyl/ self_check_in_srv.
Monitoring Concept
Use
Monitoring is an essential task in the management of SAP technology and applications. You can nd more information about monitoring in the SAP Help Portal under
http://help.sap.com/nw74 . Go to System Administration and Maintenance Information Technical Operations for SAP NetWeaver .
Features
Integration Engine Monitoring and Restart
The interface connectivity between SAP Yard Logistics (SAP YL) and SAP Transportation Management (SAP TM) is based on integration scenarios using SAP PI. Therefore,
the monitoring of the interface between SAP TM and SAP YL can be done using transaction SXMB_MONI. It is important to mention here that this monitoring transaction is
available in the sending system (for example, the SAP TM), the receiving system (for example, the SAP YL), and in the PI system connecting both the systems. Interface
messages between these systems can be transferred correctly only if the messages are processed successfully in all three systems. From this transaction, you can also
trigger a message re-start if the original call has ended in a failure. A Restart button to re-process the web service call is available for use in such a scenario.
Queue Monitoring
The integration engine of SAP PI as well as SAP EWM use A2A interfaces based on RFC function calls that are processed via queued RFCs. The naming of the queues have
been taken over from the naming conventions of these applications. You can perform the basic monitoring using transaction SMQ1 for outbound queues, that is, qRFC calls at
sender side, or transaction SMQ2 for inbound queues, that is, qRFC calls at receiver side.
This is custom documentation. For more information, please visit the SAP Help Portal 6
2/24/2022
The Post-Processing Framework (PPF) is used in SAP Yard Logistics to perform follow-up process actions based on existing business objects, that is, yard orders, yard tasks
and yard TUs. PPF monitoring can be performed in two different ways. The rst way is directly in the FPM user interface of the single document maintenance for one of the
business objects mentioned before. In these user interfaces, you will nd an own UIBB area called Output Management that shows all PPF actions related to the current
business object document. For example, you enter a speci c yard order in the yard order FPM UI and you want to verify that it has been sent to SAP TM. You navigate to the
UIBB area Output Management, and see if an entry for the PPF action Send LDAP Noti cation to SAP TM exists and has a green light, that is, has been processed
successfully.
In the second, a more conventional method, you can use transaction SPPFP. Here, you have to enter the date and time frame of the PPF action that you want to see.
The action pro le – /SAPYL/YO for yard orders, /SAPYL/TU for yard TUs, /SAPYL/YT for yard tasks
The action de nition – one of the entries mentioned in the table below
Then, you can see a PPF action processed as resulting list entries. If you have enabled the function, from this list also you can re-trigger a PPF action.
The Yard Cockpit is a monitoring tool that enables you to see all activities within a yard based on the operational documents as well as the current situation using a graphical
way.
To support these needs, the Yard Cockpit is split into several areas. The right side of the screen contains the Visual Yard, which is the display of the current situation within
the yard in a graphical way. On the left side of the screen, you can see the lists for yard orders, yard tasks, resources, and so on.
Technically, in these areas UIBBs are shown in the FPM application, which allows for the efficient ltering and display of the operational business documents, for example,
yard tasks, yard orders, TUs, and so on.
In the Yard Cockpit, the different UIBBs mentioned in the table below are treated independently. This means, for example, one Yard Order in the Yard Order UIBB has no
impact on the display of the Visual Yard.
UIBB Description
Yard Tasks With this UIBB, you can lter and display yard tasks based on different criteria such as
creating new ones and editing existing ones.
Yard Orders With this UIBB, you can lter and display yard orders based on different criteria.
Transportation Units With this UIBB, you can lter and display TUs based on different criteria.
Alerts With this UIBB, you can lter and display alerts based on different criteria.
Resources With this UIBB, you can lter and display resources based on different criteria.
Note that you can click the person symbol on the upper right corner to determine the layout of the yard cockpit.
In SAP Yard Logistics, it is used to send an SMS for driver advice after the check-in of a Yard Order document. This makes use of SAPconnect, a functionality to set up
different communication possibilities sent from the SAP system. To monitor the SMS sent, you can use transaction SOST.
Remember
You nd this documentation on the SAP Library for SAP NetWeaver 7.4. Go to SAP Help portal at http://help.sap.com and choose Technology Platform SAP
NetWeaver SAP NetWeaver 7.4 Application Help . Go to Function-Oriented View Application Server Application Server ABAP Other Services . Then select Services for
Business Users SAPconnect .
Trace les and log les are essential for analyzing problems.
This is custom documentation. For more information, please visit the SAP Help Portal 7
2/24/2022
For general information about traces, see SAP Library for SAP NetWeaver on SAP Help Portal at http://help.sap.com/nw703 and choose Application
Help Function-Oriented View . Go to SAP NetWeaver by Key Capability Application Platform by Key Capability Application Server ABAP Administration of
Application Server ABAP Monitoring and Administration Tools for Application Server ABAP Trace Functions .
You can also see SAP Help Portal at http://help.sap.com/nw74 and choose Application Help Function-Oriented View . Go to SAP NetWeaver Library: Function-
Oriented View Application Server ABAP Administration of Application Server ABAP Monitoring and Administration Tools for Application Server ABAP Trace
Functions .
Application Log
The application log is a re-use tool that collects messages, exceptions, and errors. This information is organized and displayed in a log. As the technical basis is SAP EWM, all
SAP Yard Logistics related logs are stored using object /SCWM/WME. This enables the switching of log messages per SAP user and warehouse.
For general information about application logs, see SAP Library for SAP NetWeaver on SAP Help Portal at http://help.sap.com/nw74 and choose Application
Help Function-Oriented View . Go to SAP NetWeaver Library: Function-Oriented View Solution Life Cycle Management Application Log .
Alert Monitoring
Proactive automatic monitoring is the basis for ensuring reliable operations for your SAP system environment. SAP Yard Logistics is technically based on SAP NetWeaver
Application Server, and reuses the Alert Monitor framework used in SAP SCM Basis. You can set up the basic customizing using transaction /SCMB/ALENCFG – Alert Engine
Con guration.
The possible alert categorization is de ned via alert structures. These structures represent special topics for alerting. The following table shows the prede ned alert
structures:
Based on the alert categorization, you can de ne the speci c alert messages called alert types. The following table shows the pre-de ned alert types:
This is custom documentation. For more information, please visit the SAP Help Portal 8
2/24/2022
To monitor the speci c alerts created by the SAP Yard Logistics solution, you can use transaction /SAPAPO/AMON1. Select one of the overall alert pro les showing all alerts
for SAP Yard Logistics to see all posted alerts.
SAP Yard Logistics uses the standard tools available in SAP NetWeaver and does not require a component-speci c tool. For the business documents of yard orders (and yard
requests), yard tasks and yard TUs, the archiving adapter of the Business Objects Processing Framework is used. For more information, see the SAP NetWeaver Operations
Guide on SAP Help Portal https://help.sap.com/nw. You can archive the following data in SAP Yard Logistics:
In addition to the archiving objects, SAP Yard Logistics also provides speci c ILM-enabled entities that are linked to the archiving objects mentioned above. The following
table gives an overview on these ILM objects for SAP Yard Logistics. For more details on how they can be used, see the online help item Making SAP NetWeaver ILM
Available at http://help.sap.com/saphelp_scm700_ehp01/helpdata/en/b0/3f9fd868c14b5696554766234884f8/content.htm?
frameset=/en/09/ec83476f0942bcaea4481bc02ddf23/frameset.htm¤t_toc=/en/35/aaef16745644c397ec0024b31fb191/plain.htm&node_id=3&show_children=false.
Periodic Tasks
This is custom documentation. For more information, please visit the SAP Help Portal 9
2/24/2022
Software Change Management
Troubleshooting
The backup and restore strategy for your system landscape must not only consider SAP systems but must also be embedded in the overall business requirements and
incorporate your company’s entire process ow. In addition, the backup and restore strategy must cover disaster recovery processes, such as, the loss of a data center
through re. In this context, it is essential that you ensure that backup devices are not lost together with normal data storage, by using separate storage locations.
SAP Yard Logistics is – as SAP EWM 9.3 – based on SAP NetWeaver technology. All related SAP NetWeaver backup procedures also work for SAP Yard Logistics. Therefore,
there is no special procedure for this component. For more information on backup and recovery, see http://help.sap.com/nw74 . Go to System Administration and
Maintenance Information Operations Information .
Periodic Tasks
In addition to the standard jobs mentioned in Technical Operations for SAP NetWeaver (see http://help.sap.com/nw74 . Go to System Administration and Maintenance
Information Technical Operations for SAP NetWeaver ). You must schedule SAP EWM-speci c jobs in your SAP system. You must run all jobs, unless otherwise speci ed, at
times of minimal system activity, so as not to affect performance or otherwise disrupt your daily operations. You can restart all jobs.
To release multiple yard requests based on their planned arrival or departure dates, automated via a background process, the business can use transaction
/SAPYL/MASS_YR_ACTIV to release multiple Yard Requests on a planned arrival or departure date.
The goal of Software Change Management is to establish consistent, solution-wide change management that allows for speci c maintenance procedures, global rollouts
(including localizations), and open integration with third-party products.
This section provides additional information about the most important software components.
Transport and Change Management: Enables and secures the distribution of software changes from the development environment to the quality. For transport and
change management issues, the procedures of SAP NetWeaver apply for SAP Yard Logistics. For more information, see SAP Library for SAP NetWeaver on SAP Help
Portal at http://help.sap.com/nw74 and choose System Administration and Maintenance Information Technical Operations for SAP NetWeaver . Go to
Administration of Application Server ABAP Change and Transport System .
The SAP Yard Logistics component is a server component that uses the standard ABAP Transport Management System (TMS) for software logistics. The SAP Yard
Logistics application component belongs to the technical software layer SAPYL (for the SAP YL applications besides the SAPUI5 application) and to SAPYLUI (for the
SAP YL’s UI5 application). Updates to these components are supplied through SAP Notes or the SAP Note Assistant and support packages.
Support Packages and SAP Notes Implementation: Provides standardized software distribution and maintenance procedures. Patches for the components are
available either as regular support packages or as SAP Notes. To download the SAP Notes, use SAP Solution Manager or the SAP Note Assistant.
For support desk management, you need the methodology, management procedures, and tools infrastructure to run your internal support organization efficiently. SAP
Support needs to be able to work remotely for highest efficiency and availability. Therefore, all required support tools must be remotely accessible for SAP support. For SAP
YL, the standard SAP procedures for setting up remote support apply.
For information about reporting incidents and forwarding them to SAP, see http://support.sap.com .
For sending incidents/problem messages/tickets to SAP, choose the appropriate component (or sub component) name from the SAP component hierarchy:
SCM-YL SAP Yard Logistics For all messages to SAP YL processes and applications
(except the mobile app for yard operations)
SCM-YL-FIO SAP Yard Logistics Fiori For all messages related to the mobile app for yard
operations
Troubleshooting
For information about troubleshooting SAP NetWeaver, see SAP Library for SAP NetWeaver on SAP Help Portal at http://help.sap.com/nw74 and choose System
Administration and Maintenance Information Technical Operations for SAP NetWeaver . The following tools are available for troubleshooting SAP Yard Logistics:
Application Logs – For more information, see section on Logging and Tracing.
SAP EWM Troubleshooting – Consult the chapter on Troubleshooting valid for SAP EWM 9.3. See SAP Help Portal at http://help.sap.com/ewm93 and choose
System Administration and Maintenance Information Application Operations Guide . Go to the chapter on Troubleshooting.
Issue Resolution
The visualization of the yard cockpit looks strange and you have de ned the items in a Clear the cache of the Visual Business GUIBB.
correct way.
The SAP Visual Business control in the browser caches map tiles on the front-end machine.
It may be necessary to clear the cache if you encounter mis- tting map tiles.
The cache content is controlled through the Visual Business Property window that you can
open with Ctrl + Alt + Right click . The window offers a Cache tab, which shows you the
actual cache location and its content. Furthermore, it allows you to clear the cache
completely.
The visualization of the yard cockpit is not starting or shows a white space or an error This is an issue in the browser security, for example, Internet Explorer 11, and for the
message "No map can be displayed for VisBis UIBB" browser, you have to allow "insecure" ActiveX controls.
There is an issue in a Web Dynpro ABAP that is only reproducible by a speci c user. See SAP Note 2198046 - How to resolve user-speci c issues in Web Dynpro ABAP and
use WD application WD_ANALYZE_CONFIG_USER
This issue may be represented by a blank screen, a dump or a time-out error.
Changes to BO eld control for yard orders, yard requests or yard tasks are not up-to-date Open transaction SHMM, then nd the shared area /BOFU/CL_BO_FIELDCONTROL_SHM
after transport. and select Delete All Instances button on the table toolbar. Then refresh Web Dynpro
application and all the elds are disabled according to the updated eld control database
table.
Caution
If several business users are using Web Dynpro applications in parallel, then they may
receive a dump because the shared memory instances are deleted
You have changed Customizing settings for the self check-in app but you still see the old The target system's client cache needs a refresh for your user. Therefore, start transaction
version in the target system SA38 and run the report /UI2/INVALIDATE_CLIENT_CACHE
You are using the NWBC locally and have empty F4 value help lists The reason is a browser bug released in a security patch in May by Microsoft, which causes
that issue. See SAP Note 2375211 .
The queues are hanging and you want to automate their restart You can schedule the following reports on a regular time base:
For more information, please consult the SAP Note 813029 - Automatic processing of
failed XI messages
This is custom documentation. For more information, please visit the SAP Help Portal 12