Start of the Support Package Import
Process 
Use
When you use the JSPM to import the Support Packages into the first runtime system in the sequence, you start a process in which the Support Packages are imported into the runtime system of the NWDI-driven landscape.
Prerequisites
Procedure
...
1.
In the first
runtime system, start the import of the Support Packages with the JSPM (see 
Applying Single
Support Packages).
2. A dialog box is displayed in which you have to specify the following:
○ Is Web AS Java configured as a runtime system in an NWDI track?
Answer this question with Yes.
If you answer this question with No, modified software components are replaced by new SAP versions. This can stop your own applications from working.
○ What is the role of the system in the track?
Answer this question with DEV or CONS.
If the first runtime system that receives Support Packages from JSPM is configured as a test or production system in the corresponding NWDI track, you must respond to the query about its role with DEV or CONS; this enables you to make modifications in the logical development system of NWDI. Otherwise, JSPM will search for replacement components for the modified software components without success.
Result
If you make the above settings, the JSPM imports only unmodified software components into the runtime system. Any modified software components, and any software components that depend on the modified software components, are not imported by the JSPM.
After the deployment, the JSPM copies all SCAs to the directory $(TRANSDIR)/EPS/in/CMS$(HOSTNAME)$(SYSTEMNAME). This directory is a temporary import directory for CMS. This action is documented by JSPM in a warning:
Warning: Component ... is a modified component and will only be transported to the CMS transport directory ... without deployment because this is a NWDI controlled DEV system.
See also:
Applying a Support
Package Stack
For more information, see:
● Maintenance of an NWDI-Driven System Landscape
● Adjusting Modifications with the NWDI