While the short answer is no, there is a way to de-envelope inbound EDI data and then re-envelope and transmit to another partner without transformation.
The first step would be to use the EDIDeenvelope process having Inbound ISA, GS, ST envelopes for the values in the data, have a translation map (EDI > EDI) on the inbound ST envelope specified. The map would have an additional Header record on the Output side - this will be for the new Outbound Envelope values desired. This is needed in case there are multiple Transactions/documents within the Interchange. You can create the input side based on the inbound data and then save as .ddf and use that .ddf to create the Delimited output side. Under Functions, there is an Auto Link option that you can use to link everything across. Make sure you have one valid link to the output Header record for the extended rule to run and populate the Sender/Receiver/ALA values with your new Outbound Envelope values.
The Inbound ST/SE envelope would have a Business Process specified that contains the Document Extraction service with the following settings
<assign to="." from="*"></assign>
The Delimited_DocExtract map will split the file if there are multiple transactions (otherwise the output could have multiple transactions/documents within one ST/SE).
The Update/Document Extraction Standard rule would be placed on each respective field, and the Sender field would contain the extended rule to split the documents:
String  buffer;
buffer = "";
While Readblock(buffer) do
If left(buffer,3) = "HDR" then
You will need to create Outbound ISA, GS, ST envelopes and once again a map to link (using the Function/Auto Link) to link everything from input to output.
Again, if you do not have this, it will envelope multiple transactions within one ST/SE envelope.
ANOTHER possible OPTION:
In this example only the Sender IDs needed to be modified prior to sending out. This example and map is specific to the positioning of the Sender ID values and also took into consideration the ISS segment that happen to be present in the test data. Below is a snippet of the original test data where only the Sender ID needs to be changed:
ISA*00* *00* *12*THIS1 *01*888888885 *150905*1724*U*00401*000000040*0*P*>~
N1*RI*Elizabeth Arden Inc*1*849222187~
ITD*08***20151004**20151004*30*****NET 30 DAYS~
CAD****RPSC*FEDEX SMALL PACKAGE - COLLECT**BM* ~
(there were multiple transactions)
Since the ISA is a static length, and the GS Sender only needed to be changed a Positional to Positional map was created to change the values.
Here is a sample rule that was used to change the IDs:
string  lbuffer;
string  rbuffer;
if left(buffer,3) = "ISA" then
if mid(buffer,35,15) = "THIS1 " then
lbuffer = left(buffer,35);
rbuffer = right(buffer,56);
buffer = lbuffer + "YOUR VALUE1 " + rbuffer;
if left(buffer,2) = "GS" then
if mid(buffer,6,5) = "THIS1" then
lbuffer = left(buffer,6);
rbuffer = right(buffer,37);
buffer = lbuffer + "YOUR VALUE1" + rbuffer;
if left(buffer,2) != "GS" | left(buffer,3) != "IS" then