Any Pointers to set user status in iw31 and iw32

Question

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?

Answer 1

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