BD83 Reprocessing of faulty IDocs in outbound queue
CG3Z Upload file
Through a sound expertise in the SAP technology environment, it is recommended to bring the know-how of the SAP basis into the IT strategy and IT roadmap. For this, the responsibility lies primarily with the CIO as the carrier and responsible of the IT strategy and the IT organisation. Likewise, the SAP basis should serve as a sparring partner for individuals and boards (such as enterprise architects) that significantly influence the strategy.
Project successes should also be documented and circulated as success stories of the SAP basis or made available to the SAP basis stakeholders to highlight the importance of the SAP basis. These success stories can be shared from the grassroots or from the outside, for example. Examples include CIO communications or project reports. BENEFITS & CONSEQUENCES The added value of the implementation of the recommendations described above lies in the guaranteed operational stability and operational safety. In addition, a company and in particular an IT organisation with a strong SAP basis receives a competent and sustainable partner for SAP topics and technologies, who is always looking at the SAP picture in general. Furthermore, all business and IT departments are aware of the role and the scope of the SAP basis. This means that you can contact them as the right person in good time. There is a lower risk that certain areas may develop shadow IT related to SAP topics and technologies due to lack of transparency.
Heterogeneous
SAP Basis Training starts at the very beginning of the project. Starting with a meticulous documentation of our work. We involve your internal employees from the very beginning.
Planning ahead: Ideally, your SAP system administrator should make the necessary adjustments to your system landscape before end users are affected. This requires careful planning and anticipation of long-term trends.
With "Shortcut for SAP Systems" a tool is available that greatly facilitates some tasks in the SAP basis.
As an alternative, one can directly use the workload monitor in the transaction code ST03N.
A previous customer of mine had a BW system, to which a total of over 20 other SAPP production systems were connected.