Automate

Greetings;

If you are adding scripts, or if the update script is generating new fields, check the use existing input fields

For scripts that do different activities but you want to re-use fields, make sure you use the same group name when you add the script, and then check use existing input/output fields.

The only caveat to this - if you are using a repeating web service.  That script needs to have all of the fields in the same repeating group, so it cannot be scattered outside of the repeating group.

Hope that helps!
Sigrid

Greetings;

Hi, SIgrid;

Thank you very, very much for getting back to me with your explanations and descriptions on how existing field mappings can be maintained when re-importing a transaction script.

Your time and help are very much appreciated.

If you are adding scripts, or if the update script is generating new fields, check the use existing input fields

For scripts that do different activities but you want to re-use fields, make sure you use the same group name when you add the script, and then check use existing input/output fields.

The only caveat to this - if you are using a repeating web service.  That script needs to have all of the fields in the same repeating group, so it cannot be scattered outside of the repeating group.

Hope that helps!
Sigrid

Greetings;

Hi, SIgrid;

Thank you very, very much for getting back to me with your explanations and descriptions on how existing field mappings can be maintained when re-importing a transaction script.

Your time and help are very much appreciated.

If you are adding scripts, or if the update script is generating new fields, check the use existing input fields

For scripts that do different activities but you want to re-use fields, make sure you use the same group name when you add the script, and then check use existing input/output fields.

The only caveat to this - if you are using a repeating web service.  That script needs to have all of the fields in the same repeating group, so it cannot be scattered outside of the repeating group.

Hope that helps!
Sigrid

Greetings;

Hi, SIgrid:

I'd like to ask a follow-up question with a slight variation.

Lets suppose my Transaction Script has been updated to include one new parameter, but all of the other parameters for the Transaction are the same
(e.g., my new version of CreateCustomer.Txr has all of the same fields; we just added a new field in the SAP Transaction for "Warranty_Period", an input field or transaction parameter. )

Would your previous set of instructions on Updating the Transaction Script with Use Existing Input Fields and Use Existing Output Fields checked or enabled still allow the Web Service call to work as before, provided I provided Form Field Name mapping for the new "Warranty_Period" Web Service Field?   Are there any other settings or items I need to review and modify as part of performing a Transaction Script Update in this manner?

Again, many thanks for your time, help and patience.

Hi, SIgrid;

Thank you very, very much for getting back to me with your explanations and descriptions on how existing field mappings can be maintained when re-importing a transaction script.

Your time and help are very much appreciated.

If you are adding scripts, or if the update script is generating new fields, check the use existing input fields

For scripts that do different activities but you want to re-use fields, make sure you use the same group name when you add the script, and then check use existing input/output fields.

The only caveat to this - if you are using a repeating web service.  That script needs to have all of the fields in the same repeating group, so it cannot be scattered outside of the repeating group.

Hope that helps!
Sigrid

Greetings;

Hi, SIgrid:

I'd like to ask a follow-up question with a slight variation.

Lets suppose my Transaction Script has been updated to include one new parameter, but all of the other parameters for the Transaction are the same
(e.g., my new version of CreateCustomer.Txr has all of the same fields; we just added a new field in the SAP Transaction for "Warranty_Period", an input field or transaction parameter. )

Would your previous set of instructions on Updating the Transaction Script with Use Existing Input Fields and Use Existing Output Fields checked or enabled still allow the Web Service call to work as before, provided I provided Form Field Name mapping for the new "Warranty_Period" Web Service Field?   Are there any other settings or items I need to review and modify as part of performing a Transaction Script Update in this manner?

Again, many thanks for your time, help and patience.

Hi, SIgrid;

Thank you very, very much for getting back to me with your explanations and descriptions on how existing field mappings can be maintained when re-importing a transaction script.

Your time and help are very much appreciated.

If you are adding scripts, or if the update script is generating new fields, check the use existing input fields

For scripts that do different activities but you want to re-use fields, make sure you use the same group name when you add the script, and then check use existing input/output fields.

The only caveat to this - if you are using a repeating web service.  That script needs to have all of the fields in the same repeating group, so it cannot be scattered outside of the repeating group.

Hope that helps!
Sigrid

Greetings;