Sales document - std variant - screen variant -sales order ?

Dear SD experts,
We have assigned a variant in sales document type through VOV8, which is doing the job of WBS element mandatory field at account assignment level while creating sales order thru VA01.
Now I have requirement that the item level WBS element also mandatory field while creating sales order thru VA01 in addition to above head level.
For this I have modified the the Variant thru SHD0 and made the Item level mandatory, but this modification is being affected to all the line items, which are not being filled with data, so if I have to use one line item, the rest of line items have WBS element as mandatory and it is not allowing the order to save.
Kindly suggest solution how to ensure that the line item which is being filled is only applicable the said WBS element mandatory.
Please help.
Thanx in advance
Regards
Srihari

hi
yes, this is one we are using as of now. but still we want if anything else thru SHDO transaction.
suggested solution, can save the sales order if user not gone to the edit incompletion log or ignored. this needs lot of user discipline unlike the mandatory field.
thanx once again,
regards
srihari

Similar Messages

Transport a display variant ( screen variant )

Hi,
I have copied a standard display variant (screen variant to choose the fields on output) to Z variant with some more fields added into it.
I need to tranport this Zvariant to the production system
Can any one help to how do i insert this variant into the tranport.
thanks
Sandhya

the program RSTRANSP is to be run for transportin variants.
plz chk this link:
Re: Transporting Screen variants

0DOC_CATEGR-Sales Document Category of Reference Doc. in Order Header

Hi,
I am extracting the standard datasource for Sales Order Header 2Lis_11_VAHDR to BW.I am getting error while loading data.I checked it in PSA there are around 30 records which were showing the error with the message
"Record 985 :Contents M from field VGTYP_AK(mapped to 0DOC_CATEGR) cannot be converted in type DEC ->longtext RSAR 198" and
"Error in an arithmetic operation in record 985 RSAR117".
I am not getting this error while loading the Order Item Data.
'M' is the Document Category of Reference Doc. in Order Header.For sales document type "RE".
In R/3 the reference was taken on Inv.No instead of Order number and also there is a User Exit written on MV45AFZZ program to check the referred quantities and also zero quantiity lines in case of back split.
As there is no customization done in BW and the only customization was in terms of an User Exit in R/3 please let me know what is the reason of this error.
Thanks in advance.
Venkat

Hi Venkat,
Assume the data mapping in transfer rule and update rule is correct
Maybe you can check the info object definition of 0DOC_CATEGR in your system. Based on the error message you mentioned below, it looks like 'data type' of the object concerned is NUMC? In our system it is CHAR (standard BC)...
Regards,
Lilly

Sales document type restriction to create sales order

Hi Frinds,
My client has one requirement ...they have different sales document type. For sales document type free of charge delivery they want only some authorised person should be able to create sales order. Is it possible to set the authorisation to create sales order according to sales document type.
Regards
SV

Yes,
As already suggested, it is very well possible to restrict the user for the use of certain sales document type from basis.
& to add to the above,
Create Z* table with Sales Org + Doc type = UserID.
call this table in VA01 transaction & write piece of coding , if current USerID have entry in this table with the said combination - should not allow to proceed further.
without any basis involvement also you can ahieve your requirement.
Note: Sales Org is used for validation purpose only.
Regards,
Reazuddin MD

Transaction variant/Screen variant (SHDO)

Hello guys,
   Actually as far as i know, if we want to put default values for certain field in any transaction, than we can do it by SHDO.Am i right?
   Actually for production order header, i want to maintain certain default values for couple of fields.Through enhancement (PPCO0006) we can do it.But one of my friend told me that its even possible by SHDO.
So could u guys plz help me in doing this?I dont know the procedure.
In CO01 Screen, i want to maintain default values for following fields,
Plant- 1009
Order type- ZPP01.
                             Thanking you guys for all the help you provided.

You can use transaction SHD0 to create transaction variant. The transaction variant can be assigned to user.
Please look into the below process.
Creating the Transaction Variant
Choose Create to create a variant.
The system calls the application transaction that you want to create a variant for. Enter the values you want to use in the in the input fields. Each time an action is completed, a Dialog Box, appears listing the fields of the current screen with their current values. The kind of dialog box called depends on the kind of screen currently being processed (see Requirements).
Here you can determine:
if you want to save the field values you have inserted on the current screen (the "Adopt field values" checkbox)
if you want to hide the entire screen (the "Do not display screen" checkbox). This is only possible if settings are copied to your variant ("Adopt field values")
if field contents are saved (the "With contents" checkbox)
if the ready for input status of specific fields should be revoked (the "Output only" checkbox)
if specific fields should be hidden (the "Invisible" checkbox)
if specific fields should be mandatory the "Mandatory" checkbox)
You may or may not be able to select each of these checkboxes for every field depending on the field's type (--> Requirements).
Screen variants are created automatically for each screen where values have been saved (adopted). Enter screen variant names in the "Name of screen variant" field. These names must be unique. If the system is able to find a unique name for a screen variant it is automatically inserted into this field. The convention reads like so: (< name_of_transaction_variant>_(<client>)_<screen_number>).
Choose the function Continue to proceed. The following pushbuttons are available:
The Cancel function displays the current application transaction screen again. Here you can make changes to your settings.
The Menu functions function displays an additional dialog box wher you can deactivate menu functions.
The GuiXT function allows the user to edit a GuiXT script for the current screen (--> GuiXT).
The Exit and Save function exits and saves the application transaction. A list appears containing all of the screens in the application transaction that you want to save entries for (that is, all screens for which screen variants will be created).
Enter a short text for your transaction variant here.
Display settings can be changed as needed from this list in the future. Settings that require information at application transaction runtime (field values, table control columns) cannot be changed from this list.
Choose "Save". The system saves your transaction variant and the corresponding screen variants. The Workbench Organizer dialog box is displayed for the transaction variant and for each screen variant. Use it to assign each of these objects to a package.
You can also branch to this list using the Change values function during the function selection process.
Apart from this there is alternative to use role/parameter-id's and assign to the user. In this case, whenever the user logins in all the cases same values would be populated on to the CO01 screen. This is easily done by the basis consultant.
Thanks,
Srinivas Karri

Updating Sales document with new sub sequent sales document

Hello All,
I am creating one sales contract from one sales document through some user exits and batch jobs.
After creating this new sales contract i want to update this doc number in Old Referenced sales document flow.
Is there any standard function module for this.. i tried some function modules containing FLOW..But no use..
Thanks&Regards,
Krishna.

It is resolved..
as I am using FM SD_SALESDOCUMENT_CREATE to create this contract i just updated the Reference document number in header structure...

Change the order type for a sales document already created

Hi gurus,
please let me know if there is any possibility for changing the order type for sales document (sales order) already created,
thank you

Hi,
Rambabu is correct. Check the alternate sales document types which your current sales document type is having in VOV8 transaction. You can have the current sales document type replaced with the assigned alternate sales document type 1 or alternate sales document type 2 during run time in the during creation or change mode subject to the current sales order is not having any subsequent document. Re-pricing will happen accordingly and all the things of order will get redetermined.
Hope this explains.

Screen Variant

Dear friends,
what is transaction Variant/ Screen Variant/Gui XT pls explain step by step
Thanking you
Regards
Reddy
[email protected]

Hi Reddy,
Transaction Variant:
Transaction variants are client independent. That means that in order to transport them you are creating a workbench request. Client independent means that the moment you save your changes, they will appear in every client on the same box. If for instance you have 3 development clients, by creating a transaction variant you will be able to see it in all 3 clients. You won't need to use transaction SCC1 to transport your changes to the other development clients.
Say for an example you need to deactivate (output only) the pricing date and material pricing group field in VA01/2.
You can use the T.code SHD0, choose your transaction variant here, further choose your screen variant.
Next select your screen variant and in the Menu bar select Variant> change with processing>Make repairs in foreign namespaces only if they are urgent> Continue(Enter)>again 'enter'>Object can only be created in SAP package>continue(enter)> Exit and save >This variant contains other screens, adopt these as well?>enter>enter> scroll down to the entry 'pricing date' or VBKD-PRSDT make the necessary changes and save.
The system will prompt to assign a package and request enter the necessary values.
Crux:- you just make fields as display, or 'supress', knowing your requirements
Transaction Variants to make fields Mandatory, Hidden or Display. Also applicable to screens and tabstrips.
You can hide unwanted screens and fields in any of the standard SAP programs without changing any of the standard programs. Additional features such as making the variant as default on the standard SAP transaction code is only available as of 4.6x.
Transaction SHD0 - Create a variant for the required transaction by changing the layout through hiding fields and screens.
Transaction SE93 - Create a variant transaction (e.g. for VA02 = ZVA02).
o Next allocate the transaction variant to this variant transaction.
In 4.6c, you can default your transaction variant as the standard variant. (SHD0 - Edit -> Activate/Deactivate as standard variant)
One more feature available, instead of creating a new T.Code...you can simply assign the Transaction Variant in the Sales Document Type in T.Code-->VOV8.
Hope this Clarifies your Doubt and Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula

Re : Removing mandt field of sales document in LV01N

Hi
I want to remove mandt field of sales document in delivery screen(vl01n).
How to do this.
Thanks
Anto

Dear Antony,
To do so, You need to create a Screen Variant for T. Code: VL01N in T. Code: SHD0.
Best Regards,
Amit

Controling Sales Document

Hai Experts,
Can u plz let me know in wat ways Sales document type, schedule line category and item category controls the sales documents. Its given tat these 3 wil control sales document but in wat way its helpful to control these documents? Plz give me some examples. Thanking you.
Regards,
J. SriramChakravarthy.
Edited by: sri ram on Mar 12, 2009 6:40 AM

Hi sri ram,
Sales document type, item type and item category
The sales document type, item type and item category define the way in which advertising sales are replicated and controlled in the system.
The sales document type is specified during sales document creation.
The item type and category are specified during document item creation. Active item types for sales document processing are defined in Customizing.
Document items of various item types or categories can be created in a sales document.
The item types are defined in the system.
Admissible item categories for each sales document type have been defined in Customizing.
Activity
Menu path
Assign item categories to sales document types
SAP Media --->Advertising Management --->Sales -
>Order --->Sales Document -
>Sales Document Item -
>Assign Item Category to Sales Document Type
If you assign the standard item and full and partial credit memo item categories to a sales document type, you can replicate associated business transactions in a single sales document by creating order and credit memo items in this document.
See also: Item Category
Create document flows
The sales document type, item category and copying variant control document flow.
To define document flow, specify the copying variants to be used to create follow-on documents and/or follow-on items for each sales document type and item category. Copying variants define the sales document type and item category in follow-on documents and/or follow-on items, such as those for credit memos or those used to convert offers to orders.
Create credit memo items
This function copies selected data from a template item within a sales document. You want to copy all schedule line data for a complaint into a new document item. The copying variant indicates that the item category for the new item is a credit memo.
Unlike a document item copy with reference to a document item, the system retains manual changes to the schedule line, such as manual surcharges or discounts, ad spec assignments or quantity changes for a document item copy with reference to a schedule line if you have defined the schedule line copying variant accordingly.
Thanks,
Swamy H P

Reg: Sales document creation

Hi Abapers,
As i am new to SD Module, would like to get some ideas from your end. My requirement is to create a sales order using Programming. After creation of sales order it should post to finance. Could anyone help me how this can be done.

REPORT ZSALESORDER.
* Parameters
* Sales document type
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text FOR FIELD p_auart.
PARAMETERS: p_auart TYPE auart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Sales organization
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text1 FOR FIELD p_vkorg.
PARAMETERS: p_vkorg TYPE vkorg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Distribution channel
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text2 FOR FIELD p_vtweg.
PARAMETERS: p_vtweg TYPE vtweg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Division.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text3 FOR FIELD p_spart.
PARAMETERS: p_spart TYPE spart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SKIP 1.
* Sold-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text4 FOR FIELD p_sold.
PARAMETERS: p_sold TYPE kunnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Ship-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text5 FOR FIELD p_ship.
PARAMETERS: p_ship TYPE kunnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SKIP 1.
* Material
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text6 FOR FIELD p_matnr.
PARAMETERS: p_matnr TYPE matnr   OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Quantity.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text7 FOR FIELD p_menge.
PARAMETERS: p_menge TYPE kwmeng OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Plant
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text9 FOR FIELD p_plant.
PARAMETERS: p_plant TYPE werks_d .
SELECTION-SCREEN END OF LINE.
* Complete Deliver
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text10 FOR FIELD p_autlf.
PARAMETERS: p_autlf TYPE autlf DEFAULT 'X'.
SELECTION-SCREEN END OF LINE.
* Data declarations.
DATA: v_vbeln            LIKE vbak-vbeln.
DATA: header             LIKE bapisdhead1.
DATA: headerx            LIKE bapisdhead1x.
DATA: item               LIKE bapisditem OCCURS 0 WITH HEADER LINE.
DATA: itemx              LIKE bapisditemx OCCURS 0 WITH HEADER LINE.
DATA: partner            LIKE bapipartnr OCCURS 0 WITH HEADER LINE.
DATA: return             LIKE bapiret2    OCCURS 0 WITH HEADER LINE.
DATA: lt_schedules_inx   TYPE STANDARD TABLE OF bapischdlx
                         WITH HEADER LINE.
DATA: lt_schedules_in    TYPE STANDARD TABLE OF bapischdl
                         WITH HEADER LINE.
DATA: lt_schedules_ink    TYPE STANDARD TABLE OF bapisdhead1
                         WITH HEADER LINE.
* Initialization.
INITIALIZATION.
v_text   = 'Order type'.
v_text1 = 'Sales Org'.
v_text2 = 'Distribution channel'.
v_text3 = 'Division'.
v_text4 = 'Sold-to'.
v_text5 = 'Ship-to'.
v_text6 = 'Material'.
v_text7 = 'Quantity'.
v_text9 = 'Plant'.
v_text10 = 'Complete delivery'.
* Start-of-selection.
START-OF-SELECTION.
* Header data
* Sales document type
header-doc_type = p_auart.
headerx-doc_type = 'X'.
* Sales organization
header-sales_org = p_vkorg.
headerx-sales_org = 'X'.
* Distribution channel
header-distr_chan = p_vtweg.
headerx-distr_chan = 'X'.
* Division
header-division = p_spart.
headerx-division = 'X'.
headerx-updateflag = 'I'.
*Complete delivery
    header-COMPL_DLV = p_autlf.
    header-COMPL_DLV = 'X'.
* Partner data
* Sold to
partner-partn_role = 'AG'.
partner-partn_numb = p_sold.
APPEND partner.
* Ship to
partner-partn_role = 'WE'.
partner-partn_numb = p_ship.
APPEND partner.
* ITEM DATA
itemx-updateflag = 'I'.
* Line item number.
item-itm_number = '000010'.
itemx-itm_number = 'X'.
* Material
item-material = p_matnr.
itemx-material = 'X'.
* Plant
item-plant    = p_plant.
itemx-plant   = 'X'.
* Quantity
item-target_qty = p_menge.
itemx-target_qty = 'X'.
* item category
itemx-ITEM_CATEG = 'X'.
APPEND item.
APPEND itemx.
*   ITEM DATA
itemx-updateflag = 'I'.
* Line item number.
item-itm_number = '000020'.
itemx-itm_number = 'X'.
* Material
item-material = p_matnr.
itemx-material = 'X'.
* Plant
item-plant    = p_plant.
itemx-plant   = 'X'.
* Quantity
item-target_qty = p_menge.
itemx-target_qty = 'X'.
APPEND item.
APPEND itemx.
*   Fill schedule lines
lt_schedules_in-itm_number = '000010'.
lt_schedules_in-sched_line = '0001'.
lt_schedules_in-req_qty    = p_menge.
APPEND lt_schedules_in.
*   Fill schedule line flags
lt_schedules_inx-itm_number = '000010'.
lt_schedules_inx-sched_line = '0001'.
lt_schedules_inx-updateflag = 'X'.
lt_schedules_inx-req_qty     = 'X'.
APPEND lt_schedules_inx.
*   Fill schedule lines
lt_schedules_in-itm_number = '000020'.
lt_schedules_in-sched_line = '0001'.
lt_schedules_in-req_qty    = p_menge.
APPEND lt_schedules_in.
*   Fill schedule line flags
lt_schedules_inx-itm_number = '000020'.
lt_schedules_inx-sched_line = '0001'.
lt_schedules_inx-updateflag = 'X'.
lt_schedules_inx-req_qty     = 'X'.
APPEND lt_schedules_inx.
* Call the BAPI to create the sales order.
CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
       EXPORTING
            sales_header_in     = header
            sales_header_inx    = headerx
       IMPORTING
            salesdocument_ex    = v_vbeln
       TABLES
            return              = return
            sales_items_in      = item
            sales_items_inx     = itemx
            sales_schedules_in = lt_schedules_in
            sales_schedules_inx = lt_schedules_inx
            sales_partners      = partner.
* Check the return table.
LOOP AT return WHERE type = 'E' OR type = 'A'.
    EXIT.
ENDLOOP.
IF sy-subrc = 0.
    WRITE: / 'Error in creating document'.
ELSE.
* Commit the work.
    COMMIT WORK AND WAIT.
    WRITE: / 'Document ', v_vbeln, ' created'.
ENDIF.
Code Formatted by: Alvaro Tejada Galindo on Dec 26, 2008 10:58 AM

Document flow for sales document

It is possible NOT update the document flow when i create sales document with reference to onther sales document?
Thanks.

When you don't want to have a relationship between to doc and want use only for reference then you can use - Dynamic Product Proposal or simply, user can refer the items from existing doc (to do this in sales order overview screen, press CRTL+F11, explore the option-easy without config )
A product proposal is a list of products for a specific customer that is automatically proposed during sales document processing. You can decide for yourself which materials should be displayed as product proposals in the sales document. You can also determine the sequence in which the materials appear in the product proposal.
During sales document processing, the system displays a product proposal in the item overview according to the customer and the business transaction. It displays the material number, material description, and historical order quantites in the sales unit last used. To use a material again, you just have to copy it. The system does not run the standard checks (pricing, availability, incompletion, material determination, free goods determination and so on) until you have entered the order quantities.
The product proposal is both an entry help and an aid to sales support and promotions. It is particularly useful in Telesales, where the employee automatically receives a display of all the materials that are of interest to a particular customer. This helps them to provide appropriate advice to the customer quickly and easily. The sales document history enables you to analyse the purchasing behaviour of a customer and recognize early on if it changes, for instance, when the customer suddenly stops ordering a product.
The product proposal differs to cross-selling in that it is dependent on the customer and sales area, and is displayed in the sales document as soon as you have entered a customer. Cross-selling, on the other hand, is triggered by a material. In other words, the system proposes cross-selling materials according to the material or a characteristic of the material you have entered.
You can determine the product proposal from different data sources:
-Order history
-Listed materials
-Excluded materials
-Item proposal
-Customer-material info records
-Customer-specific data sources
You can combine materials from these data sources to create a product proposal. The system then accesses the data sources either online or in the background.
To define a product proposal for sales document processing, you must carry out the following activities in Customizing:
-Define customer procedure for product proposal
-Define document procedure for product proposal
-Assign document procedure for product proposal to order types
-Maintain table of origin for product proposal
-Define product proposal procedure and determine access sequences
-Maintain procedure determination (in background) for product proposal
-Maintain procedure determination (online) for product proposal
The product proposal procedure determines how the system displays the product proposal in the sales document. For instance, if the system has accessed the order history, it determines how many columns should be displayed in the sales document, in which period intervals thehistoric order quantities should be displayed (for instance, day, week, or month), and most importantly, the sequence in which the system should access the data sources (for example, order history, listing, exclusion).
The product proposal procedure depends on the:
- Customer determination procedure
The customer procedure determines which product proposal procedure the system automatically uses when you create a sales document for a particular customer. It is specified in the customer master record per sales area.
- Document determination procedure
The document procedure determines which product proposal procedure the system automatically uses for a certain document type. The document procedure is stored as a key in the header for the sales document type.
If you use online processing, the product proposal procedure is determined according to the customer and document determination procedures.
If you use background processing, the product proposal procedure is determined according to the sales area in the customer master and the customer determination procedure. It does not use the document determination procedure because the document type is not recognized in background processing
Hope this can assist.
Thanks & Regards
JP

ERP sales document integration

Hello,
the C4C offers the functionality to see related ERP sales documents in an opportunity. I would like to know the criteria that show these ERP sales documents. Are only open sales documents shown? Are only the last 5 sales documents shown?
Cheers,
Koen

Hello Koen,
When a C4C system is integrated to an ERP system, the integration capability allows to see followup documents to an Opportunity which are created from a C4C Opportunity screen itself.
You get to initiate from within C4C Opportunity:
1. Customer Quote Request.
2. Sales Order Request.
Once the above two request are initiated to integrated ECC system, on the ERP system you can create the follow ups to the above docs as:
1. Customer Quote.
2. Sales Order.
Once the above four docs are created, on the C4C Opportunity screen, under the tab SALES DOCUMENTS, you get to see:
1. Document ID for Customer Quote Request created on the ERP system.
2. Document ID for Customer Quote created on the ERP system.
3. Document ID for Sales Order Request created on the ERP system.
4. Document ID for Sales Order created on the ERP system.
When you click on the Document ID of any of the above four documents, you can see a PDF preview of the relevant document.
Hope this answer helps.
Let me know if you need further information on this.
Thanks
Ankur

Controlling the misuse of FD ( free of charge Deliveries) sales document

Hello SD Gurus,
I am using the free of charge deliveries (FD) sales document type for one of the business scenarios.
Any material that i enter in this document becomes free (by virtue of the item ct. KLN)
I want to restrict the use of this document type only for certain materials and not for all (As many people will have the authorirization to create this document) I dont want that somebody intentinally or otherwise using this document to send the free goods other than specified one.
How can i control that?
You response is highly appreciated.
Thank You.
Regards,
Niketan

Hi
You can visit the following thread with the same business requirement.Hope it answers your queries.
[Sales document type restriction to create sales order;
Regards,
Ravi

Swap items from Sales Document to Billing Document

Hello, I am facing with the following issue.
We had customizing a Billing plan, that means that the information to make the billing document comes from the sales order. The sales document have 2 materials for sale, the first one must be delivered (item number 10) and the second one it is a service material (item number 20), and the customer wants that sequence. Then when I make the billing document, the system swap the sequence of the materials, put in first the service material and then the deliver material.
Then I went to check in the in copy requirements the check mark "Copy Item number", the consecuence if I check or if I uncheck, its the system put all the time as second the delivered material, only changing the item number.
There is a way to keep the same order?
Thanks in advance for the comments.
Regards,
JCR

I have found the solution of the issue; the problem was in the item category of the service material. The delivery material, has the item cathegory with the customizing for Billing plan, thats mean the letter " I " in the box of Billing reference; but the service material had the customizing for "relevant for order related billing", thats means the letter " B " in the box of Billing reference.
The solution was change the letter "B" for the letter "I"; and then choose the same Billing Plan Type for both items categorys. And also I have put the check mark in the copy requirements.
Thanks all for your comments,
Regards,
JCR

Sales document - std variant - screen variant -sales order ?

Similar Messages

Maybe you are looking for