IW31/32 Operation User Status visible as a field on  Operation tab table

Hello,
Is there a way to add the "Operation User Status" as a field visible on the Operation tab table for IW31/32.
Your help will be very much appreciated.
Thanks.

jay23r 
Not as standard.. and its the same with the used-fields which should be displayed on the Operation tab table (it is in the task list..)
I don't know why SAP haven't sorted these out...
Open an OSS Message to SAP - the more requests they get, the more chance there is of them fixing it in the future
What we have done a few times in the past is to utilise the Header Enhancement tab (user-exit IWO10018) to add a table control to show these fields. Its not elegant, but it works
PeteA

Similar Messages

  • How to get system status and user status ?

    how to get system status and user status for the given production order?
    In which PP table we can
    find these?
    Thanks&Regards
    Satish

    Hi Ram,
    Use the FM "STATUS_READ" to read both the system and user statuses for an Order.
    Alternatively, the following tables store the user and system status info:
    JSTO- Status object information
    JEST- Individual Object Status
    Hope this helps.
    Let me know if u need further information.
    Regards,
    Sonal

  • How do I report on BP's with active User Status?

    We are using the Status tab on the BP to indicate specific status(s) such as Bad Debt, Cash Only, etc.  I have found the various status 'types' in table TJ30T (TXT04 & TXT30) along with the Status Profile and User Status but I am unable to find a table that allows me to find all the BP's with each active status type.  Is there a way to query this information?  Thanks in advance for any help you can give.

    Hi Linda
    I assume you're looking for tables JEST and JSTO.
    You can access the information for example via function STATUS_OBJECT_READ.
    Yep
    Jürgen
    Edited by: sattlerj on Mar 15, 2010 7:31 AM
    Edited by: sattlerj on Mar 15, 2010 7:47 AM

  • Problem in catching the User status of a WBS Element

    Hi All,
          In CJ20n transaction we need to catch the User status for a particular WBS element when it gets changed to 'Technically Completed(TECO)' so that we can create an asset.
         At present we are using the method <b>'AT_SAVE'</b> of the BADI <b>'WORKBREAKDOWN_UPDATE'</b> in which we are unable to catch the user status since the user status is not getting updated in the JEST table at that time.
        We have tried calling a function module in Update task but in that also the JEST table is not getting updated.
    Please provide us the solution.
    Thanks and Regards,
        Siva

    Hi Siva,
    Try the following BADIs
    WBS_FIELDS_FOR_ASSET
    WBS_MULTIPLE_ECP
    If these do not solve your purpose, then there is a work around..
    1). Goto the transaction CJ20n -> goto the User Status Screen -> On the User Status check box press F1 -> Goto technical information. Get the Structure and field name of the Status.
    2). This structure will be filled up with the current value during the program execution. You can get the value from this Structure.
    Hope it helps...
    Lokesh

  • How to retrieve the User Status on WBS Elements

    Hello,   could someone please tell me  how to retrieve the User Status for WBS Elements using ABAP?  Which table stores this information.
    Thanks.

    if you have the OBJNR there was also another FM status  in Se37 [link>>|http://sap.ittoolbox.com/groups/technical-functional/sap-dev/changing-status-620444]
    also look in the similar requirement [discussion|http://sap.ittoolbox.com/groups/technical-functional/sap-bw/wbs-user-status-262089]

  • Any Pointers to set user status in iw31 and iw32

    Hi all,
    I am working on an enhancement where I need to set the user status for an order every time a new order is created(iw31) or an existing order is changed(iw32) and a material in that is flagged as a retirement unit material.
    Is there any function module to do that?

    Hello Anu
    I would like to point to the BAPI documentation where a useful BAdI (<b>IBAPI_ALM_ORD_MODIFY</b>) is mentioned:
    FU BAPI_ALM_ORDER_MAINTAIN
    Short Text
         Process Maintenance-/Service Order
    Functionality
         This Business Application Programming Interface (BAPI) is used for
         changing maintenance- or service orders and their lower-level objects.
         The following objects of an order can be processed (for restrictions,
         see the note at the end of the documentation):
         o   Order header
         o   Partner
         o   User status
         o   Order operations
         o   Relationships
         o   Components
         o   Long texts for order header, operations, and components
       Function
         Calling up this BAPI once allows you to perform all the operations. For
         this the system supplies the function module with a method table
         containing the methods to be performed. The entries in the method table
         refer to data records in the optionally filled-out data tables. All the
         methods from the method table are performed. Alternatively, just lower-
         level objects from existing orders can be changed.
         You can process the transferred data with the Business Add-In (BAdI)
         IBAPI_ALM_ORD_MODIFY to, for example, merge data from the external
         system with data from the R/3 system. The BAdI is called up as soon as
         the transferred data is converted into the internal format. The tests
         then take place after this.
       Construction of Method Table
         o   REFNUMBER   Reference number for linking object methods - attributes
             The reference number is the line of the database which contains the
             corresponding data. The data table is determined by the object type.
         o   OBJECTTYPE  Object category
             The object category specifies which object from the order should be
             processed. The key words listed here are not language-dependent and
             must  be transferred exactly as they are. The following objects
             exist:
             -   HEADER      Order header
             -   PARTNER     Partner data
             -   USERSTATUS  User status
             -   OPERATION   Operation data
             -   RELATION        Relationships
             -   COMPONENT   Components
             -   TEXT            Long texts
             -   (empty)     ,General BAPI functions (save)
         o   METHOD      Methods
             The methods with which the data should be processed. The following
             functions exist:
             -   CREATE          Create objects
             -   CHANGE          Change objects
             -   DELETE          Delete objects
             -   RELEASE         Release
             -   TECHNICALCOMPLETE   Technically complete
             -   ATPCHECK            Availability check
             -   CALCULATE       Calculate
             -   SCHEDULE            Schedule
             -   DELELTEDSEX     Delete the status for external scheduling at
                 operation level
             -   SAVE                Save all data
             -   DIALOG          Call-up dialog. See explanation below.
             -   TRACE       Write trace file in the specified file to the
                 frontend
         o   OBJECTKEY       SAP external object key
             This key is for assigning the lower-level objects correctly to the
             corresponding objects, as there is always just one key in the data
             table. The key must have the following structure:
             -   1-12        Order number
                 When creating orders with internal number assignment, a
                 reference number  beginning with % must be entered here. The
                 BAPI then returns this number and the number actually assigned.
             -   13-16       Operation number
             -   17-20       Sub-operation number
             For relationships, the key is structured as follows:
             -   1-12    ,Order number from
             -   13-16   Operation number from
             -   17-28   Order number to
             -   29-32   Operation number to
         The following methods are permissible for the individual objects:
         o   HEADER:
             CREATE, CHANGE, RELEASE, TECHNICALCOMPLETE, ATPCHECK, CALCUALTE,
             SCHEDULE
         o   OPERATION
             CREATE, CHANGE, DELETE, DELETEDSEX
         o   PARTNER, RELATION, COMPONENT, USERSTATUS, TEXT:
             CREATE, CHANGE, DELETE
         o   (empty):
             SAVE, DIALOG, TRACE
       Data tables and update tables
         The objects have one or more data tables. For some objects you can
         specify which of the fields specified in the structure should be
         changed. For this you must set the field in the corresponding table to X
         as in the data table. If no update-table  is transferred, then only
         those fields are set that have a value that is not initial. This
         simplifies the transfer data. However, this means it is not possible to
         delete fields. If an update structure should  only be specified for some
         data records, the table with the update fields must nonetheless have the
         same amount of lines as the data table.  The empty lines are then
         treated as if no update structure was transferred. The objects
         "Partner", "User Status", and "Text" have no update tables. The whole
         data record is always copied here.
       References
         The objects use the field REFNUMBER from the method table to refer to
         the lines in the data table. Counting always begins with 1. In doing
         this, REFNUMBER also refers to the update table. However, in the method
         table there is a second reference to higher-level objects for
         lower-levels objects. The field OBJECTKEY must be filled with  order
         number, operation number, and sub-operation number, as specified above.
         If lower-level objects of a newly-created order should be changed, then
         you must enter a temporary order number that must begin with %. Several
         orders can be numbered serially, for example, with  %00000000001,
         %00000000002 ... .
         The following objects have special treatment for REFNUMBER:
         o   Partner
         o   Texts
         Partners have an order number in the data table. During processing of
         the method table, all those entries in the data table are processed
         which have an order number that is the same as that in the line to which
         the method refers. Thus, through just one entry in the method table,
         several partners can be changed.
         Texts are composed of two tables. The first table (IT_TEXT) is made up
         of the header data of the text. Here you must specify the object and the
         first and last line of the text table (respectively inclusive, counting
         from 1). Through this, a line segment is specified in the text line
         table (IT_TEXT_LINES).
       Peculiarities in processing
         The BAPI processes the transferred methods in a particular sequence,
         which must not correspond to the sequence in the methods table.
         o   Write trace file
         o   Change user status time period 1
         o   Delete objects (dependent first)
         o   Create new objects
         o   Change existing or newly-created objects
         o   Change user status time period 2
         o   Status change of order
         o   Save data
         The methods are performed such that lower-level objects can also be
         assigned to newly-created objects. For example, first the operations are
         created, and then the components. Long texts can also be created for the
         objects.
         Components have an exceptional position. Components are created through
         the assignment to an operation, that is, using the "key" order/
         operation (item number). However, as this is not the unique component
         key, you can only access the components to change them, delete them, or
         add long texts by using the reservation number/-item, which is only
         given after saving. This means that, for example, you cannot create a
         long text when you create the component.
         User status changes can take place at two different time points. Time
         point 1 is before the object changes, time point 2 is after the object
         changes and before the status change of the system. These time points
         should be defined in the transfer table in the field CHANGE_EVENT. The
         field documentation contains the possible values.
         The external scheduling is offered by the BAPI as a special function.
         THe BAPI can set the date field directly at the operation level, and
         select the operation with the status DSEX "Date set by external system".
         This status prevents any further scheduling of the operation, it keeps
         the transferred dates. For this, set the category 'X' in the restriction
         categories. When reading the operation, this category is also returned,
         independent of the category of restriction set in the dialog. To delete
         the status, you can call up the method DELETEDSEX for the object
         operation. The external scheduling cannot be influenced in the dialog.
         All changes to the scheduling restrictions in the dialog are saved as
         normal, but are not relevant for the scheduling as long as the status
         DSEX is active.
         Every time the BAPI is called up, a SAVE or DIALOG method must be
         transferred. Normally, calling up a BAPI is seen as a transaction. All
         data that is changed in the BAPI should be saved to the database
         immediately. The BAPI checks whether a SAVE method exists, otherwise it
         terminates processing. A test run of the BAPI is composed of a normal
         call-up using the SAVE method and a subsequent
         BAPI_TRANSACTION_ROLLBACK. To call up the BAPI without the SAVE method,
         for example, to realize dialog transactions, the BAPI can be called up
         with the DIALOG method. This switches off the check for the SAVE method.
         The processor must then ensure that later either a SAVE method or a
         BAPI_TRANSACTION_ROLLBACK is called up.
         A BAPI_TRANSACTION_COMMIT without SAVE method terminates processing in
         the update to ensure that no inconsistent data is written to the
         database. The processor who called up the BAPI does not receive any
         confirmation for the termination of the update in the target system.
         This logic is necessary as the order data was flagged for updating with
         BAPI_TRANSACTION_COMMIT through the SAVE method. However, the status
         information was already flagged for updating when the BAPI was called
         up. A BAPI_TRANSACTION_COMMIT without SAVE method then just saves the
         status information and would generate inconsistent orders, if the
         updating was not terminated.
       Customer Enhancement
         The BAdI IBAPI_ALM_ORD_MODIFY can be used to change the transferred
         data. The BAdI is called up after the conversion of the transfer
         structure into the structures used internally. Additional data can be
         transferred using the table EXTENSION_IN. Only then is the data checked.
    Example
         The following examples should clarify the use.
       Creating an order
         OBJECTKEY should be filled with a temporary key. The BAPI returns  this
         key together with the assigned order number in the return table
         ET_NUMBERS . The order number in the HEADER table should also be filled
         with the number. For external number assignment, the external number
         should be specified. The update structure can be transferred if
         necessary.
         Methods table
         REFNUMBER   OBJECTTYPE  METHOD      OBJECTKEY
         1           HEADER      CREATE      %00000000001
         IT_HEADER
         ORDERID     ORDER_TYPE  PLANPLANT   ...
         %00000000001    PM01    1000        ...
       Creating an order with operation and long text
         Methods table
         REFNUMBER   OBJECTTYPE  METHOD      OBJECTKEY
         1           HEADER      CREATE      %00000000001
         1           OPERATION   CREATE      %00000000001
         1           TEXT        CREATE      %000000000010010
         IT_HEADER
         ORDERID     ORDER_TYPE  PLANPLANT   ...
         %00000000001    PM01    1000        ...
         IT_OPERATION
         ACTIVITY    SUB_ACTIVITY    CONTROL_KEY WRK_CNTR    ...
         10                      PM01        MECHANIC    ...
         IT_TEXT
         ACTIVITY    ...         TEXTSTART   TEXTEND
         10          ...         1           2
         IT_TEXT_LINES
         TDFORMAT    TDLINE
          *          Longtext for operation 10, line 1
          *          Line 2 of the long text
    Notes
       Using the BAPI to process the order data cannot support all the functions
       of the transaction. This applies in particular for the following
       functions:
         Order header data
         o   The object list cannot be processed.
         o   Refurbishment orders are not supported.
         o   The estimated costs cannot be processed - only the estimated overall
             costs of the order.
         o   Notification data cannot be processed with the order BAPI. Even if
             the settings in Customizing are such that the orders and
             notifications can be maintained on one screen, no notification is
             created for the order.
         o   Permits cannot be processed.
         o   The order addresses cannot be processed.
         o   Individual partner addresses cannot be maintained.
         o   The settlement rule cannot be maintained.
         Order functions
         o   Printing the papers is not possible.
         o   Locking and unlocking the order is not possible.
         o   Accepting and rejecting quotations is not possible.
         o   Business completion is not possible.
         o   Flagging for deletion is not possible.
         o   The log cannot be displayed.
         o   User default values are not used.
         o   The field selection is not checked.
         o   The Customer Exits/BAdIs are not executed completely.
         o   Joint ventures are not supported.
         o   Funds Management is not supported.
         o   Investment orders are not supported.
         o   No integration of service products with task lists possible.
         o   No integration of configurable service products possible.
         o   Assignment of sales document items with service products in
             accordance with the aforementioned conditions.
         Operation data
         o   A change of the control key in the operation is not possible, if
             this leads to a change of the processing type (internal-/external
             processing)
         o   User status change not possible.
         o   Production resources and tools cannot be processed.
         o   Service lines cannot be processed.
         o   Task list integration is not supported.
         o   Linking operations with object list is not supported.
         Component data
         o   User status change not possible.
         o   BOM data cannot be processed.
         o   The delivery address cannot be processed.
    Further information
         See also the documentation for the individual transfer tables.
    Parameters
         IT_METHODS
         IT_HEADER
         IT_HEADER_UP
         IT_HEADER_SRV
         IT_HEADER_SRV_UP
         IT_USERSTATUS
         IT_PARTNER
         IT_PARTNER_UP
         IT_OPERATION
         IT_OPERATION_UP
         IT_RELATION
         IT_RELATION_UP
         IT_COMPONENT
         IT_COMPONENT_UP
         IT_TEXT
         IT_TEXT_LINES
         EXTENSION_IN
         RETURN
         ET_NUMBERS
    Exceptions
    Function Group
         IBAPI_ALM_ORDER
    Regards
      Uwe

  • How to modify operation user status

    Hi Team,
    I am created an order from IW31. Is there any way to change the user status of its operation.
    I mean I am looking for any enhancement or BAPI by which I can change the user status of operation.
    Mainak

    Hi
    BAPI to change user status is "BAPI_ISUSMORDER_USERSTATUSSET"
    and BAPI to change system status "BAPI_ISUSMORDER_SETSTATUSTECHN"
    Thanks,
    Prajakta

  • Planning board user status at operation level

    Hi Guys,
    Our user is not using planning board and therefore system status should not have DISP status as system status.
    Now user needs two profiles in the CM07 bases on the statuses SCH and RFS.
    Profile 1: For operation user status=SCH
    Profile 2: For operation user status=RFS
    I know how to create over all profile for planning board from the below path.
    IMG>Production>Capacity Requirements Planning>Evaluation>Profiles-->Define overall profiles
    Could any one please suggest me where and how to define required user statuses against the profile.
    Thanks,
    Lucky

    Hello,
    Please check the transction BS02. or Below Path in SPRO
    Production Planning for Process Industries>Master Data>Resource>General Data>Define Status Profiles
    Regards,
    Rakesh

  • User status at operation level

    Hi,
    I have created one user status profile and attached in order type. In this profile I have included Operation and Order header as an "Allowed object type"
    My problem is when I am changing  user status at order level , it is not getting changed automatically at operation level.
    Pls suggest me the solution.
    Thanks

    Hi,
    I dont think it is possible .
    A suggestion not sure if it works .
    Assign user status profile operation wise and then have some development to check the operation status and
    then update production order status with same user status you mentioned in operation.
    FM: STATUS_CHANGE_EXTERN will help you to change the user status of order.
    Regards,
    Vishal

  • Block Order TECO on the basis of operation User Status

    Hi Experts,
    I am trying to restrict the TECO of maintenance order on the basis of order operation status. I have configured the user status profile and assigned it to order operation. This user status profile have two statuses, INCL - Incomplete and another is CMPL - Complete. I have prohibited the TECO for user status INCL. But when I create an order and try to TECO, the system allows me TECO it enenif the operation user status is INCL.
    Could you Pl. tell me, have I missed something in configuration?

    Dattatraya,
    Actually you can control TECO by completion confirmation of order operation as PCNF ( partial confirmation) for operation which you have mentioned in Order. So you can set up in configuration like allow TECO only once CNF ( Full confirmation ) for all operations mentioned in Order.
    For your mentioned scenario , I dont feel based on user status you can stop the TECO, anyway you can check with other experts as well.
    Riyaj

  • Need help on to set User status for Operations in Maintenance order

    Hi experts,
    i am new to PM module.
    i need to do BDC for IW31. i want to know some inforamtion
    on user status for each opertaion.
    my problem is ,, what is user status.
    why it is saying order is not yet released when saving and status can not set.
    in this cases how can i do BDC.

    User status are something set in the configuration and specific to the company which SAP hasn't given in the system status.
    May be in your system user status are configured to set only  after the release of the order.
    For doing the userstatus you may need to release the order, you can release the order thru bdc and then do bdc for user status. Also see below link
    http://www.sap-img.com/plant/user-status-set-date-in-maintenance-order.htm

  • To update user status of an operation in Plant maintenance

    Hi
          I ma trying to update the user status of an operation of an order using function module status_update but it is not working properly. Although the same function module is working fine for updation of user status of order. Can somebody please tell me some other function module to update the user status of operations?
    Thanx in Advance.
    Richa.

    Hi Richa,
    I have the same requirement like which you had. updating the operation user status in work order.
    How did you attend this requirement. Please let me know your solution.
    Thanks in advance.

  • User status for an operation

    Hi all,
    I have 3 queries-
    1) What is the meaning of business transaction "GOODS MOVEMENT" in BS02-status profile / user status screen
    2) I have an order with 2 operations in it.
    I have created a user status for the "PP/PM operation" business object type and the following business transactions are marked as forbidden.
    Confirm transaction
    Delete operation
    Determine costs
    Goods Movement
    Partially confirm operation
    I want that when the status is assigned to the operation the system that the system should not any confirmation, goods movement (issue/resceipt), activity posting for that operation.
    When i assign the user status and make the confirmation by co11 then such messege is issued by the system which is OK.
    But when i issue the component by 261 mvt type by mb1c to the order, the system carries out the transaction.???
    How it is??
    I think this issue is carried out at order level that is why it is.
    3) What is the meaning of all the business transactions in bs02 screen???
    Regards,
    MHP

    Hi Rajesh,
    Thanx for the reply. I'd rewared  with the points.
    I am not clear from ur answers as follows.
    ANS 2-- I AM NOT CLEAR THAT IN MB1A WHEN SYSTEM WILL ALLOW & WHEN SYSTEM WILL NOT ALLOW??
    U MEAN TO SAY IF IT IS PLANNED THEN SYSTEM WILL ALLOW & IF IT IS UNPLANNED SYSTEM WILL DISALLOW. IS IT SO??
    BUT THEN WHAT IS THE USE OF FORBIDDING "GOODS MOVEMENT".
    ANS 3-- I KNOW WHAT U HAD REPLIED WITH. BUT I WANT THE MEANING OF ALL
    BUSINESS TRANSACTIONS
    REGARDS,
    MHP

  • BAPI_ALM_ORDER_MAINTAIN Operation User Status Update

    Hi All,
    I am trying to use this BAPI_ALM_ORDER Maintain to update the user status at the Operation level, but am facing the following issue:
    In the IT_METHODS table, I am passing the USERSTATUS CHANGE (with the right object key - aufnr + vornr), and SAVE Method.
    And am filling the User Status table (IT_USERSTATUS) with the correct user status to be updated at the Operation Level.
    But when I execute the BAPI - it throws an error saying that the User status XXXX doesnt exist in the XXXXXX (This is the wrong profile. This profile is at the Header level and not at the operation level) Profile.
    So somehow its trying to update at the Header level and not at the operation level.
    Any idea what can be the reason?
    Regards
    Ankur

    Hi,
    BAPI_ALM_ORDER_MAINTAIN user status Change
    check out this link..
    Thanks & regards.

  • BAPI_ALM_ORDER_MAINTAIN - Change User Status in Operation u00BF?

    IT´S POSSIBLE CHANGE USER STATUS OF THE OPERATION?
    I SEE THAT FILL IT_METHODS AND IT_USERSTATUS BUT ONLY CHANGE THE USER STATUS OF HEADER ORDER.
    ANY CAN HELP ME?
    THANKS IN ADVANCE.

    Hi,
    Use the FM "ALM_ME_ORDER_CHANGE"
    There you can change the operation details including the User status.
    Hope this may help you.
    Regards,
    Smart Varghese

Maybe you are looking for