[eGroups Migratio...]

Hi,

Do anyone has idea about the below issue:

I am using scratch pad variables to map to target field. In Simulation trace I can see the value of the scratch pad variable correctly but still it did not fire it to target field. In some other map it does the desired function but sometimes I have seen this it is not mapping value to output field.

Is there any special reason for values to be mapped to output field?

Thanks for help!!

Neeraj

[eGroups Migratio...]

Hi Neeraj,

Scratchpad variables are not “fired” as soon as there is no “live” (input) data available being mapped to a field on the same level (container).

Regards,

Bas

[eGroups Migratio...]

Hi Bas,

Thanks for your response.

If I understood correctly, you mean I must have some other DLN with input value on the same level or container. Even if the scratch pad variable has some value and I don’t have other links at same level (with value), it won’t fire the link for scratch pad.

Am I right?

Thanks again.

Neeraj

[eGroups Migratio...]

Hi Bas,

Thanks for your response.

If I understood correctly, you mean I must have some other DLN with input value on the same level or container. Even if the scratch pad variable has some value and I don’t have other links at same level (with value), it won’t fire the link for scratch pad.

Am I right?

Thanks again.

Neeraj

Neeraj,

You are completely right. The only way to work around this (in case you have no other fields to map), is to drag a link from the input to your destination field and overwrite the value (src expression) with the scratchpad variable.

Regards,

Bas

[eGroups Migratio...]

Neeraj,

You are completely right. The only way to work around this (in case you have no other fields to map), is to drag a link from the input to your destination field and overwrite the value (src expression) with the scratchpad variable.

Regards,

Bas

or you can do a "force write" to force the scratchpad variable to be mapped to the destination field irregardless of whether there's existing DLN on the same level.

Michael

[eGroups Migratio...]

or you can do a "force write" to force the scratchpad variable to be mapped to the destination field irregardless of whether there's existing DLN on the same level.

Michael

Yes, the force write is a second good option, although it might have the unwanted side-effect that the field is created “always”. In case you have containers on a higher level being filled with scratchpad variables as well, these fields will be created as well, since the child is being created in a “forced” way.

Bas

[eGroups Migratio...]

Yes, the force write is a second good option, although it might have the unwanted side-effect that the field is created “always”. In case you have containers on a higher level being filled with scratchpad variables as well, these fields will be created as well, since the child is being created in a “forced” way.

Bas

Thanks All. The problem is solved now. Actually I was working with ST/SE segments and ST/e02 was not mapped so whenever I was mapping value to SE/e02….result was……nothing….

So as per your remarks, I mapped ST/e02 and then SE/e02 also worked fine….because both are at same level…

Thanks again…

Regards,

Neeraj