[LIKELY JUNK]RE: [LIKELY JUNK]Email Content not populated correctly

[Dart, Jocelyn]

Well ... I'd suggest you check that the language translations exist in
your production box. The transport process for translations is a little
complicated so it could just be that. 
And there are some global workflow admin settings around whether
workitems should be translated at all as there is a performance cost
involved.  But I don't normally have to bother
with translations so you might need to see who else on the forum can
help. 
Regards,
Jocelyn 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Preethi_Gurramkonda
Sent: Thursday, 12 February 2009 3:58 PM
To: SAP Workflow Users' Group
Subject: [LIKELY JUNK]RE: [LIKELY JUNK]Email Content not populated
correctly



Hi Jocelyn,

Thanks for the clarifications.

I have checked with the ID which has authorizations in production box.
now I can able to see the email content set.

Now the problem is in development box by logging in Chinese(ZH) the
subject of the email is coming properly however in production Box the
subject of the email is taking the task name. not the subject given in
the email step. Kindly let me know what is the reason for picking the
task name instead of the subject in Chinese language  even though in
Development box Its working properly.

Thanks & Regards,

Preethi G

Program SCALE - AMS

 

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Dart, Jocelyn
Sent: Thursday, February 12, 2009 9:54 AM
To: SAP Workflow Users' Group
Subject: RE: [LIKELY JUNK]Email Content not populated correctly

 

Preethi, 

Check the format of your business object reference.  Make sure the same
format is being used in dev and prod. 

Make sure delegation settings etc. are correct in prod. 

Check you are not being prevented from seeing data by authorization
issues - i.e. the person creating the work item must have access to
extract the data via the business object, the person viewing the work
item must have access to extract the data via the business object. 

Regards,

Jocelyn 

 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Preethi_Gurramkonda
Sent: Thursday, 12 February 2009 3:14 PM
To: sap-wug at mit.edu
Subject: [LIKELY JUNK]Email Content not populated correctly

Hi,

Workflow : vendor workflow. Business object : Created custom BO(super
type LFA1) , properly delegated

The email content is not populated properly. Some contents are coming
blank. Example vendor number, vendor name 

checked the binding in WF template. Its proper.

Checked the work flow log, there the BO is not set  . WF has not gone to
error.

The same workflow is working properly in development box. Only in
production box the contents are coming blank in the email as wel as the
BO is set.

Thanks & Regards,

Preethi G

 

 

________________________________

DISCLAIMER:
This email (including any attachments) is intended for the sole use of
the intended recipient/s and may contain material that is CONFIDENTIAL
AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or
copying or distribution or forwarding of any or all of the contents in
this message is STRICTLY PROHIBITED. If you are not the intended
recipient, please contact the sender by email and delete all copies;
your cooperation in this regard is appreciated.


________________________________

DISCLAIMER:
This email (including any attachments) is intended for the sole use of
the intended recipient/s and may contain material that is CONFIDENTIAL
AND PRIVATE COMPANY INFORMATION. Any review or reliance by others or
copying or distribution or forwarding of any or all of the contents in
this message is STRICTLY PROHIBITED. If you are not the intended
recipient, please contact the sender by email and delete all copies;
your cooperation in this regard is appreciated.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20090212/d97dc02c/attachment.htm