Different selection of printed characteristics (LO-VC) according the smartforms

[former_member585917]

Hello,

Our users would like to have the possibility to print a different list of characteristics on manufacturing orders than on the sales documents.

Currently, the characteristics that need to be printed are flagged in CL02 in the area RMCLM-DRURE.

What would be the better way to implement this change ?

I'am not familiar with smartforms. From what I've seen in other messages, maybe it would be possible to use a ZTABLE and a FM in Manufacturing orders smartform instead of RMCLM-DRURE.

I've have already created Ztable for query purpose, so with some similar examples Im expecting to be able to use code in smartforms.

Regards, François.

[former_member585917]

Thank you Jelena for your answer.

As it's my first post on the community help portal, I am not familiar with Tags, ... I'am going to update the post.

I was not aware of BRF+, it sounds goods to implement business rules (e.g SD users have just logged a new one about price list selection depending of combination of customer group, current date and requested delivery date of sales orders).

For my request, hardcoding in the form should tthe quick solution to be explored as characteristics to be printed follow a static rule.

There is the case where some characteristics that are not displayed at the user according the value of the previous ones (display dependancy), so they don't need to be printed if not displayed. But I'am exepecting that they are not at the output of the file which be exploited by the smartforms program.

[Jelena]

Other than the general print indicator you've already noted I'm not aware of separate ones for SD/PP. (Might want to search in SAP Notes though in case there was an enhancement delivered for this recently.)

Depending on the actual requirements in can be either just hardcoded in the form / output program or it could be a custom table, as you've suggested. Normally hardcoding is not recommended but if you have rather static rules about what's printed and what's not (e.g. certain characteristic name pattern) then there is no reason to complicate things with Z table. It really depends on how complex you are expecting the rules to be and whether they'll change a lot. Z table would be a more dynamic solution, of course, but you'd need to remember to maintain the table.

You could also look into using BRF+ (Google it, lots of blogs on the subject out there), which might offer the best of both worlds: simplicity of hardcoding with flexibility of a Z table.

P.S. Please use more specific tag if you'd like to get more answers. Both SD and PP tags would give you better exposure.

P.P.S. This can also be a good subject for one of those Customer Engagement Initiatives SAP is running once a year. I believe new SD one will start in August-September. Many companies are likely to have similar requirements.