Change message status after release purchase order

Hi,
I'm a newbie in MM...
When a purchase order is created, the message status is not processed (yellow light) until the purchase order is released. Then the message is printed and the status changes to green light.
As far as I see, I can't find in the spro where is this customizing set or if there is a user-exit or badi for changing the message status depending on the release indicator.
Thanks in advance!
Jen

Hi Jen,
Complete the condition record, for example, like this:
- Transaction: MN04
- Output Type: NEU
- Choose third option: Purchasing Output Determination Document Type
- Document Type: NB
- Function: VN (Vendor)
- Medium: 1 (Print output)
- Date/Time: 4 (Send immediately (when saving the application))
Select the line and press button "Communication". Complete the output device and mark the option "Print immediately"
So, when the PO is created the system generates the message with yellow status. Then, when the PO is released, the message status will be green
Regards,
Fernando

Similar Messages

  • Status table for purchase orders

    Hi experts,
    When a purchase order is accepted by someone it changes its status. Is there any table that i can select from it to obtain the worker who changed the status of a purchase order?
    Thank you all,
    Artur.

    hi,
    Try to check the table EKBE (History per Purchasing Document).
    and also check CDPOS and CDHDR table
    I guess her you find the all the required details

  • Need Message On change of Released Purchase order

    Hi
    I need to display message On Edit of released purchase order through ME22N or on click of edit in ME23N
    Kindly suggest exits for the same.

    Hi Arun,
    Create implementation for BADI: ME_PROCESS_PO_CUST. In this get the release status of PO and raise a message.
    Regards,
    Vijay

  • Problem after change item status procedure in sales orders.

    Hello experts,
    I have changed item status procedure for sales orders. But now all BDoc with queue name CSA_ORDER_xxxxx remain in state 'Written to qRFC Queue (intermediate state)' and needs to be reprocessed manually.
    No problem reprocessing.
    Have somebody any idea ?
    Best regards
    Juan Salom

    Hi,
       Is your inbound queue un-registered(type U)? Look at trx.
    SMQR
    and see if it is in un-registered. If yes, select the CSA_ORDER_*** queue and click on
    Registration
    button.
    If this does not help, re-generate your Bdoc services (for Bdoc BUS_TRANS_MSG) using
    SMOGGEN
    or
    using the generation workbench.
    Then try the delta once again and observe for queue and Bdoc status in the
    SMW01
    Hope it helps! Reward if helpful.
    Regards,
    Sudipta

  • Z Report of Transaction ME28.(Release Purchase Order)

    Dear all,
                   I want to make Z Report for the Transaction ME28 (Release Purchase Order).
    I am facing problem of GUI status in my Z Report. Actually Report is not displaying like ME28.
    and all the menu and function keys are also not coming properly.
    So, pls suggest me good solution.
    Thanks & Regards,
    Sandip Sonar.

    I am attaching a copy of ME28. Please give it to your ABAP consultant.
    He should be able to do the needful:
    REPORT RM06EF00 NO STANDARD PAGE HEADING MESSAGE-ID ME.
           Anzeigen Einkaufsbelege zur Belegnummer                       *
    Tabellen                                                            *
    INCLUDE FM06LTO1.
    INCLUDE FM06LCFR.
    **table added t16fc  - SAPBY     6 Feb 98
    TABLES: T16FG, T16FS, T16FV, T16FE, RM06B, T160B, T16FC.
    DATA: BEGIN OF XEKPO OCCURS 100.
            INCLUDE STRUCTURE EKPO.
    DATA: END OF XEKPO.
    *- Interne Tabelle der Zustände -
    DATA: BEGIN OF ZUS OCCURS 10.
            INCLUDE STRUCTURE T16FV.
    DATA: END OF ZUS.
    DATA: BEGIN OF ZUSKEY,
             MANDT LIKE EKKO-MANDT,
             FRGGR LIKE EKKO-FRGGR,
             FRGSX LIKE EKKO-FRGSX,
          END OF ZUSKEY.
    Parameter und Select-Options                                        *
    PARAMETERS:     P_FRGCO LIKE T16FC-FRGCO OBLIGATORY.
    SELECT-OPTIONS: S_FRGGR FOR EKKO-FRGGR.
    PARAMETERS:     P_FRGSE LIKE RM06A-P_FRGSE DEFAULT 'X',
                    P_FRGRS LIKE RM06A-P_FRGRS,
                    P_FRGVO LIKE RM06A-P_FRGVO DEFAULT 'X',
    set default to 'X' to show items as well - SAPBY
                    P_MITPOS AS CHECKBOX DEFAULT 'X',
    set default to 'DEFAULT'  - SAPBY
                    LISTU LIKE T160O-LISTU DEFAULT 'DEFAULT'.
    SELECT-OPTIONS: S_BSTYP FOR EKKO-BSTYP,
                    S_EKORG FOR EKKO-EKORG,
                    S_EBELN FOR EKKO-EBELN MATCHCODE OBJECT MEKK
                                           MEMORY ID BES,
                    S_BSART FOR EKKO-BSART,
                    S_EKGRP FOR EKKO-EKGRP,
                    S_LIFNR FOR EKKO-LIFNR MATCHCODE OBJECT KRED,
                    S_RESWK FOR EKKO-RESWK,
                    S_BEDAT FOR EKKO-BEDAT.
    Hilfsfelder                                                         *
    INCLUDE FM06LCEK.
    DATA: XFRG1 LIKE EKKO-FRGZU,
          XFRG2 LIKE EKKO-FRGZU.
    DATA: XSELKB LIKE EKKO-BSTYP,
          XSELKK LIKE EKKO-BSTYP,
          XSELKL LIKE EKKO-BSTYP,
          XSELKA LIKE EKKO-BSTYP.
    FIELD-SYMBOLS: .
    DATA: HFDPOS LIKE SY-FDPOS.
    **workflow line added for workflow
    DATA : LAST_USER_COMMAND  LIKE SY-UCOMM.
    Intitialisierung                                                    *
    INITIALIZATION.
      PERFORM ANFORDERUNGSBILD(SAPFM06L) USING XSELKB XSELKK
                                               XSELKL XSELKA.
    lines 67, 70 and 73 commented out -SAPBY
    **listu = t160b-listu.
      S_BSTYP-SIGN = 'I'.
      S_BSTYP-OPTION = 'EQ'.
    **if xselkb ne space.
      S_BSTYP-LOW = 'F'.
      APPEND S_BSTYP.
    **endif.
      IF XSELKK NE SPACE.
        S_BSTYP-LOW = 'K'.
        APPEND S_BSTYP.
      ENDIF.
      IF XSELKL NE SPACE.
        S_BSTYP-LOW = 'L'.
        APPEND S_BSTYP.
      ENDIF.
      IF XSELKA NE SPACE.
        S_BSTYP-LOW = 'A'.
        APPEND S_BSTYP.
      ENDIF.
    next two lines added to default the release code
      IMPORT T16FC-FRGCO FROM MEMORY.
    get parameter id 'ZRC' field t16fc-frgco.
      P_FRGCO = T16FC-FRGCO.
    Seketionsbild                                                       *
    AT SELECTION-SCREEN ON LISTU.
      PERFORM LISTUMFANG(SAPFM06L) USING LISTU.
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FRGCO.
      CALL FUNCTION 'HELP_VALUES_FRGAB'
           EXPORTING
                I_FRGOT = '2'
           IMPORTING
                E_FRGAB = P_FRGCO
           EXCEPTIONS
                OTHERS  = 1.
    AT SELECTION-SCREEN.
      CALL FUNCTION 'ME_REL_CHECK_MANY'
           EXPORTING
                I_FRGOT = '2'
                I_FRGCO = P_FRGCO
           TABLES
                T_FRGGR = S_FRGGR
                T_T16FV = ZUS.
    Beginn der Selektion                                                *
    START-OF-SELECTION.
      NOT_FOUND = 'X'.
      SET PF-STATUS 'FREI'.
      SET TITLEBAR '001' WITH P_FRGCO.
      PERFORM FRG_INIT(SAPFM06L) USING P_FRGCO P_MITPOS.
    *- Lesen Belegköpfe -
      SELECT * FROM EKKO APPENDING TABLE XEKKO
                         FOR ALL ENTRIES IN ZUS
                         WHERE FRGRL EQ 'X'
                           AND FRGGR EQ ZUS-FRGGR
                           AND FRGSX EQ ZUS-FRGSX
                           AND EBELN IN S_EBELN
                           AND BSTYP IN S_BSTYP
                           AND EKORG IN S_EKORG
                           AND LIFNR IN S_LIFNR
                           AND RESWK IN S_RESWK
                           AND BEDAT IN S_BEDAT
                           AND BSART IN S_BSART
                           AND EKGRP IN S_EKGRP
                           AND LOEKZ EQ SPACE.
      IF P_FRGRS NE SPACE.
        SELECT * FROM EKKO APPENDING TABLE XEKKO
                           FOR ALL ENTRIES IN ZUS
                           WHERE FRGRL EQ SPACE
                             AND FRGGR EQ ZUS-FRGGR
                             AND FRGSX EQ ZUS-FRGSX
                             AND EBELN IN S_EBELN
                             AND BSTYP IN S_BSTYP
                             AND EKORG IN S_EKORG
                             AND LIFNR IN S_LIFNR
                             AND RESWK IN S_RESWK
                             AND BEDAT IN S_BEDAT
                             AND BSART IN S_BSART
                             AND EKGRP IN S_EKGRP
                             AND LOEKZ EQ SPACE.
      ENDIF.
      SORT XEKKO.
    *- Prüfen Freigabevoraussetzungen -
      LOOP AT XEKKO.
        MOVE-CORRESPONDING XEKKO TO ZUSKEY.
        READ TABLE ZUS WITH KEY ZUSKEY BINARY SEARCH.
        CHECK SY-SUBRC EQ 0.
        XFRG1 = ZUS+9(8).
        XFRG2 = XEKKO-FRGZU.
        TRANSLATE XFRG2 USING 'X  +'.
        OVERLAY XFRG1 WITH XFRG2 ONLY '+'.
        SEARCH XFRG1 FOR 'X'.
    *---- Keine Freigabezuständigkeit -
        IF SY-SUBRC NE 0.
          DELETE XEKKO.
        ELSE.
    *---- Freigabestelle merken -
          HFDPOS = SY-FDPOS.
          ASSIGN XFRG2+SY-FDPOS(1) TO .
    *---- Freigabe bereits erfolgt -
          IF P_FRGRS EQ SPACE AND
              EQ SPACE.
            DELETE XEKKO.
          ELSE.
    *---- Freigabe noch nicht erfolgt -
            IF P_FRGSE EQ SPACE AND
                NE SPACE.
              DELETE XEKKO.
            ELSE.
    *---- Freigabevoraussetzung fehlt -
              IF XFRG1 CA '+' AND
                 P_FRGVO NE SPACE.
                DELETE XEKKO.
              ELSE.
                EKKO = XEKKO.
                PERFORM FRG_FEKKO_AUFBAUEN(SAPFM06L) USING HFDPOS.
              ENDIF.
            ENDIF.
          ENDIF.
        ENDIF.
      ENDLOOP.
      SORT XEKKO.
    *- Lesen Belegpositionen -
      IF P_MITPOS NE SPACE.
        SELECT * FROM EKPO APPENDING TABLE XEKPO
                           FOR ALL ENTRIES IN XEKKO
                           WHERE EBELN EQ XEKKO-EBELN.
      ENDIF.
    *- Ausgabe -
      LOOP AT XEKKO.
        EKKO = XEKKO.
        PERFORM EKKO_ANSCHRIFT(SAPFM06L).
        PERFORM EKKO_AUSGABE(SAPFM06L).
        IF P_MITPOS NE SPACE.
          LOOP AT XEKPO WHERE EBELN EQ EKKO-EBELN.
            EKPO = XEKPO.
            PERFORM FC_ME_READ_HISTORY(SAPFM06L).
            PERFORM EKPO_AUSGABE(SAPFM06L).
          ENDLOOP.
        ENDIF.
      ENDLOOP.
    Ende der Selektion                                                  *
    END-OF-SELECTION.
      IF NOT_FOUND NE SPACE.
        MESSAGE S260.
        IF SY-CALLD NE SPACE.
          LEAVE.
        ELSE.
          LEAVE TO TRANSACTION SY-TCODE.
        ENDIF.
      ENDIF.
      WRITE: /(81) SY-ULINE.
    OK-Code-Eingabe                                                     *
    AT USER-COMMAND.
    **workflow inserted 6 Feb 98 by SAPBY
        PERFORM WORKFLOW_AT_USER_COMMAND.
    INS GSB 18/02/2004 - check user approving is not user that create
    PO
    if sy-ucomm = 'FRGU' or sy-ucomm = 'FRGS'.
    loop at xekko.
      if xekko-ERNAM = sy-uname.
         CALL FUNCTION 'POPUP_TO_DISPLAY_TEXT'
           EXPORTING
             TITEL              = 'Error'
    TEXTLINE1 = 'As the creator of this pruchase order you cannot approve it
    as well !'
        leave program.
      endif.
    endloop.
    endif.
      PERFORM USER_COMMAND(SAPFM06L).
    Seitenueberschrift                                                  *
    TOP-OF-PAGE.
      PERFORM TOP(SAPFM06L).
    TOP-OF-PAGE DURING LINE-SELECTION.
      PERFORM TOP(SAPFM06L).
    **& form workflow_at_user_command
    TEXT
    ---> p1  text
    <--  p2  text
    FORM WORKFLOW_AT_USER_COMMAND.
      IF LAST_USER_COMMAND IS INITIAL.
        LAST_USER_COMMAND = SY-UCOMM.
      ENDIF.
      IF SY-UCOMM EQ 'ZURU'.
         PERFORM TRIGGER_WORKFLOW.
      ENDIF.
      CASE SY-UCOMM.
        WHEN 'BU'.
          IF P_MITPOS EQ 'X'.
            CHECK LAST_USER_COMMAND <> 'FRGR'.
            PERFORM TRIGGER_WORKFLOW.
          ELSE.
            CHECK LAST_USER_COMMAND = 'FRGS'.
            PERFORM TRIGGER_WORKFLOW.
          ENDIF.
        WHEN 'FRGU'.
          PERFORM TRIGGER_WORKFLOW.
      ENDCASE.
      LAST_USER_COMMAND = SY-UCOMM.
    ENDFORM.
    **& form TRIGGER_WORKFLOW.
    TEXT
    ---> p1  text
    <--  p2  text
    FORM TRIGGER_WORKFLOW.
    DATA : BEGIN OF ZEKKO OCCURS 20.
              INCLUDE STRUCTURE ZEKKO.
    DATA : END OF ZEKKO.
    DATA : BEGIN OF YEKKO OCCURS 20.
              INCLUDE STRUCTURE ZEKKO.
    DATA : END OF YEKKO.
    DATA : WFBAN LIKE EKKO-EBELN,
           WFERN LIKE EKKO-ERNAM.
    CLEAR : WFBAN, WFERN.
    MOVE-CORRESPONDING XEKKO TO YEKKO.
    CONCATENATE YEKKO-FRGZU 'X' INTO YEKKO-FRGZU.
    APPEND YEKKO.
    MOVE-CORRESPONDING XEKKO TO ZEKKO.
    *XEKKO-KZ = 'F'.
    APPEND ZEKKO.
    SELECT SINGLE KOKRS KOSTL
         INTO (EKKN-KOKRS, EKKN-KOSTL)
         FROM EKKN
         WHERE EBELN = XEKKO-EBELN
         AND EBELP   = '00010'.
    if sy-subrc <> 0.                  " Cost centres not mandatory at XXX
      exit.
    endif.
    CALL FUNCTION 'Z_ME_REL_EVENT_EKKO'
         EXPORTING
              I_CALL_UPDKZ = 'F'
              I_WFBAN      = EKKO-EBELN
              I_FRGCO      = T16FC-FRGCO
              I_ERNAM      = SY-UNAME
              I_UCOMM      = SY-UCOMM
         TABLES
              I_EKKO_NEW   =  YEKKO
              I_EKKO_OLD   =  ZEKKO.
    ENDFORM.

  • MESSAGE TYPE DEFAULT FOR PURCHASE ORDER

    Dear All,
    I want to set default message type ZNEU for all purchase order. I try this with T-CODE MN04 AND MN05 but it is not working.
    SO HOW I MAKE MESSAGE TYPE DEFAULT FOR PURCHASE ORDER
    Regards,
    Pankaj

    Hi,
    Miantain the all the conditions records in t.code : MN04. after that check for the "Define Partner Roles for Purchase Orde" what did you mentioned for new or change as per that,
    Check you had fine tune the output (message) type in following path:
    SPROMMPurchasingMessageOutput controlMessage tyoesDefine message type for Purchase Order--Fine-Tuned Control: Purchase Order
    Select the check box coresponding to your output(message) type ZNEU to have print output for this message type .......
    Now try creating PO & u will have default message type ZNEU......
    Hope this will help you.......
    BR,
    Patil

  • After releasing the order same screen user updating the quantity in process order  in sap pp

    Hi experts,
    After releasing the order in the same screen user updating the quantity in process order  in sap pp.
    How to control it.
    can any help in this regards
    Thanking you,
    Rishit.

    Hi Rishit,
    You can control it by BAdi WORKORDER_UPDATE method AT_SAVE make error message if there is any change in quantity.
    Or you can create Transaction Variant through SHD0 for CO02 and make field Total Qty (CAUFVD-GAMNG) as output only.
    Regards,
    R.Brahmankar

  • Changing the status of the sales order item based on reason for rejection

    Hi All,
    When a Sales order item is rejected then the status at the item level is changed as 'TECO'.When the reason for rejection is removed the status 'Teco' is reset.This status change can be achieved using the user exit 'MV45AFZZ'.But the exit does not allow re-atp calculation whenver a blocked item is release.I have use the exit 'MV45AFZB' ,through this the status change as well as re-atp calculation takes place.But the status changed(Based on reason of rejection) does not appear in the same screen.The change gets reflected only when the sakes order is saved and i open it again.
    I want the status change to appear in the same screen.I am doing my code in the form 'userexit_check_vbap' of the exit 'MV45AFZB'. Please let me know if there are any user exits or BADI's available for the same(Changing the status of the sales order item based on reason for rejection ).
    Regards,
    S.Subasree

    Hi subburamaiah
    If you want the report you can create a separate SIS report . In that take the input field  as a Reason for rejection.. and ask for the output the list of sales orders .Now when you check this user defined report you will give the reason for rejection and check what all orders got rejected on that reason for rejection.
    Regards
    Srinath

  • Define status for backend purchase order in SRM7.02

    Hi,
    i am working in SRM 7.02 classic scenario using PI.
    When the SC is converted to Backend PO, some PO XML are failed due to various reason. Instead i need to create a PO in held status.
    For the same, we have settings 'Define status for Backend purchase order' in SPRO. If we maintain the information in this setting that is enough..??It will work??
    1.I heard there is some enhancement need to done for the same to work ...??if it is what is the enhancement ???
    2. if it is work, then all PO will be created in Held status or only error PO will be created in Held status?? remaining in released status ???
    Kindly advice me ..
    Thanks

    As far as,  BAPI_PO_CREATE1, you need to pass
    MEMORY_UNCOMPLETE = abap_true
    MEMORY_COMPLETE   =  abap_false
    for POHEADER, pass,
    MEMORY = 'X'
    MEMORYTYPE = 'H'
    for POHEADERX, pass,
    MEMORY = 'X'
    MEMORYTYPE = 'X'
    Though you will be using ESOA for this, this knowledge would help.
    Regards,
    Ganapathi

  • Unprinted released purchase orders

    Hello forum,
    Is there any way from standard SAP (report) to watch, which purchase orders are released but they are NOT printed ?
    Thanks in advance.

    Hi Stratos,
    You can achieve this through Standard SAP. I am assuming that you have the print output, not set, as "send immediately when saving the application"
    Please provide the list of P.O's which you are investigating in ME9F, provide the application as EF and Processing Status as 0 (Not processed)
    This way, you will get the whole list of P.O's which have not been printed out, please note that outputs can only be processed on successfully released Purchase Orders.
    Regards
    Shailesh

  • Change material status after creating SO

    Hi Guru,
    i have created a sales order with material 'DCC001'.
    after creating the sales order the STATUS of material 'DCC001' should be 'Sales not allowed'.
    but, when i am checking the status of that material, its showing blank in field 'X-distr.chain status' which is in tab 'Sales: sales org. 1'.
    Please tell me how can i change the status after creating SO.
    Thanks & Regards
    Sohel

    Please post in correct forum..

  • ABAP-Workflow : which way to send email after creating Purchase Order ?

    Hi expert,
    I'm a new workflow so I have not  understood about workflow . Please help me ...
    Today, I have recieved a request from client as below:
       +    SAP system auto send a email to USER B after  creating Purchase Orders by User A.
       *++.  USer B open email and click on the link in his/her email and open new transaction to Release this Purchase Order.*
    Could you please help me how to do that?
    Thank you so much all.

    Hi ,
    Thank you so much for your quick response.
    I found in SAP system  2 workflows:
                WS20000075 : Release of purchase order
                WS11000013 : Complete Purchase Order
    Open  transaction "SWDD" I have added the step  "Send Email" --> Active and Excute  --> enter PO number --> system auto send email to USER B.
    But I want the system auto semd email after clicking SAVE in  transaction"ME21N" , No need enter PO number in SWDD .
    How to integrate between ME21N and Workflow? Could you please helpme step by step or sample to do that.?
    Thank you so much .

  • Every time system create new production order after releasing sales order c

    Hi Guru,
    FG material strategy: 82 (sales order creates production order).
    After creating the sales order it goes in to credit block. Whenever we release sales order from credit block through VKM1, system has created production order. We confirmed this production order and delivered.
    But after this sales person change the sales order value, because of which again sales order goes into the credit block and after releasing sales order from credit block system create new production order even if one production order already confirmed and delivered against the same sales order.
    *Every time system create new production order after releasing sales order credit block.
    Thanx & regards
    pnu

    PNU,
    So, to restate:
    In MD04, you have Unrestricted Sales order Stock ('E' Stock) on hand.
    In the same MRP segment, and against the same Storage Location as the stock, you have a Sales Order requirement that was recently blocked and unblocked.
    During the unblocking event, the system produced a new production order.
    This is not normal.  If the above accurately depicts your situation, I would look for an altered Strategy 82, or a userexit.  SAP ATP (the beginning event of the Strat 82 process) will normally first check for the availability of stock.  Only if the stock is not available, then it will create the new production order.
    Best Regards,
    DB49

  • Report for released purchase order

    Hai guru's
    this is second time but i did't get any good replay please consider this, i want any standard report for released purchase order,means(i released two backdated po today next day i verify the report ME2n,those po are not display, the system take only document date not released date, now i am using CDHDR through this i got the report. but it is big process, so once check this and send your valuable solution.
    Prasad

    Hi Krishna,
    You could use Me2N with the dynamic selection coupled with normal selection screen.
    In Dynamic selection(3rd icon in screen).....you can select for which company code, release indicator as released....and save it as default variant.
    hope this should solve your query
    Sk.

  • Error release purchase order using transaction code me29n

    i have warning error this purchasing document number cannot be released.
    while i enter me29n t code.why?
    then how to release purchase order using me29n t code?
    can anyone answer this two questions.

    hi
    i have warning error this purchasing document number cannot be released. while i enter me29n t code.why?
    is the release strategy is triggred for the po ?? check thisin  P order in me23n ,in header level check release strategy tab ,
    then how to release purchase order using me29n t code? can anyone answer this two questions.
    just go to me29n >release strategy tab here just click on the release button in front of the release code

Maybe you are looking for

  • Create a new database in foxpro , msaccess dynamically

    hello, i am writing an application in which depending on the users selection a database will be created dynamically .i.e if he selects oracle or foxpro or access it will create a new database using the dsn supplied by the user and then creates the ta

  • Error when ejb deployment in WLS 9.1 clustered environment

    Hello, We have a WLS 9.1 cluster consisting of one admin server and two managed servers. we are deploying ejb jar,It is succeed on the first managed server but fail on the second managed server. The admin console and for the second managed server con

  • On 3rd replacement! help with ongoing issues

    I am desperate! I got my first 3gs in May and by July I took it to a Genius Bar becuase of battery issues. They replaced it immediately. That phone worked fine at first then it started to freeze. It would turn off randomly and I wouldn't be able to g

  • Jsp:forward failed with 'Response already committed'

    I got a "Response already commited" error when using logic:forward or jsp:forward inside a JSP page fragment that is part of a Struts Tiles layout. Here is the code fragment included in the layout.jsp. <%@ taglib uri="/WEB-INF/struts-logic.tld" prefi

  • Re: playbook wifi connection issues

    I just completed the new download and now I can't connect to any Wifi, my help doesn't work and the thing won't shut down properly.  what the heck!!!!  I got it for a Xmas gift and don't know what to do.