Non decimal currency in workflow inbox

Fri Dec 7 00:10:13 EST 2007

hello Guys,

Thanks for your reply, solved it as Florin said.

Florin, 

Thank you!

Best Regards,
Ameko.> From: sap-wug-request at mit.edu> Subject: SAP-WUG Digest, Vol 37, Issue 15> To: sap-wug at mit.edu> Date: Thu, 6 Dec 2007 07:55:36 -0500> > Send SAP-WUG mailing list submissions to> sap-wug at mit.edu> > To subscribe or unsubscribe via the World Wide Web, visit> http://mailman.mit.edu/mailman/listinfo/sap-wug> or, via email, send a message with subject or body 'help' to> sap-wug-request at mit.edu> > You can reach the person managing the list at> sap-wug-owner at mit.edu> > When replying, please edit your Subject line so it is more specific> than "Re: Contents of SAP-WUG digest..."> > > Today's Topics:> > 1. Re: HTTP-Errors in Approval Step for Standard Task TS50000075> (Baerbel) (Ananth)> 2. Re: Non decimal currency in workflow inbox (Ananth)> 3. RE: SMS Through Workflow (???? ????)> > > ----------------------------------------------------------------------> > Message: 1> Date: Thu, 6 Dec 2007 12:05:22 +0100> From: Ananth <write2ananth at gmail.com>> Subject: Re: HTTP-Errors in Approval Step for Standard Task TS50000075> (Baerbel)> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>> Message-ID:> <7e1903b20712060305q33189f2avc2f23902dd2bf11c at mail.gmail.com>> Content-Type: text/plain; charset=ISO-8859-1> > Hi Baerbel,> > I think you need to maintain 'Visual Parameters'. Please check the> values, since it is different for different systems, since we use JSP> Iview at this client's place.> Also please check QISRSCENARIO for the scenario id and what is that> maintained for your scenario.> > Regards> Ananth> > On 12/6/07, baerbel.winkler at carestreamhealth.com> <baerbel.winkler at carestreamhealth.com> wrote:> >> > Hi Ananth,> >> > thanks for your reply!> >> > I just checked transaction SWFVISU and I see this entry:> > Task Visualization Type> > TS50000075 IVIEW IView> >> > There is nothing maintained, though, under "Visualization Parameters" for> > TS50000075.> >> > Thanks and Cheers> > Baerbel> >> > >> > > Message: 1> > > Date: Wed, 5 Dec 2007 21:00:51 +0100> > > From: Ananth <write2ananth at gmail.com>> > > Subject: Re: HTTP-Errors in Approval Step for Standard Task TS50000075> > > To: "SAP Workflow Users' Group" <sap-wug at mit.edu>> > > Message-ID:> > >> > <7e1903b20712051200l56808871rfaac98a0c3278db at mail.gmail.com>> > > Content-Type: text/plain; charset=ISO-8859-1> > >> > > Hi Baerbel,> > >> > > Can you please check whether you have maintained TS50000075 in SWFVISU> > > transaction.> > >> > > Regards> > > Ananth> > >> > > On 12/5/07, baerbel.winkler at carestreamhealth.com> > > <baerbel.winkler at carestreamhealth.com> wrote:> > > >> > > > Thanks, Mike, for your quick reply!> > > >> > > > Unfortunately, my colleagues already checked out transaction WF_HANDCUST> > and> > > > the settings there look okay.> > > >> > > > At the moment we are really at a loss and don't know where else to look> > or> > > > what else to try.> > > >> > > > Thanks and Cheers> > > > Baerbel> > > >> > > > > ------------------------------> > > > >> > > > > Message: 3> > > > > Date: Tue, 4 Dec 2007 11:01:47 -0000 (UTC)> > > > > From: "Mike Pokraka" <asap at workflowconnections.com>> > > > > Subject: Re: HTTP-Errors in Approval Step for Standard Task TS50000075> > > > > To: "SAP Workflow Users' Group" <sap-wug at mit.edu>> > > > > Message-ID:> > > > >> > > >> > <32689.194.74.202.254.1196766107.squirrel at mail.workflowconnections.com>> > > > >> > > > > Content-Type: text/plain;charset=iso-8859-1> > > >> > > > >> > > > > Hi Baerbel,> > > > >> > > > > As far as the WUG/SDN question goes, there is a certain overlap. SDN> > is> > > > > driven by points so if you want a quick answer post there. WUG is> > driven> > > > > by interest and enthusiasm, so if you want a good answer post here. It> > all> > > > > depends on your question and it's complexity/urgency really. Nothing> > > > > stopping you from posting in both (though a small PS. note wouldbe> > nice).> > > > >> > > > > To your question: It sounds like your web service handlers aren't> > setup.> > > > > Txn WF_HANDCUST should do the trick - it's mostly auto-generated but> > you> > > > > may need some basis input for hostnames etc. It's also reasonably well> > > > > documented.> > > > >> > > > > Hope that helps, shout back if not.> > > > > Cheers,> > > > > Mike> > > > >> > > > > On Tue, December 4, 2007 10:06,> > > > baerbel.winkler at carestreamhealth.com wrote:> > > > > Hi Folks,> > > > >> > > > > as this is my very first post to WUG, here is a quick introduction:> > I've> > > > > been involved with SAP and ABAP for almost 8 years (prior to that I> > did> > > > > PL/1-development) but I'm completely new to Workflow (just had BIT601> > last> > > > > month). I already spent some time reading and searching through the> > > > > SDN-Forums/Blogs/Wikis and have posted this question there as well> > last> > > > > week, but - helpful as they were - the replies haven't yet solved our> > > > > issue. As I don't really know how much overlap there is between> > SDN-forum-> > > > > and WUG-participants, I'd like to try this venue as well.> > > > >> > > > > Now for my current issue:> > > > >> > > > > I'm involved with a project to make use of the Manager Self Service> > (MSS)> > > > > functionality provided by SAP. A colleague and I are trying to follow> > the> > > > > information provided by SAP in these three documents: "Configuration> > Guide> > > > > for the Personnel Change Request (Release 60.1)", "Developing your own> > > > > personnel change requests (Release 50.1/50.2)" and "Internal Service> > > > > Request (ISR) cookbook (July 2004)". We are running Netweaver 04, SAP> > > > > Basis 620, SAP_HR 470.> > > > >> > > > > As a prototype, we've managed to get scenario SPPD for "Change> > Position> > > > > (enhanced)" set up in the MyHRManager-section of the portal. We can> > submit> > > > > the form for one of the employees we've set up in the development> > system> > > > > and we also see (via transaction SWEL) that Standard Workflow> > WS50000041> > > > > is triggered. Subworkflow WS50000033 is triggered as well and the> > > > > work-item for standard task TS50000075 gets assigned to the correct> > > > > responsible agent (we did have an issue with the agent-assignment> > earlier,> > > > > but - for whatever reason - this is now working fine).> > > > >> > > > > Whenever the responsible agent tries to process the workitem, we get> > the> > > > > following two HTTP-related errors and don't seem to be able to find> > the> > > > > root-cause for them:> > > > >> > > > > 1.> > > > > Work item 000000319008: Object method SWW_WW_EXECUTE_S cannot be> > executed> > > > > Message no. WL821> > > > >> > > > > 2.> > > > > HTTP handler for starting an external service cannot be read> > > > > Message no. SWK045> > > > >> > > > > I did find a reference to WL821 in OSS where it says that this is> > usually> > > > > a very meaningless message, but I didn't find anything for SWK045.> > Does> > > > > anybody have any ideas which configuartion settings we might need to> > check> > > > > and possibly modify? Unfortunately, neither my colleague nor myself> > really> > > > > know what we need to be on the lookout for, so any information will be> > > > > helpful. We also already tried to find out where these messages get> > > > > triggered via debugging, but were not successful. A "where-used" for> > the> > > > > messages also didn't find anything.> > > > >> > > > > Before we can progress with our project, we are fairly certain that we> > > > > first have to get the SAP-supplied PCRs working - otherwise we'll> > later> > > > > never know where any issues are coming from!> > > > >> > > > > Thanks and Cheers> > > > > Baerbel> > > > > _______________________________________________> > > > > SAP-WUG mailing list> > > > > SAP-WUG at mit.edu> > > > > http://mailman.mit.edu/mailman/listinfo/sap-wug> > > > >> > > >> > > > _______________________________________________> > > > SAP-WUG mailing list> > > > SAP-WUG at mit.edu> > > > http://mailman.mit.edu/mailman/listinfo/sap-wug> > > >> > > >> >> > _______________________________________________> > SAP-WUG mailing list> > SAP-WUG at mit.edu> > http://mailman.mit.edu/mailman/listinfo/sap-wug> >> >> > > ------------------------------> > Message: 2> Date: Thu, 6 Dec 2007 12:15:00 +0100> From: Ananth <write2ananth at gmail.com>> Subject: Re: Non decimal currency in workflow inbox> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>> Message-ID:> <7e1903b20712060315j4a49bb41h575da21dbd27e88c at mail.gmail.com>> Content-Type: text/plain; charset=ISO-8859-1> > Hi Xuetang,> > Please check the default settings of WF-BATCH user, since the date and> currency settings can be displayed according to that.> > Another possible thing is get the user default settings from USR01 of> the manager and set the currency/date settings accordingly before> sending workitem/mail to the manager.> > Regards> Ananth> > On 12/6/07, Florin Wach <florin.wach at gmx.net> wrote:> > Hi,> >> > I think you'll have to create a new virtual attribute on the deviated object for BUS2081, e.g. TotalAmount_text> > As you cannot connect an Amount-field to the Currency-field, the workflow system cannot use the correct currency (as in the statement WRITE...TO....CURRENCY cur.) and will always use a 2-decimal-currency instead.> >> > To avoid such problems, define your amount-field as pure character, length 17 or so. In the virtual attribute read the correct amount and use the WRITE-TO statement using the currency conversion.> >> > If you're unfamiliar with the implementation of a sub-objecttype, system-wide delegation and virtual attribtutes, please have a search in the documentation, the mailing list here and/or the SAP-SDN.> >> > Best wishes,> > Florin> >> > -------- Original-Nachricht --------> > > Datum: Thu, 6 Dec 2007 05:37:59 +0000> > > Von: xuetang chen <chenxuetang at hotmail.com>> > > An: sap-wug at mit.edu> > > Betreff: Non decimal currency in workflow inbox> >> > >> > > Hi,> > >> > > In my workflow, after the user enter the incoming invoice (MIRO) will send> > > out a email with PO number, amount, currency to manager inbox, the manager> > > will approve it.> > >> > > Right now, it not worked for non decimal currencies, such JPY, KRW. for> > > example, the amount is 1000JPY will display as 100.00 JPY in manger inbox.> > >> > > I know i can use 'FWOS_CURRENCY_DECIMALS_READ' to get local currency> > > decimal , or use write amount to field with currecny to process it in the> > > report, but now i do not know how to process it in workflow inbox, where i should> > > put my codes?> > >> > > Thanks!> > > ------------------------------> > Message: 3> Date: Thu, 6 Dec 2007 14:42:40 +0200> From: ???? ???? <ronenf at paz.co.il>> Subject: RE: SMS Through Workflow> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>> Message-ID:> <FB3AF7DD0A0A474FB07A5E15675966C703134BC2 at PAZMAIL.paz.local>> Content-Type: text/plain; charset="windows-1255"> > David,> > Try formatting the recipient address like this:> > SMS:0505222111 (put the string SMS: before the number)> > > Also, just remembered, you need to set up SMS as a valid transmission type in customizing.> This is done in the IMG (Transaction SPRO) in the following path:> > SAP Netweaver - Application server - Basis services - Address management - Define pager services> > You just need to define a service there - here is how it looks in our system> > > > > I hope this helps,> > Best regards,> Ronen> > -----Original Message-----> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Bibby, David> Sent: Thursday, December 06, 2007 12:30 PM> To: SAP Workflow Users' Group> Subject: RE: SMS Through Workflow> > > Hi Ronen,> Thanks for your reply.> I have tried this and replaced the recipient e-mail address with the mobile phone number.> > > However when I check in SOST the message sent is in error status with'> Specify a valid recipient of the object. The address <mobile number> or address type 'INT' you specified (no 'type' specification is equivalent to the SAP address) contains an error.> > However from speaking to our mobile phone team we do not have a service that allows us to SMS phone numbers as e-mail addresses.> Does this also mean that your method explained calling 'SO_DOCUMENT_SEND_API1' will not work anyway?> > Regards> David> > > ________________________________> > From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of ???? ????> Sent: 06 December 2007 04:49> To: SAP Workflow Users' Group> Subject: RE: SMS Through Workflow> > > Hello JM,> > First, please remove the screenshot from the mail before replying to the group since it takes up plenty of space...> > Now for the SMS:> > A service provider is a server with sms sending software that "knows how to" send text messages from a computer to any of the mobile numbers in your country or outside. This can be a server installed on your site or a server belonging to another company to which you will have to pay a fixed price for the SMS messages you wish to send. Anyway this is a component outside of the Netweaver platform and must be addressed as an external service - this is done via configuration transaction SCOT> > As for your questions:> 2. You need authorization for send process in the SAP system, needs to be checked out if there is a restriction on the recipient type.> 3. The format of the recipient ID is between you and the service provider> 4. See explanation above> 5.Enclosed please find a sample of the calling of the standard SAP function we perform> > CALL FUNCTION 'SO_DOCUMENT_SEND_API1'> EXPORTING> document_data = document_data> put_in_outbox = 'X'> sender_address = sender_address> sender_address_type = 'B'> commit_work = 'X'> TABLES> packing_list = packing_list> contents_txt = contents_txt> receivers = receivers> EXCEPTIONS> too_many_receivers = 1> document_not_sent = 2> document_type_not_exist = 3> operation_no_authorization = 4> parameter_error = 5> x_error = 6> enqueue_error = 7> OTHERS = 8. > > I hope this is helpful> Thanks,> Ronen Fox> Paz Oil Co.> > > > -----Original Message-----> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of JITU MOHAN> Sent: Wednesday, December 05, 2007 1:33 PM> To: SAP Workflow Users' Group> Subject: Re: SMS Through Workflow> > > Hi,> > I have following queries:> 1. Please explain me about the service provider, i mean do we need to have a service provider who allow us to use there services. > More explaination with example will be helpful.> > 2. While sending message do we need any specific authorization.> 3. Is there any specific format of receipent ID and all?> 4. Can we send Local/National/Internaltional SMSes?> 5. Can you provide me any sample code in ABAP.> > Thanks,> JM> > > On Dec 5, 2007 4:30 PM, ???? ???? <ronenf at paz.co.il> wrote:> > > Hi,> > The steps for configuring SCOT depends on your SMS service provider.> > The system needs some sort of an external service in order to be able to send outgoing SMS messages.> Once you set up an account with the service provider, the node at transaction SCOT should look something like this:> > > > > I hope this helps. You are welcome to ask further questions.> Thanks,> Ronen> > -----Original Message-----> From: sap-wug-bounces at mit.edu [mailto: sap-wug-bounces at mit.edu <mailto:sap-wug-bounces at mit.edu> ] On Behalf Of JITU MOHAN> Sent: Wednesday, December 05, 2007 12:47 PM> To: SAP Workflow Users' Group> Subject: Re: SMS Through Workflow> > > > Hi Ronen, > > The steps provided by you are very useful, could you provide me the steps for configuring SCOT for SMS/Pager. > > Thanks in advance... > > Warm Regards, JM> > > On Dec 5, 2007 10:32 AM, ???? ???? <ronenf at paz.co.il> wrote:> > > Hello David,> > We have a workflow sending out SMS messages.> > The way it is set up is as follows:> > 1. Maintain the mobile number either in the person or the user master data> 2. Create a method or an attribute to read that number from the master data record.> 3. Create a method for sending the message based on SO_DOCUMENT_SEND_API1 function module. Be sure to pass the parameter sender_address_type = 'B' > 4. Your message is sent via the SCOT mechanism> > Of course you have to set up in transaction the option to send SMS via the PAG node. We did it with an external service provider that receives an http string from us. > > It works very good for us (hundreds of messages each day)> > Good luck !> > Ronen> > -----Original Message-----> From: sap-wug-bounces at mit.edu [mailto: sap-wug-bounces at mit.edu <mailto:sap-wug-bounces at mit.edu> ] On Behalf Of Sudhir Pargaonkar> Sent: Tuesday, December 04, 2007 6:54 PM> To: SAP Workflow Users' Group> Subject: Re: SMS Through Workflow> > > Hi David,> > I have done it before. Every mobile number has its own email address. You can get it from mobile career. (for example tmobile has :1234567890 at tmomail.com ). > > Just use send email step to send message to this address. Make sure to keep number of characters limited as per max length of SMS.> > Regards,> Sudhir> > > On Dec 4, 2007 10:38 AM, Bibby, David < david.bibby at linklaters.com> wrote:> > > Hi,> Has anyone ever managed to send SMS messages from a workflow?> I believe this is possible reading the SAPConnect documentation on help.sap.com <http://help.sap.com/> . > > If so can anyone tell me how this is done?> I have a requirement that when a new project (BUS2001) is released that we get the mobile number of the project manager from SAP HR and SMS them to let them know it has been released. > > Many Thanks> David> > _______________________________________________> > This communication, issued by Linklaters LLP or one of its affiliated firms or other entities carrying on business under or including the name 'Linklaters' (together "Linklaters"), is confidential and may be privileged or otherwise protected by work product immunity. If you have received it by mistake please let us know by reply and then delete it from your system; you should not copy it or disclose its contents to anyone. All messages sent to and from Linklaters may be monitored to ensure compliance with internal policies and to protect our business. Emails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. Anyone who communicates with us by email is taken to accept these risks. > > Linklaters LLP is a limited liability partnership registered in England and Wales with registered number OC326345. It is a law firm regulated by the Solicitors Regulation Authority (see www.sra.org.uk <http://www.sra.org.uk/> ). The term partner in relation to Linklaters LLP is used to refer to a member of Linklaters LLP or an employee or consultant of Linklaters LLP or any of its affiliated firms or entities with equivalent standing and qualifications. A list of the names of the members of Linklaters LLP together with a list of those non-members who are designated as partners and their professional qualifications is open to inspection at its registered office, One Silk Street, London EC2Y 8HQ or on www.linklaters.com <http://www.linklaters.com/> . and such persons are either solicitors, registered foreign lawyers or European lawyers.> > Linklaters LLP has taken over the greater part of the practice of Linklaters the general partnership. For information about this conversion, including any transfer of your information, and other important information on our regulatory position, please refer to www.linklaters.com/regulation.> > > > > _______________________________________________> SAP-WUG mailing list> SAP-WUG at mit.edu> http://mailman.mit.edu/mailman/listinfo/sap-wug > > > > > > _______________________________________________> SAP-WUG mailing list> SAP-WUG at mit.edu> http://mailman.mit.edu/mailman/listinfo/sap-wug> > > > > > > -- > Thanks & Regards, > Jitu Mohan > > > _______________________________________________> SAP-WUG mailing list> SAP-WUG at mit.edu> http://mailman.mit.edu/mailman/listinfo/sap-wug> > > > > > > -- > Thanks & Regards,> Jitu Mohan > > -------------- next part --------------> An HTML attachment was scrubbed...> URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20071206/ef88a0c9/attachment.htm> -------------- next part --------------> A non-text attachment was scrubbed...> Name: not available> Type: image/bmp> Size: 480038 bytes> Desc: Outlook.bmp> Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20071206/ef88a0c9/attachment.bin> > ------------------------------> > _______________________________________________> SAP-WUG mailing list> SAP-WUG at mit.edu> http://mailman.mit.edu/mailman/listinfo/sap-wug> > > End of SAP-WUG Digest, Vol 37, Issue 15> ***************************************
_________________________________________________________________
Connect to the next generation of MSN Messenger 
http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-us&source=wlmailtagline
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20071207/5acd1cbd/attachment.htm