ABAP Guidelines for transfer rules & Update rules

[Former Member]

Is there any guidelines for abap when using it for transfer rules and update rules? I am looking for some best practise in this area.

Thank you,

[Former Member]

All limitations that apply to writing an ABAP program apply here.

The only key difference here is that the LIST processor is not available! This means that you cannot use statements like "WRITE" in these routines.

Additionally, there are no events here. As the name suggests, these are subroutines and have to be treated as such.

The documentation links posted by me in the in the previous post will throw some light on what data (variables) is available in these routines and what steps need to be taken care off. Read the sub topics in the links as well!

Unfortunately, there is no easy way to siphon this information into a couple of sentences! Hope I am guiding you down the right path!

Rishi

[Former Member]

Probably the wrong forum for the question, but here are the documentation links.

<a href="http://help.sap.com/saphelp_nw04/helpdata/en/80/1a64c6e07211d2acb80000e829fbfe/frameset.htm">Update Rules-Click Here</a>

<a href="http://help.sap.com/saphelp_nw04/helpdata/en/80/1a62bfe07211d2acb80000e829fbfe/frameset.htm">Transfer Rules-Click Here</a>

Happy reading!

Rishi

[Former Member]

Thank you. I checked the help site but I am looking for abap guidelines when using transfer vs update rules. In essence are there different standards that we should follow when writing abap codes in transfer rules compared to update rules.

[Former Member]

There is no specific differences in the standards/coding procedure for Transfer Vs. Update Rulse.

This can only come from a combination of requirement, design and experience! (in no particular order)

for e.g.

If the converions are the same for all data targets, you would use the transfer routine, start routine in the Transfer rules.

If the converions are different for different data targets, you would use the update routine, start routine in the Update rules.

Key concerns being performance, modularization, reduced effort and ease of maintenance.

Not sure I have answered you question! Please get back if there is something specific you are interesed in (a scenario perhaps!)

Rishi

[Former Member]

Thanks once again. I am not an Abap person, so I guess I am not explaining it correctly. I am doing some documentation on best pratices and one of thme is to come up with abap guidelines when writing an abap routine keepong in mind the do's & dont's of the code or the function module or limitations of an internal table, etc, etc. Hope I am explaining this well.

Appreciate your time very much.

[Former Member]

All limitations that apply to writing an ABAP program apply here.

The only key difference here is that the LIST processor is not available! This means that you cannot use statements like "WRITE" in these routines.

Additionally, there are no events here. As the name suggests, these are subroutines and have to be treated as such.

The documentation links posted by me in the in the previous post will throw some light on what data (variables) is available in these routines and what steps need to be taken care off. Read the sub topics in the links as well!

Unfortunately, there is no easy way to siphon this information into a couple of sentences! Hope I am guiding you down the right path!

Rishi

[Former Member]

Thank you very much. I will check. Appreciate all your pointers and help.

[Former Member]

The pleasure was mine! Thanks for the awarded points!