Abbreviation: WWI stands for Windows Word processor Integration
It is a tool used in context of SAP EHS Management to generate documents. The documents are in most cases then stored in SAP (e.g. DMS). It is an add on to Microsoft Office solution „Word“. The tool is used as well in the context of distribution of documents (like Safety Data Sheets) or the generation of labels.
Latest Post
SAP WWI TCodes
T-Code CG42 --> Create a WWI template in EHS module
T-Code CG54--> Report Information System
T-Code CG50 --> Report Management
T-Code CG02 or CG02BD ---> Create the reports or to get a „draft“ view of content of the documents
Abbreviation: WWI stands for Windows Word processor Integration
Related Posts:
What is WWI?
Tags: WWI Installation docs, pdf, guides, download,
T-Code CG54--> Report Information System
T-Code CG50 --> Report Management
T-Code CG02 or CG02BD ---> Create the reports or to get a „draft“ view of content of the documents
Abbreviation: WWI stands for Windows Word processor Integration
Related Posts:
What is WWI?
Tags: WWI Installation docs, pdf, guides, download,
SAP Netweaver 7.5 Cluster HA Info
- Each of the cluster nodes in the cluster must have its own local disks and have access to shared disks that can be reached by the cluster nodes via a shared bus.
- The cluster nodes of the cluster must be connected by a private and public network:
- ○ The public network enables communication from the cluster nodes of the cluster to other resources in the local area network (LAN).
- ○ The private network enables internal communication between the cluster nodes. In particular, it enables the Cluster Service running on all cluster nodes to regularly exchange messages on the state of the cluster nodes so that the failure of resources is quickly detected
Netweaver 7.5 Stack.xml Parameter
Software Provisioning Manager (the “installer) can be called with parameter SAPINST_STACK_XML= <path to xml file>
SAP JCE Policy Files Download Location
http://service.sap.com/swdc -->Download SAP Cryptographic Software -->download the package SAP Java Cryptography Extension Jurisdiction Policy)
The file names are
local_policy.jar
US_export_policy.jar
The file names are
local_policy.jar
US_export_policy.jar
Cannot drop the view 'CDS_M_M2S_PD_ITM', because it does not exist or you [SAP BASIS ERRORS]
Error:
SQL-error-Text: "Cannot drop the view 'CDS_M_M2S_PD_ITM', because it does not exist or you
Warning:
SQL-error "3701" in DDL statement for "CDS_M_M2S_PD_ITM
This error comes during support pack upgrade using SPAM
Fix:
Run report RUTDDLSACT with view as “DDL_CDS_STOCK_SUM”
SQL-error-Text: "Cannot drop the view 'CDS_M_M2S_PD_ITM', because it does not exist or you
Warning:
SQL-error "3701" in DDL statement for "CDS_M_M2S_PD_ITM
This error comes during support pack upgrade using SPAM
Fix:
Run report RUTDDLSACT with view as “DDL_CDS_STOCK_SUM”
SAP NW 7.5 New Features from Basis Perspective
Basis Changes
In NW 7.5 you will no more see the folder name DVEBMGS<nn> it's replaced by just D<nn> like our Dailog app server.
NW 7.5
SAP NetWeaver 7.5 enables technology trends like the Internet of Things (IoT), mobile, cloud, big data and analytics and offers a foundation for the easy and fast development of simple business applications. It supports Java 8 to enable Java-based hubs like SAP Enterprise Portal, SAP Process Orchestration, and SAP Business Process Management to benefit from new Java features. The innovations in ABAP and Java, together with improvements to SAP NetWeaver hubs, SAP Fiori, and lifecycle management offer significant benefits.
In NW 7.5 you will no more see the folder name DVEBMGS<nn> it's replaced by just D<nn> like our Dailog app server.
NW 7.5
SAP NetWeaver 7.5 enables technology trends like the Internet of Things (IoT), mobile, cloud, big data and analytics and offers a foundation for the easy and fast development of simple business applications. It supports Java 8 to enable Java-based hubs like SAP Enterprise Portal, SAP Process Orchestration, and SAP Business Process Management to benefit from new Java features. The innovations in ABAP and Java, together with improvements to SAP NetWeaver hubs, SAP Fiori, and lifecycle management offer significant benefits.
Activation of CDS views aborts on MSS - Objects missing in the database - IMPORT PROPER PHASE
WHEN YOU GET THIS ERROR
During SPAM IMPORT_PROPER phase, you would run into this issue.
CHECKS
check in DB02->Diagnostics->Missing Tables and Indexes, you find many DDL SQL views are listed as "Objects missing in the database"
SOLUTUON
Run report with view as “DDL_CDS_STOCK_SUM”
Read this Note for more details
As per the note 2125387 - Activation of CDS view aborts on MSS
During SPAM IMPORT_PROPER phase, you would run into this issue.
CHECKS
check in DB02->Diagnostics->Missing Tables and Indexes, you find many DDL SQL views are listed as "Objects missing in the database"
SOLUTUON
Run report with view as “DDL_CDS_STOCK_SUM”
Read this Note for more details
As per the note 2125387 - Activation of CDS view aborts on MSS
SAP SUM
SUM ERROR PREPROCESSING PHASE - RDDIMPDP Could not be started or terminated abnormally
ERROR: RDDIMPDP Could not be started or terminated abnormally
Logs to Check
/SUM/abap/log/SLOGS , SAPup.Eco
If Windows Check SAP MMC ABAP Logs to see error
Fix:
Login to Shadow Instance 000 client
T-Code SM61
Create Batch Server for shadow instance app server.
tags: SAP_DEFAULT_BTC, Batch server, SE38, RDDIMPDP, SUM, SApup.eco, MMC
SAP SUM
SUM tool Start Commands in Windows
SIDADM> D:\USR\SAP\SID\SUM>STARTUP.BAT
Starts SL Controller
D:\URS\SAP\SID\SUM\SDT\EXE>DSUGui.BAT
Starts SUM GUI
Starts SL Controller
D:\URS\SAP\SID\SUM\SDT\EXE>DSUGui.BAT
Starts SUM GUI
How to check when SAP was last Started? Answer: ST02 TCode
Go to T-Code : ST02
You can see the last started time of SAP system in box highlighted below screen.
You can see the last started time of SAP system in box highlighted below screen.
SAP Transports - Script to add bulk tp to buffer
As a part of SAP Basis life, we need to import many transports at a time, which is very crucial for the project at the same time its very boring job indeed.
Some of us take help of excel and notepad and create file to import those transports at OS level like separate line for each transport
tp import SA8K901203 <SID> client=100 u0126 pf=/usr/sap/trans/bin/TP_DOMAIN_<SID>.PFL
tp import SA8K901205 <SID> client=100 u0126 pf=/usr/sap/trans/bin/TP_DOMAIN_<SID>.PFL
tp import SA8K901207 <SID> client=100 u0126 pf=/usr/sap/trans/bin/TP_DOMAIN_<SID>.PFL
This solves the purpose, but there is no fun in it. Plus lets say if you want that in case of return code 8 or other error the import should stop then above method will not going to help at all. Solution is to create a script for it in Unix. I have done thousands of transport with help of this script on Solaris and Linux, and I don't see any reason why it should not run on other flavors like AIX, HP-UX.
Lets proceed to create script file.
Create a directory where you like, I created inside trans directory with name TrnScript. Provide read write access to <sid>adm for this directory.
Inside this directory you need to create three files.
1. /usr/sap/trans/TrnScript/transport_list.txt file, this file will contain transports list, each transport in new line, which will look like below:
$ more transport_list.txt
EC6K900076
EH4K930113
EH4K900148
SA8K901203
SA8K901225
SAPKD70243
This is a simple text file and there is no limitation on number of transports you can have a list of thousand transports and they will be processed one by one in linear sequence, the transport in top will be processed first and it will move to second line and so on in downward direction. This file will needs read access rights for <sid>adm.
Now we need a executable file to add transports in buffer, it does not matter if the transports are already there in buffer or not, below script is not going to do any harm in system, run it anyway before starting the import script file.
2. /usr/sap/trans/TrnScript/trns_add2buff.sh
$ more trns_add2buff.sh
# Start of Script file
#! This script will add transports to buffer one by one sequentially.
# The list of transport should be given in transport_list.txt file where
# each transport should be in new line.
###
TPLIST=/usr/sap/trans/TrnScript/transport_list.txt
TPSTATUS=${TPLIST}.log
for i in `cat ${TPLIST}`
do
/usr/sap/DT9/SYS/exe/uc/linuxx86_64/tp addtobuffer $i DT9 u1 pf=/usr/sap/trans/bin/TP_DOMAIN_DT9.PFL
RC=$?
print "`date`...Transport ${i} Status RC=${RC}" >> ${TPSTATUS}
done
# End of script file
This file should have executable rights for <sid>adm. Check this file carefully for the path mentioned for
(a) TPLIST
(b) tp
(c) DOMAIN file
When above script file will execute, it will create a log file named transport_list.txt.log at same location where transport_list.txt file is present, provided <sid>adm has write access to the directory. The log file will contain information like below
$ more transport_list.txt.log
Mon Apr 30 06:49:56 CDT 2012...Transport EC6K900076 Status RC=0
Mon Apr 30 06:49:56 CDT 2012...Transport EH4K930113 Status RC=0
Mon Apr 30 06:49:56 CDT 2012...Transport SA8K901225 Status RC=0
This log file will give you chance to check if data file and cofiles are present and readable. Also, if any of the transport is imported in system without option "Leave transport Request in Queue for Later Import" then it will add it again so the request can become transportable again. If you find any other return code than zero then correct the issue rename the log file and rerun this script file again and check log file.
If everything goes fine till here then we can go for transport import script file
3. /usr/sap/trans/TrnScript/trns_import.sh
$ more trns_import.sh
# Start of Script file
#! This script will import transports one by one sequentially.
# The list of transport should be given in transport_list.txt file where
# each transport should be in new line.
###
TPLIST=/usr/sap/trans/TrnScript/transport_list.txt
TPSTATUS=${TPLIST}.RClog
for i in `cat ${TPLIST}`
do
/usr/sap/DT9/SYS/exe/uc/linuxx86_64/tp import $i DT9 client=100 u0126 pf=/usr/sap/trans/bin/TP_DOMAIN_DT9.PFL
RC=$?
print "`date`...Transport ${i} Status RC=${RC}" >> ${TPSTATUS}
if [ "$RC" -ne 0 ] && [ "$RC" -ne 4 ]; then
break
fi
done
# End of script file
This script file will import transports with u0126 mode which means
0 - Leave Transport Request in Queue for Later Import
1 - Import Transport Request again
2 - Overwrite Originals
6 - Overwrite Objects in Unconfirmed Repairs
Import Option.jpg
If you want to select different option then you can adjust accordingly the number appended after "u" in script.
This file will create log file transport_list.txt.RClog which will contain the timestamp and RC of each transport.
The import of transport will stop when it will get return code other than 0 or 4
Now you can read SAP tp log and resolve the issue then you need to remove those transports which are already imported through script from file transport_list.txt and execute the script again.
If you want that in case of error too, the script should move ahead with next transport then you simply need to put # in start of these 3 lines or remove them from the script file
if [ "$RC" -ne 0 ] && [ "$RC" -ne 4 ]; then
break
fi
You can also use at now or cron to schedule the script as per your need.
Hope this will be of help to some of us.
Posted by Ishteyaque Ahmad in SAP on UNIX
Tags:
script for multiple tp addtobuffer and tp import Mass adding of transports SAP Add to Buffer & Import Multiple Transports using TP Scripts how import mass transport requeast at os level
Some of us take help of excel and notepad and create file to import those transports at OS level like separate line for each transport
tp import SA8K901203 <SID> client=100 u0126 pf=/usr/sap/trans/bin/TP_DOMAIN_<SID>.PFL
tp import SA8K901205 <SID> client=100 u0126 pf=/usr/sap/trans/bin/TP_DOMAIN_<SID>.PFL
tp import SA8K901207 <SID> client=100 u0126 pf=/usr/sap/trans/bin/TP_DOMAIN_<SID>.PFL
This solves the purpose, but there is no fun in it. Plus lets say if you want that in case of return code 8 or other error the import should stop then above method will not going to help at all. Solution is to create a script for it in Unix. I have done thousands of transport with help of this script on Solaris and Linux, and I don't see any reason why it should not run on other flavors like AIX, HP-UX.
Lets proceed to create script file.
Create a directory where you like, I created inside trans directory with name TrnScript. Provide read write access to <sid>adm for this directory.
Inside this directory you need to create three files.
1. /usr/sap/trans/TrnScript/transport_list.txt file, this file will contain transports list, each transport in new line, which will look like below:
$ more transport_list.txt
EC6K900076
EH4K930113
EH4K900148
SA8K901203
SA8K901225
SAPKD70243
This is a simple text file and there is no limitation on number of transports you can have a list of thousand transports and they will be processed one by one in linear sequence, the transport in top will be processed first and it will move to second line and so on in downward direction. This file will needs read access rights for <sid>adm.
Now we need a executable file to add transports in buffer, it does not matter if the transports are already there in buffer or not, below script is not going to do any harm in system, run it anyway before starting the import script file.
2. /usr/sap/trans/TrnScript/trns_add2buff.sh
$ more trns_add2buff.sh
# Start of Script file
#! This script will add transports to buffer one by one sequentially.
# The list of transport should be given in transport_list.txt file where
# each transport should be in new line.
###
TPLIST=/usr/sap/trans/TrnScript/transport_list.txt
TPSTATUS=${TPLIST}.log
for i in `cat ${TPLIST}`
do
/usr/sap/DT9/SYS/exe/uc/linuxx86_64/tp addtobuffer $i DT9 u1 pf=/usr/sap/trans/bin/TP_DOMAIN_DT9.PFL
RC=$?
print "`date`...Transport ${i} Status RC=${RC}" >> ${TPSTATUS}
done
# End of script file
This file should have executable rights for <sid>adm. Check this file carefully for the path mentioned for
(a) TPLIST
(b) tp
(c) DOMAIN file
When above script file will execute, it will create a log file named transport_list.txt.log at same location where transport_list.txt file is present, provided <sid>adm has write access to the directory. The log file will contain information like below
$ more transport_list.txt.log
Mon Apr 30 06:49:56 CDT 2012...Transport EC6K900076 Status RC=0
Mon Apr 30 06:49:56 CDT 2012...Transport EH4K930113 Status RC=0
Mon Apr 30 06:49:56 CDT 2012...Transport SA8K901225 Status RC=0
This log file will give you chance to check if data file and cofiles are present and readable. Also, if any of the transport is imported in system without option "Leave transport Request in Queue for Later Import" then it will add it again so the request can become transportable again. If you find any other return code than zero then correct the issue rename the log file and rerun this script file again and check log file.
If everything goes fine till here then we can go for transport import script file
3. /usr/sap/trans/TrnScript/trns_import.sh
$ more trns_import.sh
# Start of Script file
#! This script will import transports one by one sequentially.
# The list of transport should be given in transport_list.txt file where
# each transport should be in new line.
###
TPLIST=/usr/sap/trans/TrnScript/transport_list.txt
TPSTATUS=${TPLIST}.RClog
for i in `cat ${TPLIST}`
do
/usr/sap/DT9/SYS/exe/uc/linuxx86_64/tp import $i DT9 client=100 u0126 pf=/usr/sap/trans/bin/TP_DOMAIN_DT9.PFL
RC=$?
print "`date`...Transport ${i} Status RC=${RC}" >> ${TPSTATUS}
if [ "$RC" -ne 0 ] && [ "$RC" -ne 4 ]; then
break
fi
done
# End of script file
This script file will import transports with u0126 mode which means
0 - Leave Transport Request in Queue for Later Import
1 - Import Transport Request again
2 - Overwrite Originals
6 - Overwrite Objects in Unconfirmed Repairs
Import Option.jpg
If you want to select different option then you can adjust accordingly the number appended after "u" in script.
This file will create log file transport_list.txt.RClog which will contain the timestamp and RC of each transport.
The import of transport will stop when it will get return code other than 0 or 4
Now you can read SAP tp log and resolve the issue then you need to remove those transports which are already imported through script from file transport_list.txt and execute the script again.
If you want that in case of error too, the script should move ahead with next transport then you simply need to put # in start of these 3 lines or remove them from the script file
if [ "$RC" -ne 0 ] && [ "$RC" -ne 4 ]; then
break
fi
You can also use at now or cron to schedule the script as per your need.
Hope this will be of help to some of us.
Posted by Ishteyaque Ahmad in SAP on UNIX
Tags:
script for multiple tp addtobuffer and tp import Mass adding of transports SAP Add to Buffer & Import Multiple Transports using TP Scripts how import mass transport requeast at os level
SAINT Stack.xml
New add-ons require stack.xml when imported through SAINT tool in SAP ABAP systems.
Generate the stack.xml in Solution Manager and upload them to SAINT and proceed further.
Generate the stack.xml in Solution Manager and upload them to SAINT and proceed further.
