on 2019 Sep 13 10:29 AM
Hi guru's,
These question could be too simple for the most of you...
Is it possible before I generate a report, enter values manually to defined fields in this report? (like the same function for GLM when user specific values can add before print out?)
Reason for asking: I would use different footers (adresses) for one report.
Dear Holger
my "main" concern is the difference between the "user entry report symbols" used mainly in GLM and your story.
Your feedback is "exactly" which what I assumed. So my story would run like:
Based on a condition "e.g. sales org" something different should be printed. Now as the condition comes "outside" of EHS we are talking about a "parameter symbol".
The data you are talking about is as well related to the story of "cover sheet" in SDS dispatchment; here you use (normally) as well "footers" etc. (but this is handle different: normally by "company" one cover sheet is generated (but in most cases: we do talk "only" about <20 companies to consider)
So if you use CG50/CG54 you can select an "initiator" (= sales org) and based on this you can print what you would like to print, The major difference to the "user entry story" is that you can use this approach "better" in CG50/CG54; but yes: the user must specify something in CG54 to get the "right" print; but !! the e.g. sales org is a parameter which can be stored in the "user parameters".
So if the user has selected the "US Company". The next time he use CG54: he will see "automatically" the "US" like look and feel without entering something (not sure if the same can be achieved using the "user entry story); this is different to the "user entry" story, Here the user must once again ! select "US" as the company
Address/Footer story as such: yes SAP is delivering something here to be used in WWI; but after talking with many companies using EHS: most of them use a "customer driven" solution for this but >90% of them use as the "selection" e.g. sales org to select the right data.
And as mentioned: this "decision" of the user (select on sales org) can be stored in the "user parameter" (the same is true if you select property tree "STANDARD")
The "only" con of this solution is; if the same user should now "print" the german data; he/she must change e.g. "initiator" and this is then once again stored in user parameter.
I am pretty sure: if only the "footer/address" story is different in your two WWI layouts: there is a feasible approach existing to combine the WWI logic in one WWI template
C.B.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Holger
The options provided by Satya and Idrees can be used; No discussion. There is only a "but".
Depending on your "exact" demand: there are better solutions in place.
Example:
This is your demand:
"Reason for asking: I would use different footers (adresses) for one report."
Let us assume now this;
The "address" you would like to print represent the data in "sync" to the company acting (or the sales org, the company code, the plant acting etc.)
If we talk about e.g, a "company code" there a lot of "report" examples which print huge amount of stuff. One "simple" example is just print:
I am company X located in Y having postal code Z etc.
In such a case the story should run different.
SAP provides the option to set up a "company code". Any company code is liked to an "address" (from module Business Partner); in such a case you can use "final report" parameters to "retrieve" this data (the address data from company code)
The "only" selection (e.g. in CG50) would be: specify the "sales org" or the "company code" and the WWI process will collect the data (and in context of SDS process: it will store the data; for other reports types: this is a different story (e.g. GLM runs different here).
AND you must pay attention regarding your "wording". If my assumption is correct: then the data is coming from "final report symbol". So there is no "before generation of process". The generation of WWI report can be splitted (in > 80% of the cases) in two phases: generate the "raw report" or "generate the final report".
In the raw report specification data is collected. ONLY this data is really stored in a document in SAP. Final report symbol data is not stored in the document as stored in SAP but in different places (check SDS distribution)
PLease read the blog "WWi for beginners", "WWI for experts" etc.
But the term "footer" does have a huge amount of "meaning"; the same is true for the term "address" data
For "footer" and similar stories in context of SDS: SAP has improved here the "picture"; this is not discussed here (nether seen any thread), but there are new options in place
Any how: please explain better your "footer" and "address" story
C.B.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Christoph,
always a helpfull comment from you. Actually we have 2 different reports in place, because of different design and Information on that reports. I would like to merge both reports to one which can provide all requriments in just one report. For that, one challange is the footer (Fußzeile) where we print our postal adress, e-Mail and phone information of (1) our company site in Germany or for the (2) report these from our site in the US. -> But we can't say in advance or in regarding the data in specification which adress we need for print out, so the user which will generate the report, should choose which one of both adress codes will needed / print out before creating.
H.H.
Hello Holger Hartung,
You can try Parameter Symbol as well - Whenever you generate a report - A pop-up comes where you can enter values manually at run time, Mostly it is used for - Customer Name / Material number and other general information.
Thanks
Idrees
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
3 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.