EDI / IDoc : While posting inbound IDocs, IDocs gets into status 56

EDI / IDoc : While posting inbound IDocs, IDocs gets into status 56 with message "EDI: Sender port in control record is invalid".
But if I reprocess the same idoc without doing any changes using RBDINPUT and select radio button to processs idocs for status 56, then it gets successfully posted.
So not getting why this stucks for the first time.
Thanks in Advance..........

i fixed this my self

Similar Messages

When we post Inbound Invoice IDocs, we are getting an error message "Enter a tax jurisdiction code".

Hi Experts,
When we post Inbound Invoice IDocs, we are getting an error message "Enter a tax jurisdiction code". As checked, we have configured OBCD and OBCA for the vendor and we are passing the Tax Jurisdiction code in E1EDP04 SAL segment. Can anybody give us some idea to resolve this issue.
Regards,
Sameek

Hi Sameek,
Please refer the below link. Hope it helps.
http://scn.sap.com/thread/1435286
Regards,
Chandan.

While posting f-53 i getting error missing table T043G

Hi
while posting F-53 i getting error "company code" is Missing table T043G.
What can i do for this.. can u advise this.
Thank u
anil

hi anil,
you are not given the tolerance group for customers/vendors, give the tolerance group for the same and try it.
also give the gl tolerance,
try t.codes oba0, oba3
pls award points.
Raghav

Error while posting Inbound Delivery

I am trying to post inbound delivery and getting error that there is no item avaialble on the Purchase order. Please help.
Thanks in advance.

Hi,
Check Confirmation Control Key of resp. purchase order.
Also check for the said inbound delivery, have you created shipment for this?
If no, create with respect to Inbound delivery using transaction VT01N and then do GR agianst Inbound delivery.
Please check and revert.
Thanks
Hrishi
Edited by: Hrishi on May 30, 2011 10:53 AM

Error while posting the CREMAS03 Idoc

Hi
I a getting the Error while posting CREMAS03 idoc from File
The ERROR: Status 65 ,Error in ALE Servics: Cross Company code does not exits..
but when i cheked with the functional guys , the comany code exits..
Any one have any idea
SV

Hey,
    seems you have given wrong enteries for logical system in sale or in WE20(patrner profile)
Steps for ALE settings:-
Steps for XI
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the R3 system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto IDX1.
     Create a new port.
     Give the port name.
     Give the client number for the R3 system.
     Select the created Rfc Destination.
Step 3)
     Goto IDX2
     Create a new Meta data.
     Give the Idoc type.
     Select the created port.
Steps for R3.
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the XI system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto WE21.
     Create a port under transactional RFC.(R3->XI)
     Designate the RFC destination created in prev step.
Step 3)
     Goto SALE.
     Basic settings->Logical Systems->Define logical system.
     Create two logical systems(one for XI and the other for R3)
     Basic settings->Logical Systems->Assign logical system.
     Assign the R3 logical system to respective client.
Step 4)
     Goto WE20.
     Partner type LS.
     Create two partner profile(one for XI the other for R3).
     Give the outbound or inbound message type based on the direction.
Step 5)
     Goto WE19
     Give the basic type and execute.
     fill in the required fields.
     Goto IDOC->edit control records.
     Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
     Click outbound processing.
Step 6)
     Go to SM58
     if there are any messages then there is some error in execution.
     Goto WE02.
     Check the status of the IDOC.
     Goto WE47.
     TO decode the status code.
Step 7)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.

'Purchasing document does not exist' error while testing Inbound PO Idoc

Hi experts,
i am working on Inbound PO Idoc scenario. I am testing Idoc in WE19 with ORDRSP mesage type.
Idoc type:ORDERS05
Process code:ORDR
FM:IDOC_INPUT_ORDRSP
while trying to create PO it is giving an error 'Purchasing document does not exist' in we05.
please suggest me how to resolve this???
Regards,
Bhuvan.

Hi,
first time i am testing this IDoc and i don't find any field in Idoc structure to provide purchase order value.
any more inputs plz??
regards,
bhuvan.

Error while posting Inbound Idocs-"EDI: Partner profile not available"

Hi,
I am getting the error "EDI: Partner profile not available" Status -56 while creating inboud Idocs.
I have done the following steps so far
1.Created IDOC basic Type and Message Type. (Custom)
2. Created process code to process the IDOC.
3. Use the FM IDOC_INBOUND_WRITE_TO_DB to create the inbound IDOC.
4. Use the FM IDOC_START_INBOUND to process the IDOC.
Is ther anything else that i have to do inorder to post the idoc sucessfully.
Thanks in advance
-Nishant
Edited by: nishant patel on Nov 13, 2009 10:35 AM
Edited by: nishant patel on Nov 13, 2009 10:41 AM

Hi,
Check in WE20 if the partner profile is configured for the idoc type and the message type. That might be the cause of the error.
Also make sure the same partner profile details are sent to the control record. Partner profile details are stored in the table EDP13.
Hope this helps
Regards
Shiva

B1358 error while posting inbound idoc with a FM

Hi
We are trying to post and inbound IDOC with the help of an rfc and eventually creating an invoice from a bdc wrapped in the RFC
The idocs are successfully pushed to R/3 while they are not getting posted and the error code in we02 is as follows
No status record was passed to ALE by the application
Message no. B1358
Diagnosis
The application failed to return a status record to the ALE layer after the IDoc was processed.
This is due to an error in the application function module which processed the inbound IDoc.
Procedure
If you wrote the application function module yourself, you need to change the program.
If the function module in question is a standard application function module, you should consult SAP.
Note: we are using a custom function module
regards
krishna

Hi Krishna,
I assume that your function module processing the IDOC does not follow the ALE/IDOC processing rules.
Please check out the programming guidelines in the SAP Online Help under:
<a href="http://help.sap.com/saphelp_nw70/helpdata/en/78/21758051ce11d189570000e829fbbd/frameset.htm">http://help.sap.com/saphelp_nw70/helpdata/en/78/21758051ce11d189570000e829fbbd/frameset.htm</a>
Important are the parameters and tables that need to be returned, containing the correct IDOC processing status. Please take the IDOC processing quite serious in regards to complete Logical Unit of Works.
Best regards,
SIlvia

Message No.00088 while posting Inbound Sales Order Idoc.

Hello Experts,
I am working on Inbound Interface i.e inbound sales order via Biz talk. When BizTalk send one file contains all sales order related data .
When it comes to SAP, the Net price for PRICE condition type, getting an error message
Input must be in the format ___,___,__~.__V
Message no. 00088
Diagnosis
Your entry does not match the specified input format.
System Response
The entry in this field was rejected.
I already checked my User settings everything is ok. When I am manually putting it like 122.32 its working but when its came by file thru inbound interface I am getting the above error.
The Net price field is KOMV-KBETR.
Please help me out.
Waiting for your suggestions.
Thanks in Advance.
Dev

Thanks for your reply.
Already check that thread & settings.
Still the error is there.
Manually its working only when data receive tru IDOC sysytem is throwing same error.

How to get Get IDOC Number for Inbound IDOCS

Hi,
I am using the FM -- IDOC_INPUT_HRMD for creating Inbound IDOCS.
I populate the values for Control Record and Data Record and the IDOC is posted successfully and i get the status 53 in the status Table.
But the problem is the field for IDOC number(DOCNUM in IDOC_STATUS Table of the FM ) is empty.
How can i get the DOCNUM for the IDOC posted as a result of this FM ?
regards,
Siddhartha

Hi Siddhartha,
I think you cannot call IDOC_INPUT_HRMD fm directly from the external program as this fm only handles the application logic part and not the idoc number generation and save part.
So I think you have to call IDOC_INBOUND_SINGLE from your external program and then get the IDOC number.
Then if you need the status records then you need to call another fm and feed IDOC number that you have got from IDOC_INBOUND_SINGLE (there is one IDOC_READ_COMPLETELY but it is not a remote enabled fm)
<b>OK, I just found one RFC enabled fm which you can use,
<b>EDI_DOCUMENT_READ_ALL_STATUS</b></b>
Hope this helps..
Sri
Message was edited by: Srikanth Pinnamaneni

Error 'No tax code found for difference' in Posting Vendor Invoice IDOC

Hi All,
I am getting error message 'No tax code found for difference' while posting Vendor Invoice IDOC into SAP. IDOC type is INVOIC02. There is no difference in PO price, Invoice price and even Standard price. then why this error message? Other Vendor EDI settings are done ( OBCA, OBCD, OBCE etc). Is there any thing specific to be done in the config for this error?
IDOC has PO as reference document.
I looked into several threads in SDN forum but could not find proper solution
Can any ine help me with this issue?
Thanks in advance
Hari

Hi
You might be missing the tax code for uploding through IDOC
so you can use the t.code we02 and give the doc and find the error
go to the WE19 to edit the tax code
and USE the t.code BD87 to select the doc and process it
thanks
Madhu

Example program - posting accounting document, Idoc ( ACC_DOCUMENT )

Hi fellows developers,
here is an example of usage of the IDOC, directly in program for an accounting document
(ALE message type ACC_DOCUMENT, bapi BAPI_ACC_DOCUMENT_POST )).
It was inspired by the lack of a flexible usage of this IDOC in LSMW
(f.e. booking of Gl and Vendor from the same file).
Both cases inbound and outbound are covered, although the outbound idoc was delivered in state
for furthere dispatching and was further not tested.
You can adapt this example to any idoc type (bapi type) and load data from anywhere ( file, table, etc.).
If you have question please ask.
On my system works !!!:)))
I hope it will help you in your daily work.
Regards,
Miroslaw
*& Report Z_MKPR87
*& Version 1.0 - creates idoc for accounting document with status
*& 64 - inbound and 30 - outbound.
*& Then you need to execute program RBDAPP01 for this message type (inbound),
*& for outbound further dispatching with appropriate tool is required (not tested here).
*& For inbound, complete booking of document was tested. For outbound
*& only to the stage 30 - 'Idoc ready for dispatch'.
*& Program does not require any additional DDIC objects.
*& The solution gives you possibility for example to book document G/L + Vendor items,
*& strictly speaking the whole power of this bapi in IDOC can be used. Unfortunately
*& in LSMW its not the case.:)
*& Data for idoc is takken from internal table, but can be loaded from anywhere.
REPORT Z_MKPR87.
INCLUDE Z_MKPPR87_TOP.
INCLUDE Z_MKPPR87_SEL.
INCLUDE Z_MKPPR87_EVN.
INCLUDE Z_MKPPR87_IDOC.
*& Include           Z_MKPPR87_TOP
CONSTANTS:
input structure for idoc ***
Achtung! don't use BAPI input structures
they are similar but not flat ( the casting cannot occure, since idoc
needs flat data - see 'sdata' field in edidd )
gc_idoc_structure1(27) TYPE c VALUE 'E1BPACHE09',
gc_idoc_structure2(27) TYPE c VALUE 'E1BPACGL09',
gc_idoc_structure3(27) TYPE c VALUE 'E1BPACCR09'.
Structrures for IDOC : ALE message type - ACC_DOCUMENT
                     BAPI - BAPI_ACC_DOCUMENT_POST
NOTE! The E1BPXXXXXX structures are flat (char type), opposite to
BAPI structures (BAPIACHE09. etc. )
DATA:      gs_DOCUMENTHEADER TYPE E1BPACHE09,
                gt_ACCOUNTGL TYPE TABLE OF E1BPACGL09,
           gt_CURRENCYAMOUNT TYPE TABLE OF E1BPACCR09,
            gt_idoc_str_names TYPE TABLE OF char15,
                 gs_edidc     LIKE edidc,
           gt_idoc_data TYPE TABLE OF       edidd,
           gt_comm_idoc_control TYPE TABLE OF edidc.
*& Include           Z_MKPPR87_SEL
SELECTION-SCREEN BEGIN OF BLOCK bk2 WITH FRAME TITLE text-002.
PARAMETERS:
          p_itype TYPE char15 DEFAULT 'ACC_DOCUMENT03',
*'CREMAS04',
          p_mtype TYPE EDIDC-mestyp DEFAULT 'ACC_DOCUMENT',
          p_rport TYPE EDIDC-rcvpor DEFAULT 'LSMW',
          p_rtype TYPE EDIDC-rcvprt DEFAULT 'US',
          p_rname TYPE EDIDC-rcvprn DEFAULT 'Z_MKARAS',
          p_inbd    TYPE c DEFAULT 'X'. " C - inbound (2), space - outbound (1)
SELECTION-SCREEN END OF BLOCK bk2.
*& Include           Z_MKPPR87_EVN
INITIALIZATION.
PERFORM initialize_idoc_const.
START-OF-SELECTION.
PERFORM create_idoc.
*& Include           Z_MKPPR87_IDOC
*&      Form create_idoc
      text
FORM create_idoc.
PERFORM set_bussines_data
              USING
                 gs_documentheader
                 gt_accountgl
                 gt_currencyamount.
PERFORM build_idoc_from_bus_dat
              USING
                 gs_documentheader
                 gt_accountgl
                 gt_currencyamount
              CHANGING
                 gt_idoc_data.
CASE p_inbd.
WHEN 'X'.
   PERFORM create_inbound_idoc.
WHEN space.
   PERFORM create_outbound_idoc.
ENDCASE.
ENDFORM.                    "create_idoc
*&      Form create_inbound_idoc
      text
FORM create_inbound_idoc.
PERFORM set_idoc_control_inbound CHANGING gs_edidc.
CALL FUNCTION 'IDOC_WRITE_AND_START_INBOUND'
    EXPORTING
      i_edidc = gs_edidc
    TABLES
      i_edidd = gt_idoc_data.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ELSE.
   MESSAGE 'Inbound idoc(s) created, check in TAC WE02' TYPE 'I'.
ENDIF.
ENDFORM.                    "create_inbound_idoc
*&      Form create_outbound_idoc
      text
FORM create_outbound_idoc.
PERFORM set_idoc_control_outbound   CHANGING   gs_edidc.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
    EXPORTING
      master_idoc_control        = gs_edidc
    TABLES
      communication_idoc_control = gt_comm_idoc_control
      master_idoc_data           = gt_idoc_data.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ELSE.
   MESSAGE 'Outbound idoc(s) created, check in TAC WE02' TYPE 'I'.
ENDIF.
ENDFORM.                    "create_outbound_idoc
*&      Form set_idoc_control_inbound
      text
     -->CT_EDIDC   text
FORM set_idoc_control_inbound CHANGING cs_edidc LIKE gs_edidc.
DATA: ls_edidc TYPE edidc.
cs_edidc-direct = '2'.
cs_edidc-idoctp = p_itype.
cs_edidc-mestyp = p_mtype.
cs_edidc-rcvpor = 'SAPECI'.
cs_edidc-rcvprt = p_rtype.
cs_edidc-rcvprn = p_rname.
cs_edidc-sndpor = p_rport.
cs_edidc-sndprt = p_rtype.
cs_edidc-sndprn = p_rname.
cs_edidc-credat = sy-datum.
cs_edidc-cretim = sy-uzeit.
ENDFORM.                    "set_idoc_control
*&      Form set_idoc_control_outbound
      text
     -->CS_EDIDC   text
FORM set_idoc_control_outbound CHANGING cs_edidc LIKE gs_edidc.
DATA: ls_edidc TYPE edidc.
cs_edidc-direct = '1'.
cs_edidc-idoctp = p_itype.
cs_edidc-mestyp = p_mtype.
cs_edidc-rcvpor = p_rport.
cs_edidc-rcvprt = p_rtype.
cs_edidc-rcvprn = p_rname.
cs_edidc-sndpor = 'SAPECI'.
cs_edidc-sndprt = p_rtype.
cs_edidc-sndprn = p_rname.
cs_edidc-credat = sy-datum.
cs_edidc-cretim = sy-uzeit.
ENDFORM.                    "set_idoc_control_outbound
*&      Form set_bussines_data
      text
     -->CS_DOCUMENTHEADER text
     -->CT_ACCOUNTGL       text
     -->CT_CURRENCYAMOUNT text
FORM set_bussines_data USING cs_documentheader LIKE gs_documentheader
                             ct_accountgl      LIKE gt_accountgl
                             ct_currencyamount LIKE gt_currencyamount.
                        CHANGING ct_idoc_data LIKE edidd.
DATA:
         ls_documentheader TYPE e1bpache09,
         ls_accountgl      LIKE LINE OF gt_accountgl,
         ls_currencyamount LIKE LINE OF gt_currencyamount.
HEADER **
cs_documentheader-bus_act = 'RFBU'.
cs_documentheader-username = 'RNOWAK'.
cs_documentheader-comp_code = '1000'.
cs_documentheader-doc_date = '20071205'.
cs_documentheader-pstng_date = '20071205'.
cs_documentheader-fisc_year = '2007'.
cs_documentheader-fis_period = '12'.
cs_documentheader-doc_type = 'JE'.
POSITIONS ***
111111111 ****
ls_accountgl-itemno_acc = '0000000001'.
ls_accountgl-gl_account = '0000473110'.
ls_accountgl-item_text = 'MIK test dokumentu GL z programu IUE'.
ls_accountgl-comp_code = '1000'.
ls_accountgl-tax_code = '0I'.
ls_accountgl-costcenter = '0000001000'.
ls_currencyamount-itemno_acc = '0000000001'.
ls_currencyamount-currency = 'PLN'.
ls_currencyamount-amt_doccur = '496'.
APPEND ls_accountgl TO ct_accountgl.
APPEND ls_currencyamount TO ct_currencyamount.
2222222222 ****
ls_accountgl-itemno_acc = '0000000002'.
ls_accountgl-gl_account = '0000113302'.
ls_accountgl-item_text = 'MIK test dokumentu GL z programu IUE'.
ls_accountgl-comp_code = '1000'.
ls_accountgl-tax_code = ''.
ls_accountgl-costcenter = ''.
ls_currencyamount-itemno_acc = '0000000002'.
ls_currencyamount-currency = 'PLN'.
ls_currencyamount-amt_doccur = '-496'.
APPEND ls_accountgl TO ct_accountgl.
APPEND ls_currencyamount TO ct_currencyamount.
ENDFORM.                    "set_bussines_data
*&      Form build_idoc_from_bus_dat
      text
     -->IS_DOCUMENTHEADER text
     -->IT_ACCOUNTGL       text
     -->IT_CURRENCYAMOUNT text
     -->CT_IDOC_DATA       text
FORM build_idoc_from_bus_dat USING is_documentheader LIKE gs_documentheader
                                        it_accountgl LIKE gt_accountgl
                                   it_currencyamount LIKE gt_currencyamount
                               CHANGING ct_idoc_data LIKE gt_idoc_data.
DATA:
ls_documentheader LIKE is_documentheader,
ls_accountgl     LIKE LINE OF it_accountgl ,
ls_currencyamount LIKE LINE OF it_currencyamount,
ls_idoc_data LIKE LINE OF ct_idoc_data.
Document header *****
ls_documentheader = is_documentheader.
ls_idoc_data-segnam = gc_idoc_structure1.
ls_idoc_data-sdata = ls_documentheader.
APPEND ls_idoc_data TO ct_idoc_data.
Positions G/L part ************
LOOP AT it_accountgl INTO ls_accountgl.
    ls_idoc_data-segnam = gc_idoc_structure2.
    ls_idoc_data-sdata = ls_accountgl.
    APPEND ls_idoc_data TO ct_idoc_data.
ENDLOOP.
Currency Items part ******
LOOP AT it_currencyamount INTO ls_currencyamount.
    ls_idoc_data-segnam = gc_idoc_structure3.
    ls_idoc_data-sdata = ls_currencyamount.
    APPEND ls_idoc_data TO ct_idoc_data.
ENDLOOP.
ENDFORM.                    "build_idoc_from_bus_dat
*&      Form initialize_idoc_const
      text
FORM initialize_idoc_const.
APPEND gc_idoc_structure1 TO gt_idoc_str_names.
APPEND gc_idoc_structure2 TO gt_idoc_str_names.
APPEND gc_idoc_structure3 TO gt_idoc_str_names.
ENDFORM.                    "initialize_idoc_const

I summarized postings and posted again into the same system. Yes, you can save an IDOC in your own system...There's an IDOC FM that will do just that... In my case, I did:
after receipt of IDOC and posting,
process the idoc tables, rebuilding the input into tables.
Summarize the tables, as needed.
Create a new IDOC with a specific function code.
Save the IDOC in my own system, using IDOC_INBOUND_ASYNCHRONOUS, as I recall.
I had a custom process code that fired off the standard FM to process the JE posting. I don't remember all the variables, but I have this stored as my example:
DATA : p_sndprn TYPE edi_sndpn3.
* Control Record Build.
CALL FUNCTION 'OWN_LOGICAL_SYSTEM_GET'
    IMPORTING
      own_logical_system = p_sndprn
    EXCEPTIONS
      OTHERS             = 0.
iedidc-direct   = '2'.
iedidc-idoctyp = 'FIDCCP02'.
iedidc-mestyp   = 'FIDCC2'.
iedidc-mesfct   = 'ACC'. <customer made up....used to control which process codes fire off when for standard message.
iedidc-sndprt   = 'LS'.
iedidc-sndprn   =   p_sndprn.
iedidc-rcvprn   =   wa-rcvprn.
iedidc-rcvprt   = 'LS'.
iedidc-sndpor   = 'SAP_EDI_SC'.
iedidc-credat   = sy-datum.
iedidc-cretim   = sy-uzeit.
APPEND iedidc.
* IDOC store routine...must commit work
* to get IDOC transferred to the IDOC processor.
CALL FUNCTION 'IDOC_INBOUND_ASYNCHRONOUS'
    TABLES
      idoc_control_rec_40 = iedidc
      idoc_data_rec_40    = iedidd.
ENDFORM.                    " send_idoc
Edited by: DaveL on Oct 25, 2011 8:15 PM

IDOC On mass Inbound

Hi All,
During the last weekend when we posted idocs on mass inbound, we got error 'No status record was passed to ALE by the application'.
Regards
Seth

Hi,
Try to check the function module of the IDOC and see whether it gives record status or not (meaning error handling is exist when error or success happened). The issue might be there.
Regards,
Teddy

Is padding required while posting to SAP

Hi
Is padding really required for a number(ex: if a field has max length is 10, can it have only 3 out of it and left others) or string(ex: if a field has max length is 10 char, can it have only 4 out of it and left others)while posting as an IDoc to SAP from XI.
Can anybody please advise...
Kr
Ramesh

Hi ramesh.
Padding with zero is required in most of the cases related to scenarios involving BAPI and IDocs in case if numeric values are being transferred.
First, check how the numeric values are stored in your database table. If their data type is charectar, then they will be left padded with zeros.
Check their representation and go ahead accordingly
Regards,
Hari

Runtime error while posting GR

This is Naresh, new to SAP-MM. While posting a GR iam getting a ABAP runtime error. Before posting Iam using check button, but no error was found. The error is MESSAGE_TYPE_X. And there is a long discription about the error like error analysis, trigger location of runtime error, source code extract etc.
Please help me. Thanks in advance.

Hi,
385830 is a note created to issue dumps rather than termination messages. This was done due to problems with data consistency in MM-IM.
If the dump comes regularly, you know how to reproduce and your ABAPers can't find the problem in debugging, don't be shy to open a message on MM-IM-GF-MB.
Regards,
Attila
PS: I second Jürgen's point regarding the amount of information.
Edited by: Attila Giber on Apr 27, 2010 11:20 AM

EDI / IDoc : While posting inbound IDocs, IDocs gets into status 56

Similar Messages

Maybe you are looking for