During planned system downtime or in case of emergency downtime, we require all iflows to be undeployed at the start of downtime and then redeploy them again when the downtime is over. This task usually is performed manually and requires a dedicated person to be available to perform the activity. There are blogs created by fellow community members which provide solution to deploy-undeploy all iflows. However, there are cases where all iflows or artifacts need not be undeployed. For eg: in case of S4HANA downtime, only iflows inbound to S4HANA need to be undeployed while outbound ones, value mapping, script collections etc. do not require to be undeployed.
This blog provides detailed steps and components that are required to manage only selective iflows during downtime.
During planned system downtime or in case of emergency downtime, we require all iflows to be undeployed at the start of downtime and then redeploy them again when the downtime is over. This task usually is performed manually and requires a dedicated person to be available to perform the activity. There are blogs created by fellow community members which provide solution to deploy-undeploy all iflows. However, there are cases where all iflows or artifacts need not be undeployed. For eg: in case of S4HANA downtime, only iflows inbound to S4HANA need to be undeployed while outbound ones, value mapping, script collections etc. do not require to be undeployed.This blog provides detailed steps and components that are required to manage only selective iflows during downtime. Read More Technology Blogs by Members articles
#SAP
#SAPTechnologyblog
