Identify the Sender

Hello to all,
Within my corporate environment, we have a case where an email account to be used by several people, type a group, like committee, and when one would use this account was recorded who sent this email, within the capabilities of GroupWise that is possible to be registered?

Hi,
Let me see if I understand your question correctly.... you want to have a single account but have several people using it. Then you want to know who exactly is using the account or who has sent e-mail from the shared account?
If that is true, I believe that you will be in violation of your licensing agreement.
Let me know if I have understood you correctly or not. Thanks.
Cheers,

Similar Messages

SMS alert - I dont want the name of the sender appearing on the screen

Prior to downloading the recent upgrade, my SMS alert would simply notify me that I had a new text message but would not identify the sender. Now, the sender's names appears on the screen. How can I change my setting so that the sender's name is not visible?

The SMS preview has been changed in the new firmware, see this thread:
http://discussions.apple.com/thread.jspa?threadID=1797569&start=0&tstart=0
So displaying the senders name can't be switched off. But you can forward your wish here:
http://www.apple.com/feedback/iphone.html.

BASED ON QUEUE NAME HOW CAN WE FIND THE SENDER SYSTEM IN ECC

Based on queue name how to identify the sender system
the issue is
Messages are are coming from pi to ecc , check below queues. These are incoming queues
to Ecc from PI. We are trying to find what these queues are. Sometimes these
are failing and we are not able to process,
Based on the above information we need to find the sender system from where it is coming.
Regards
MADHU

Hi srinivas- Thanks for your reply and there is no issue on pi side after reaching to ecc the entries got stucking in smq2 of ecc system now the target system wants to know on which sender system these messges are coming we are not finding sender system detials from smq2 of ecc system .
Regards
Madhus

Finding out the sender who sent a skype text alert

How do i find out who was the sender who sent me a message by skype text alert?

I have the same question. The SMS sender is only identified by a code. i do not know who the sender is and cannot respond to the email. Is it possible to identify the sender?

Is there any way to identify the particular socket connection is closed ?

Is there any way to identify the particular socket connection is closed or not ?
Any methods ???
How can the program knows the connection is lost or some thing ...
Is the socket throws some excpetions when there is no active connection ???
namanc

If you get an IOException when you try to use the socket, the connection was obviously closed.
The correct way for an application to know if the socket was closed is:
1) the server sends a message indicating that the socket should be closed
2) the client closes the socket itself

Use of ABAP expression in the Send Mail Header and Text

Hi Workflow Gurus,
I have a requirement wherein I have to inform the Manager of a user that his/her request for leave availment has been approved. However, we need to show the users name for the Manager to easily identify the user.
Now, I checked the send mail step and it is possible to insert an expression, but the available expressions are confined within the containers available. Hence, we only have the user id of the workflow initiator.
Is there a way to place a code in the send mail expression which will determine the user's employee name given the user id as opposed to having to create an FM and a method to determine the users name? Or is the only recourse to develop and fm and a method to determine these details in the background and pass it to the containers for extraction?
Regards,

If you don't have for example the employee name in the available container elements, you need to add it and do the necessary coding/development for it. Classically employee or user data has been retrieved by using a certain standard background task to get the user/employee object based on the user ID. This will require an additional background step but no coding since the task includes the coding already.
It is anyhow possible to try to get the data for example with functional methods by using container operations in the workflow (or it is also possible to do this in binding too) - but then you need to develop a functional method(s). In other words you can use a functional method for example in your binding or in a container operation. Check for example Jocelyn Dart's blog about functional methods. Anyhow, how well the functional methods will work depends on the SAP system version.
Regards,
Karri

Unable to identify the exchange protocol of the message (sync AS2 MDN)

Hi,
We got the following error:
Description: Unable to identify the exchange protocol of the message
StackTrace:
Error -: AIP-50080: Exchange protocol identification error
     at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1367)
     at oracle.tip.adapter.b2b.msgproc.Request.postTransmit(Request.java:2370)
     at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1813)
     at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:968)
     at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1152)
     at oracle.tip.adapter.b2b.xmlgwIntg.XMLGWIntegration.raiseOutboundMessage(XMLGWIntegration.java:168)
     at oracle.tip.adapter.b2b.xmlgwIntg.Outbound.onMessage(Outbound.java:297)
     at oracle.jms.AQjmsListenerWorker.dispatchOneMsg(AQjmsListenerWorker.java:316)
     at oracle.jms.AQjmsListenerWorker.run(AQjmsListenerWorker.java:129)
     at java.lang.Thread.run(Thread.java:534)
Here is the Wire message (sync MDN)
=======================
Message-ID=<23033756.391232032071968.JavaMail.SYSTEM@INUBITTEST>
Subject=Your ORDERS AS2
[email protected]
Content-Length=1347
MIME-Version=1.0
Server=Apache
Date=Thu, 15 Jan 2009 15:07:52 GMT
Content-Type=multipart/mixed;      boundary="----=_Part_53998_23619909.1232032071968"
[email protected]
------=_Part_53998_23619909.1232032071968
Content-Type: text/plain; charset=UTF-8; name=test.txt
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename=test.txt
Message-ID: <17080722.371232032071906.JavaMail.SYSTEM@INUBITTEST>
MIME-Version: 1.0
Content-Type: multipart/report; report-type=disposition-notification;
     boundary="----=_Part_53997_14786767.1232032071906"
AS2-Version: 1.1
AS2-From: test_AS2
AS2-To: as2me
------=_Part_53997_14786767.1232032071906
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
MDN for Message ID: <33156:4:0:137@as2me>
From: as2me
To: test_AS2
Received on: Thu, 15 Jan 2009 16:07:51 +0100
Status: processed
Comment: This is not a guarantee that the message has
been completely processed or unterstood.
------=_Part_53997_14786767.1232032071906
Content-Type: message/disposition-notification
Content-Transfer-Encoding: 7bit
Reporting-UA: inubit Integration Server
Original-Recipient: rfc822; test_AS2
Final-Recipient: rfc822; test_AS2
Original-Message-ID: <33156:4:0:137@as2me>
Disposition: automatic-action/MDN-sent-automatically; processed
Received-Content-MIC: 5kFOLMXOUurpm6DUTA8IMRj5gcs=, sha1
------=_Part_53997_14786767.1232032071906--
------=_Part_53998_23619909.1232032071968--
============================
The communication with our TP is going well, we are able to send, receive messages over AS2 and send back MDN, but we are not able
to receive their MDN.
Edit:
It seems that after the latest MLR patch, the error changed to [IPT_HttpSendError] HTTP encounters send error :. Premature EOF encounter but the roots seem to lead to the problem with MDN as B2B is sending the message a couple of times now and gives the mentioned EOF error.
Please advise,
Thank you
Edited by: Kamil Zadora on Jan 30, 2009 3:44 AM

Hi Ramesh,
Yes, agreement uses AS2 IDentifiers. Incoming messages are recognized correctly, and we send back sync MDN that is correctly received by our TP. They also recieve our messages correctly although Oracle B2B does not recognize the MDN from them. I think that this causes that, now after applying the latest MLR patch, B2B tries to send it around 6 times and gives the Unexpected EOF error.
Thank you for your help in advance,
Kind regards,

To identify the user running the job at runtime

Hi All,
My requirement is to develop a program which need to send mail only if a particular user runs the job.
I need to read the user who runs the job at runtime, i tried with SY-UNAME but it holds the user name of the person who created the job at runtime.
Please suggest me the possible ways of identifying the user running the job at runtime.
Thanks in advance!!!
Regards,
Dinesh.

"I need to read the user who runs the job at runtime, i tried with SY-UNAME but it holds the user name of the person who created the job at runtime."
This is not true if your program/form/method is called inside the ABAP report which is executing in the batch job step. There, the active SY-UNAME is the user entered in SM36 as the job step user. It is not the user who planned/scheduled the job.
It is unclear from your description where your program is actually running. Is it another (ABAP) step belonging to the same job or is it actually some routine called within the same job step that you are checking or is it a program totally unrelated to the batch job in question (in that case, check out the other answers about TBTCO/TBTCP)
- Alex

How to determine the sender business system for ABAP client proxy

Hi All,
I have one doubt: when the client proxy sends the message to XI, how could i know what is the sender business system name for it?
Is it the logical system which is reflected in Technical System?
let's say if i have the ABAP system, the technical system is ECC, which has three clients: 001, 066 and 000.
And the client 001's logical system in ECCCLNT001 (all the client proxy is created in this client). In this case, the sender business system name is ECCCLNT001, am i right?
If no, please correct me.
Thanks in advance
Leo

Hi lawrence
When data is distributed between different systems, each system within a network has to be clearly identifiable. The u201Clogical systemu201D deals with this issue.
A logical system is an application system in which the applications work together on a common data basis. In SAP terms, the logical system is a client.
Since the logical system name is used to identify a system uniquely within the network, two systems cannot have the same name if they are connected to each other as BW systems or as source systems, or if there are plans to connect them in any way.
Although SAP does not recommend that you connect test systems to production systems, a test system can have the same name as a production system. This makes copying production systems to test systems a lot simpler.
You are only allowed to change the logical system name of a system if the system is not connected to any other systems, because changing the logical system name would render all the connections to other systems useless.
Logical system names must contain capital letters and numbers only. SAP recommends the following naming convention for logical system names: <System-ID>CLNT<Client>.
Regards
sandeep

File-idoc Unable to convert the sender service to an ALE logical syste

Hi experts
iam working on file-idoc scenario ,iam getting the below error in sxmb_moni and RWB
"Unable to convert the sender service to an ALE logical system"
i checked the partnetr profile, RFC(sm59) and IDX1 t codes.
the connection is ok. but still i could figureout the problem.
please suggest me
Thanks
vasavi

Hi,
Have u checked the logical system is added in the Sender Business service in the Integration Directory?
Open the Buiness Service/System --> EDIT-ADAPTER SPECIFIC IDENTIFIERS
then specify the logical system name.
Go throgh the following link
Troubleshooting File-to-IDOC Scenario in XI.
Regards
Sridhar Goli

Unable to convert the sender service BS_PARTNER to an ALE logical system..!

Hi All,
File to IDoc scenario.
1. Business system is correct because its working for other scenarios.
2. I checked Adapter Specific attributes in Business service and given Partner number which in maintained in WE20 for the partner in R/3.
3. Refreshed cache.
But still... its showing the below error.
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:P1>BS_PARTNER</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert the sender service BS_PARTNER to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Any idea what might be wrong?
Regards
Deepthi.

Hi Experts,
Could you please help me to fix this.
SCENARIO: SAP - IDOC -
> XI -
> SOAP Adapter (Webservice)
Workaround:
1. Verified Adapter Specific configurations and its fine with same Logical system in SLD and ALE service.
2. Header mapping in Receiver com channel : Sender service and Receiver Service is assigned
3. Identifier Tab in comm channel details: Its empty - no values.
SXMB_MONI :
Error Details:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_INV_SND_SERV</SAP:Code>
<SAP:P1>CAPTOR3_PRU</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unable to convert sender service X12345X to an ALE logical system</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks in Advance,
Sunil.

Unable to convert the sender service ABC_Service to an ALE logical system

Hi,
I have a JMS (Party) --> PI --> IDOC scenario.
Party: ABC_Party
Service: ABC_Service
I am getting the error Unable to convert the sender service ABC_Service to an ALE logical system when I test the scenario using RWB -> Component Monitoring -> Integration Engine -> Test Message.
I have already done the below settings:
1) Defined Header Mapping in Receiver Agreement for IDOC (Sender Party, Sender Service and even Receiver Service are specified)
2) Business Component (ABC_Service) -> Adapter Specific Identifiers -> mentioned details for SAP (IDOC) system.
The scenario works perfectly fine for a party-less communication JMS -> PI -> IDOC
Have already seen:
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/rajeshkumar.pasupula/blog/2009/03/16/unable-to-convert-the-sender-service-to-an-ale-logical-system
Thank you,
Pankaj.

You need to create party if its a B2B scenario
Under Identifiers
under agency select any standard agency , scheme name will automatical;ly get populated and name you can give manually as sender name
Please refer this for more details
http://help.sap.com/saphelp_nwpi71/helpdata/en/b9/64663c7a6c2545ae292fb26d8c33c4/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/81/104bb1fbab254c8644877c7f856bbf/content.htm
Re: Party Configuration
In case of cross company process it is required
Regards
Ninad
Edited by: Ninad Sane on Nov 18, 2010 11:17 AM

Unable to convert the sender service to an ALE logical system... Urgent..!!

Hi,
Im DOing File to Idoc scenario.
Firstly i check LS name exist or not in BS.. then i found its not maintained.
I edited the BS and provided the required LS name.
and the same has been tested in ID
Business System -> Service -> Adapter Specific Identifiers .
Now i got logical system name in "Adapter Specific Identifiers".
Pressed Apply, save and activate the changes.
But still it is showing the same error.
1. Any idea what might have gone wrong??
2. I need to maintain the
   LS name of R/3 in XI system? and
   LS name of XI in R/3 system?
    Is it necessary?
Waiting for your answers.
Regards
Seema.
Edited by: reddy seema on Dec 27, 2007 1:37 AM

Hi Reddy,
        just mention the logical system name in the Sender Business system or Service ( click on sender business service> Service(menu)> Adapter Specific Identifiers--> specify the logical system name which you configured in R/3 WE20 ..) in R/3 side WE20 you need to configure the Inbound parameters of your Idoc ..
Here sender business system and Reciver Business system logical system names are different.. for checking just go to Services and check the adapater specific identifiers..--> then you   can find the name of logical system.. like that you need to check for both systems.. and both should be different..
try with this option..
Regards
@jay

PI 7.1Error between the sender interface and the receiver (abstract)interf.

Hi all,
I have been receiving an error in configuring the step of type receiver (BPM). More exactly I receive the following error message about the pipeline to the adapter between a third-part sender and a BPM receiver. The sender interface does not known the receiver interface.
BPE_ADAPTER">UNKNOWN_MESSAGE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>No object type found for the message. Check that the corresponding process is activated</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Any help will be well appreciated.
Many thanks in advance for your kind support.
Regards,
Giovanni

looks like message interface is not able to identify by the integration engine ,Check that the interface name and namespace of sender are coming as of expected
if not this provide more details
Rajesh

Issue with the sender file interfaces when using UTF-8 files

Hello experts,
     We are having number of File to SAP interface scenarios in our business process. In the past, we are having the files coming to us in ASCII text format. Recently, because of the business process change(to handle multiple languages like Chinese), we are getting now the same files in UTF-8 format. So, we have changed the attribute File Type in the sender communication channel from Binary to Text and used encoding format as UTF-8.
Now, when we see the processed files in PI, we are missing the Header record in the message. For example, we have the PO interface in the following format:
Identifier     Information
H     PO header information
I     PO Item information
I     PO Item information
Once the file adapter picks this format kind of file and when we see the XML message in PI, it is just having only two Items information. The header part is not coming to PI at all and the message is trying to get processed inside SAP and therefore interface is failing.
Additional observations made:
u2022     We have checked the Document Offset field value too; it is initial for the interface.
u2022     We added an empty line in the UTF-8 text file, it worked fine. But, this is not an ideal solution for us, because the system which generates these files, canu2019t handle it.
   Does any one has observed this kind of problem before? If so, can you please help me ...
Thanks,
Adithya K

Thanks for all the information. Currently i've tried to use both modules (TextCodepageConversionBean and XMLAnonymizerBean) in my Sender File Adapter, but for now without any result...
To describe the situation: i am using flatfiles which i am fetched from the file system (NFS) by the Sender File Adapter. To translate the characters to the XML strucutre, the File Content Conversion protocol is been used.
The content conversion defines the structure base on the first two characters on each row in the flat file. This worked fine till one of our suppliers is delivering BOM characters like "EF BB BF" in the beginning of the file.The content conversion is not able to recognize my header characters in this situation, which will normally start with "01".
Any suggestions?

Identify the Sender

Similar Messages

Maybe you are looking for