Edi message

How and where to create this EDI message type.
Field name : edidc-stdmes EDI message type

Hi,
Create Message Type --> WE81
Regards
Sudheer

Similar Messages

EDI Message not Transmitted for Scheduling Agreement

Hi guys!
Does anybody know what should I check to see why the EDI message for a delivery line in the scheduling agreement has not been transmitted? Would really save me
Regards,
Ileana

Hi
First check the message whether it has been processed properly or not . goto ME39 , Check the message(Shift +F1)
if the message is in red, check the processing log,
If the message is in yellow , process the same using ME9E
If the message is in grren means the Idoc's are generated.
Now got Transaction WE05 & Check the IDoc's giving the Basic type - DELFOR02
Give from & to dates based on the rpocessing date of the message.
Here check the Idoc's are in Red or green . If in red check the Message in the Status.
Thanks & Regards
Kishore

How to control the status of EDI message in delivery document

Hello:
We use user exit:EXIT_SAPLV56K_001 in function:IDOC_OUTPUT_Delivery to block the IDOC generation if delivery is blocked in GTS system.The IDOC generation can be blocked successfully by this user exit but the EDI message type will still have the status of "successfully processed" in the delivery doucment after IDOC generation is prevented.So user have to manually repeat the EDI Message type so that this EDI message type can be retriggerred by the background job of RSNAST00.
I am wondering if the EDI message in the delivery document can have the status of "not processed" even after IDOC generation is prevented.
BR
Thanks

Did you raise any exception like ERROR_MESSAGE_RECEIVED from the exit when the delivery is blocked?
The most important is the RSNASTED should get some exception to set RC = 4 (Non-zero). Only in that case, the EDI message type will go to error (i.e. VSTAT = 2) otherwise, by-default the RC = 0 unless we lead it to set to non-zero. Unless u make VSTAT = 2, you can't process it thru' RSNAST00 or better RSNAST0F for reprocessing the messages that go to error.

EDI message output for goods movements

Dear experts,
we configured NACE to send EDI messages, when goods movements are created. When we use partner type "VN" (Vendor) and leave the partner number empty, no message is created. Only if the partner number is filled, a message is created. This means, that the partner number is not extracted dynamically from the goods movement and we have to make one NACE entry for each partner. For other applications (e. g. outbound call offs), the partner number in NACE can be left empty and when a document is posted, the receiver partner number is determined dynamically.
Is it possible to modify the processing, so that the partner number is extracted from the goods movement? How can this be done?
Best regards,
David Claes

Hi,
What is the application you selecting for creating ouput?
I don't see output record condition with as combination.
You should be using ME as application area.
Thank you!
Dipak

Error in inbound processing: EDI message - XML Gateway

Hello!
I've setup a DELFOR transaction in B2B and modified XML Gateway settings for internal delivery channel in order to send the message to EBS, but I'm getting weird errors in b2b.log. (XML Gateway in EBS is not setup yet, but it should't be an issue since incoming errors are handled in EBS, and I would just see an inbound transaction with processing errors in Transaction Monitor.)
In the beginning of b2b.log I see this:
2009.07.07 at 15:26:31:897: B2BStarter thread: BusinessLogicLayer - (DEBUG) Push Stack: queryInternalDeliveryChannel
2009.07.07 at 15:26:31:897: B2BStarter thread: BusinessLogicLayer - (DEBUG) Pop Stack: queryInternalDeliveryChannel
2009.07.07 at 15:26:31:897: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:31 CEST 2009 inbound initialize
2009.07.07 at 15:26:31:897: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:31 CEST 2009 Obtaining inbound connection...
2009.07.07 at 15:26:31:897: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:31 CEST 2009 inbound connect string: jdbc:oracle:thin:@server64.xa.si:1521:test2
2009.07.07 at 15:26:31:897: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:31 CEST 2009 inbound username: apps
2009.07.07 at 15:26:32:522: B2BStarter thread: B2B - (DEBUG) : Tue Jul 07 15:26:32 CEST 2009 inbound initialize exit
2009.07.07 at 15:26:32:522: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:startListen Enter
2009.07.07 at 15:26:32:538: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:startListen Exit
2009.07.07 at 15:26:32:538: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:run Thread start
2009.07.07 at 15:26:32:538: B2BStarter thread: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:initialize Exit
2009.07.07 at 15:26:32:538: B2BStarter thread: B2B - (DEBUG) B2BStarter - B2B initialized
After I copy the edi file to the incoming directory B2B starts processing the file:
2009.07.07 at 15:30:01:878: Thread-10: B2B - (DEBUG)
Protocol = File
Version = 1.0
Transport Header
filename:00003442_23.CMS
filesize:12345
file_ext:CMS
fullpath:C:\xa_endpoint\00003442_23.CMS
timestamp:2009-07-06T16:14:29.393+01:00
As I see in the log: B2B finds the trading partner and agreement and all looks fine. But later comes this:
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination Enter
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination deliver message to destination. protocol is XMLGateway Queues
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination deliver message to XMLGW
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : Tue Jul 07 15:30:05 CEST 2009 Converting B2B message to ECX message..
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : Tue Jul 07 15:30:05 CEST 2009 Inbound - B2BtoECX - Enter
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : Tue Jul 07 15:30:05 CEST 2009 B2B Message -
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : COLLABORATION_NAME : null
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : ACTION_NAME : DELFOR
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : DOCUMENT_TYPE : DELFOR
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : DOCUMENT_TYPE_REVISION : D97A
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : SOURCE_NAME : tpartner
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : DESTINATION_NAME : Xa d.d.
2009.07.07 at 15:30:05:909: Thread-9: B2B - (DEBUG) : PAYLOAD : UNB+UNOA.............. edi message continues here
2009.07.07 at 15:30:05:925: Thread-9: B2B - (DEBUG) : PAYLOAD : <?xml version="1.0" ?><Transaction-DELFOR............... xml continues here
2009.07.07 at 15:30:05:925: Thread-9: B2B - (DEBUG) : Tue Jul 07 15:30:05 CEST 2009 ECX Message -
2009.07.07 at 15:30:05:925: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:handleAppMessageRetry Could not deliver the message; exception message is null
2009.07.07 at 15:30:05:925: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:handleAppMessageRetry No application side retry
2009.07.07 at 15:30:06:081: Thread-9: B2B - (ERROR) Error -: AIP-50903: Message "0A14011912255682A58000003257C600-1" retry count is zero
     at oracle.tip.adapter.b2b.msgproc.MessageHandler.handleAppMessageRetry(MessageHandler.java:394)
     at oracle.tip.adapter.b2b.msgproc.MessageHandler.deliverMessageToDestination(MessageHandler.java:344)
     at oracle.tip.adapter.b2b.msgproc.Request.putMsg(Request.java:657)
     at oracle.tip.adapter.b2b.msgproc.Request.continueRequest(Request.java:481)
     at oracle.tip.adapter.b2b.msgproc.Request.incomingRequest(Request.java:410)
     at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:2062)
     at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2574)
     at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2444)
     at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2399)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
     at java.lang.Thread.run(Thread.java:534)
Last message repeats once more and then:
2009.07.07 at 15:30:06:081: Thread-9: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2009.07.07 at 15:30:06:081: Thread-9: BusinessLogicLayer - (DEBUG) Push Stack: updateBusinessMessage
2009.07.07 at 15:30:06:096: Thread-9: BusinessLogicLayer - (DEBUG) Pop Stack: updateBusinessMessage
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateMsgError(3 params) Exit
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) DBContext commit: Enter
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) DBContext commit: Transaction.commit()
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) DBContext commit: Leave
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination Exit
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest Exit
2009.07.07 at 15:30:06:096: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: processIncomingMessage setting seq numbers
2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Call Incoming Request Processor
2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest Enter
2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest TransportBindings created
2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest Create a Message Table Row for Request message with message state Continue Processing
2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow Enter
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Push Stack: queryExchangeProtocolRevision
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Pop Stack: queryExchangeProtocolRevision
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:null
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Push Stack: queryDocumentProtocolRevision
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) Pop Stack: queryDocumentProtocolRevision
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (ERROR) Error -: AIP-13115: Not in an active transaction
     at oracle.tip.repos.core.persistency.BaseObject.prologue(BaseObject.java:1408)
     at oracle.tip.repos.core.persistency.BaseObject.createObject(BaseObject.java:913)
     at oracle.tip.model.instance.DataStorage.create(DataStorage.java:794)
     at oracle.tip.adapter.b2b.message.MessageStorage.create(MessageStorage.java:145)
     at oracle.tip.adapter.b2b.msgproc.DbAccess.insertMsgTblRow(DbAccess.java:953)
     at oracle.tip.adapter.b2b.msgproc.Request.incomingRequest(Request.java:397)
     at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:2062)
     at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2574)
     at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:2444)
     at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:2399)
     at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:527)
     at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:374)
     at java.lang.Thread.run(Thread.java:534)
2009.07.07 at 15:30:06:112: Thread-9: BusinessLogicLayer - (DEBUG) setRuntimeActiveandQuiescing()
2009.07.07 at 15:30:06:112: Thread-9: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage General Exception ERROR
Error repeats a few times.
Wire message stays in Processing status, Business message is errored and an exception message is created in ip_in_queue.
Both remote and host delivery channels have retry set to 1. Agreement was re-deployed + all B2B restared, but the problem remained.
Could anyone help with this? What could be wrong?
Thanks in advance.
Kind regards,
Wanda
PS. I've checked all threads that might have anything to do with this, but found nothing useful.

Hi Anuj,
thanks for taking the time to examine the file.
Answers to your questions:
1. Yes, this is the 1st time for B2B, but the EBS I'm trying to connect to is up and running for approx. 2 years (it's a test instance).
2. Patching was done by the customer's sysadmin, so I don't really have an overview on what and how he did. Result of opatch:
Installed Patch List:
=====================
1) Patch 8298731 applied on Sat Jun 13 09:23:42 CEST 2009
2) Patch 5907304 applied on Thu Jul 17 14:26:55 CEST 2008
3. In theory the sysadmin should have run it, but how could I double-check this?
I know he had problems while applying patch 8298731, but he said it was solved later. (Customer is using windows os, which is making a lot of troubles otherwise.)
Regarding IDC log there is no success. I've restared B2B at least 5 times plus once the database, but still nothing. In tip.properties:
oracle.tip.adapter.b2b.transportTrace = C:\APPS\OAS\ip\log/transport.trc
also I tried the following values:
C:\\APPS\\OAS\\ip\\log/transport.trc (since there is a similar entry: oracle.tip.LogDirectory = C:\\APPS\\OAS\\ip\\log)
C:\\\\\\\\\\\\\\\\APPS\\\\\\\\\\\\\\\\OAS\\\\\\\\\\\\\\\\ip\\\\\\\\\\\\\\\\log/transport.trc (this was commented before; maybe it comes from some default)
true (I had no other idea)
Result is the same for all the cases: b2b_idc_transport.log file is 0 bytes, but b2b_dc_transport.log has initial data+writes log when processing.
If I remove or comment the above line from tip.properties, then no transport log files are created.
I've updated the agreement to have B2B inbound for the internal delivery channel, re-deployed it and it worked fine -> transaction(s) appeared in IP_IN_QUEUE.
Changing it back to XML Gateway (and re-deploying) causes all original problems.
Regards,
Wanda

EDI Message in Seeburger adapter

Hi All,
is there any posibilities to see the signed EDI message (encrypted format) in seeburger module
please guide me the procedure
by
Boopalan

Hi Prateek Raj,
s i have done all config in Sender communication chennel & Sender Agreement
s custumer need MDN, which they can receive successfully
the same process which we did for anoterher customer its working fine
in AS2 Adapter Guid they mentioned the solution for the error Error while parsing AS2 message: AUTHENTICATION_ERROR is Check the authentication certificate settings.
but using the same certificate we can able to send & customer can able to decrypt the EDI Message
where the problem could be..?
by
boopalan

Inbound EDI Message Flow

Hi,
Am using AS2 and OFTP adapter in seeburger and want to understand the inbound flow of messages.
As I have read some blogs and searched couple of entries in SDN, I want to make sure whether my understandings are correct.
The big doubt in my mind is the starting point of an seeburger Inbound message. When an EDI Message comes into seeburger which communication channel does the following jobs
Classifier
Mapping
Splitting
And after splitting it forwards the message to the Split997 and in turn it identifies the proper sender agreement.
But am more confused on the starting point like any scenario will have a sender communication channel to pick up the seebyrger messages. Which one is it?
Can anyone explain me the configuration part alone? I have already gone through Prateek seeburger scenario and got most of the things clarified.

When an EDI Message comes into seeburger which communication channel does the following jobs
This could be any communication channel. If your partner support OFTP or As2 protocol, it would be AS2 sender or OFTP sender communciation channel. Inside these channels only, you will add the modules.
Suppose your sender side sends a simple EDI file using FTP, then you may use standard File sender adapter and add these modules to it.
Regards,
Prateek

EDI Message output gets processed for held PO

Hi All,
When I save my purchase order as a HELD PO (EKKO-MEMORY=X), EDI Message output gets processed.
Can you please provide me any inputs to disable this.
Regards
Deepak

Hi All,
Can anyone provide any inputs on this.
Regards
Deepak

EDI messages for ASN and POD - general flow

Hi,
We are looking to send an Advance Shipping Notification Idoc / EDI message to our customer as we despatach and they will send a Proof Of Delivery EDI message to us confirming receipt and quantities.
Am I right in saying that the customer MUST take our delivery item numbers and refer to them with the POD message so that we know which item they are refering to? I think they should otherwise we won't know which item they are referring to. On the other hand I cannot see customers being interested in our item numbers.
Any experience on this?
Thanks

Thanks for your reply.
You are right that the customer wants a referene number and therefore the delivery number can be used ... so when the POD comes back the delivery number will be referenced ... but my issue is with the items in the delivery
We could have items 900001, 900002 etc and each of these need to be referenced in the POD. So the custoomer woudl need to reference these which I dont think they are likely to do.
I also suspect I am wrong .. but when I try the POD IDOC with WE19 test tool I have to enter the item number .. so either the customer has to send it or we have to do some ABAP to identify the item somehow I think?
Thanks for any more thoughts

EDI Message type issue

Dear Friends,
In my current project my issue is related to EDI Message type the problem is as below
If I use output type (message type) NEU which is SAP standard and if I select this out put type (NEU) with medium EDI after saving this I can see all the data segments in Outbound Idoc.
Now the actual issue is if I use the ZNET customize output type which is the extension of NEU with medium type EDI after saving this if I check the Idoc (We02) I am not able to see few purchase orders data segments like E1EDKT1(Header Text ) and E1EDPt1(Item Text)
What could be the reasons? Is there any setting where output types and data segments are linked
Your help will be highly appreciated
With Best Regards,
Ashish Vats

Hi,
Thanks for your reply.
I have maintained all the parameters in partner profile.... I think Could not explained the issue in detail.
the issue is as below
When I select the output type ZNET in purchase order and medium EDI(Partner profile for Vendor maintained for outbound PO) after saving the same when I check the outbound IDOC generated by system in that some segments are not coming while in NEU output type all the segments are coming properly.
ZNET is the Extension of NEU .. now my question is to forum where output types are linked with segments ?so that I can compare the ZNET with NEU and findout the missing segments or could link the missing segments with ZNET
Hope I could explained you...........
Regards,
Ashish

Message type for Inbound SD EDI message : Sales Order Confirmation

Hi,
There is an EDI message coming into SAP for sales order confirmation post delivery.
The data in the Idoc should then proceed to update the system and create the delivery document.
I need a standard Message Type which when triggered, will perform the above actions.
Will ORDRSP Message type be useful here.
Thanks ,
Ankit

Hi,
Message type/Idoc type
"ORDERS / ORDERS04 --For orders
ORDCHG / ORDERS04 -Order change
ORDRSP / ORDERS04 --PO
DESADV / DELVRY02 --Deivery
INVOIC / INVOIC02"-Invoice
Thanx,
Pramod

How to Archive Outbound edi messages in Payload?

hello,
I am doing Idoc to EDI File scenario using "localejbs/GenericConverterModule" module in receiver Channel, How to archive the EDI file when I do monitoring this outbound EDI file should be apprear in Monitoring when I click the message. How to achive this?
Means; In Message ->monitoring If i select that message , In "Payload" tab I am getting the IDOC, and XML-Edi message, I want to see the EDI message also there. Can be possible? how to get that?

Hi Khaja,
You can check with "Adapter module MessageLoggerBean in a receiver communication channel" that may help you on this:
Please refer following blog for more information
http://scn.sap.com/community/pi-and-soa-middleware/blog/2012/11/06/message-staging-and-logging-options-in-advanced-adapter-engine-of-pi-73x
Regards
GB

EDI message to IDOC mapping

hi
is there a place where i can find mapping of EDI messages to that of SAP IDOC message types?
~Suresh

Hi Suresh,
EDI subsystem will convert the IDOC into flat file (X12, EDIFACT, ODETTE, VDA etc) or flat file into IDOC. At the EDI subsytem the there will be field mapping instructions design will be there which maps the idoc to flat file. So its EDI subsystem which will be used identify the idoc msg types. Which subsystem u are using.
Regards
kannaiah

Edi messages

what are the different edi messages that are widely used ?? Whether seeburger adapter is suitable for all edi messages or we got to use different edi adapters for each message type ??
thanks
kumar

Hi,
>>>the different edi messages that are widely used ??
in logistics area:
delivery documents, sales orders/purachse orders
invoices
>>>Whether seeburger adapter is suitable for all edi messages
it all depends on your country EDI provider
in somecountries you need to use old technologies
like VAN networks and EDI messages
in some you can use SOAP and XML edi messages (so no need to any seeburger)
Regards,
michal

Non-EDI messages via AS2 Communication Channel

Hi,
We have many EDI interfaces running via AS2 communication channel provided by Seeburger.
I was wondering whether AS2 should only be used for EDI message or any other normal XML formats also.
If AS2 can be used for other formats also, what is the difference then sending the request via AS2 rather than HTTP.
Since AS2 is using HTTP transport protocol, I could rather use HTTP communication channel itself.
Let me know the differences please!

I was wondering whether AS2 should only be used for EDI message or any other normal XML formats also.
As far as I know, it is not restricted, I used AS2 protocol to transfer flat files in my last project
If AS2 can be used for other formats also, what is the difference then sending the request via AS2 rather than HTTP.
AS2 has more features than plain HTTP, like support MDN message, which allow sender to know the status of receipt immediatly.
AS2 can be used as Aync or Sync.
It can keep file name which is useful in some integration with financial institutes.
Receipts of the file can not deny their receipts of the messages (NonRupdiation)
Since AS2 is using HTTP transport protocol, I could rather use HTTP communication channel itself
Yes, you could, but you might loss the feature that AS2 protocol provides, and some trading partner only ask for AS2 protocol for the transmission of the files.
Regards
Liang

Map EDI messages to SAP iDocs

Hi all,
Is is possible to map EDI messages to SAP iDocs using Oracle Integration?
Thanks

Yes, OracleAS Integration has several components. One is called Integration B2B, which allow you to send and receive EDI messages. You can then pass this on either using Integration InterConnect or BPEL Process Manager to the SAP adapter which can talk to SAP systems using e.g. iDocs.

Edi message

Similar Messages

Maybe you are looking for