User status during reconciliation

Hi All,
I have configured AD connector for reconciliation and it is working fine. Also I have created Resource Object, Process Definition and form for multiple resources of AD, during reconciliation when event is linked user status is set to 'Provisioning' instead of 'Provisioned' as per the default functionality and during the successive recon the status is changed to 'Enabled'.
Can any one please tell me what configuration might be missing due to which the status is set to 'Provisioning' at first time.
Any pointers in this regards will be appreciated.
TIA

After successful target source recon, the status should be 'Enabled' or 'disabled' depending on the user account status in AD. Can you look at the tasks that are executed when the status is set to 'provisioning'? Which task fails? what is logged in the logs? Could be that 'Get ObjectGUID' task is not completed and it completes before the next run of the scheduler, which is why it works fine in second run.

Similar Messages

  • Function module to set user status during QA11 transaction

    Hi ,
    Anyone knows the function module to set the user status during QA11/QA12  transaction?
    I received the user status 'e.g CFA1' from an idoc data and would like to set the user set based on this idoc value during QA11/QA12 transaction.
    Any function module for this action? BDC seems impossible..
    Thanks.
    Regards,
    Clarice.

    oh i realised this function module can be used
    STATUS_CHANGE_EXTERN
    with a commit statement..

  • Deleting IDM user accounts during reconciliation

    Hello All,
    We have an authoritative data source which is a MySQL database. I have loaded all the users from the DB into IDM. What I want to know is can we delete the user in IDM when the user account is deleted from the MySQL database?
    How can I achieve this during reconciliation?
    Any help would be highly appreciated.
    Thank you very much.
    Vamsi

    I think you need to use the per account workflow, which is part of the recon policy. It should be something like:
    <Extension>
    <WFProcess name='UC2 ORA Per Acct Workflow' title='UC2 ORA Per Acct Workflow'>
    <Variable name='userName' input='true'/>
    <Variable name='accountId' input='true'/>
    <Variable name='loginApplication' input='true'/>
    <Variable name='resource' input='true'/>
    <Activity id='0' name='start'>
    <Transition to='Sync Attributes'>
    <eq>
    <ref>initialSituation</ref>
    <s>AR_SITUATION_NAME_UNMATCHED</s>
    </eq>
    </Transition>
    <Transition to='Deprovision User'>
    <eq>
    <ref>initialSituation</ref>
    <s>AR_SITUATION_NAME_DELETED</s>
    </eq>
    </Transition>
    <Transition to='Disable User'>
    <eq>
    <ref>initialSituation</ref>
    <s>optional logic here</s>
    </eq>
    </Transition>
    <Transition to='Clear Task Results'/>
    <WorkflowEditor x='38' y='177'/>
    </Activity>
    <Activity id='1' name='Sync Attributes'>
    <Variable name='WF_ACTION_ERROR'/>
    <Variable name='user'/>
    <Action id='0' name='Checkout User' application='com.waveset.session.WorkflowServices'>
    <Argument name='op' value='checkoutView'/>
    <Argument name='type' value='User'/>
    <Argument name='id' value='$(accountId)'/>
    <Argument name='authorized' value='true'/>
    <Argument name='Form' value='UC2 ORA Per Acct Form'/>
    <Variable name='view'/>
    <Return from='view' to='user'/>
    <Return from='WF_ACTION_ERROR' to='ERROR'/>
    </Action>
    <Action id='1' name='Checkin User Object' application='com.waveset.session.WorkflowServices'>
    <Condition>
    <isnull>
    <ref>WF_ACTION_ERROR</ref>
    </isnull>
    </Condition>
    <Argument name='op' value='checkinView'/>
    <Argument name='view'>
    <ref>user</ref>
    </Argument>
    </Action>
    <Transition to='Clear Task Results'>
    <isnull>
    <ref>WF_ACTION_ERROR</ref>
    </isnull>
    </Transition>
    <Transition to='end'/>
    <WorkflowEditor x='259' y='7'/>
    </Activity>
    <Activity id='2' name='Deprovision User'>
    <Variable name='WF_ACTION_ERROR'/>
    <Variable name='user'/>
    <Action id='0' name='Checkout User' application='com.waveset.session.WorkflowServices'>
    <Argument name='op' value='checkoutView'/>
    <Argument name='authorized' value='true'/>
    <Argument name='type' value='Deprovision'/>
    <Argument name='id' value='$(accountId)'/>
    <Variable name='view'/>
    <Return from='view' to='user'/>
    <Return from='WF_ACTION_ERROR' to='ERROR'/>
    </Action>
    <Action id='1' name='Select All Accounts for Deprovision'>
    <expression>
    <set name='user.resourceAccounts.selectAll'>
    <s>true</s>
    </set>
    </expression>
    </Action>
    <Action id='2' name='Checkin User Object' application='com.waveset.session.WorkflowServices'>
    <Condition>
    <isnull>
    <ref>WF_ACTION_ERROR</ref>
    </isnull>
    </Condition>
    <Argument name='op' value='checkinView'/>
    <Argument name='view'>
    <ref>user</ref>
    </Argument>
    </Action>
    <Transition to='Clear Task Results'>
    <isnull>
    <ref>WF_ACTION_ERROR</ref>
    </isnull>
    </Transition>
    <Transition to='end'/>
    <WorkflowEditor x='308' y='241'/>
    </Activity>
    <Activity id='3' name='Disable User'>
    <Variable name='WF_ACTION_ERROR'/>
    <Variable name='user'/>
    <Action id='0' application='com.waveset.session.WorkflowServices'>
    <Argument name='op' value='disableUser'/>
    <Argument name='accountId' value='$(accountId)'/>
    <Argument name='doWaveset' value='true'/>
    </Action>
    <Transition to='Clear Task Results'>
    <isnull>
    <ref>WF_ACTION_ERROR</ref>
    </isnull>
    </Transition>
    <Transition to='end'/>
    <WorkflowEditor x='390' y='387'/>
    </Activity>
    <Activity id='4' name='Clear Task Results'>
    <Action id='0' application='SET_RESULT_LIMIT'>
    <Argument name='limit' value='0'/>
    </Action>
    <Transition to='end'/>
    <WorkflowEditor x='351' y='104'/>
    </Activity>
    <Activity id='5' name='end'>
    <WorkflowEditor x='691' y='50'/>
    </Activity>
    </WFProcess>
    </Extension>
    Reg/Suveer

  • Chek System and User status during Equipment creation (IE01)

    Hi gurus
    I need to check if the system state I0180-NPRT is set by teh use during the creation of an equipment.
    I tried to use the FM BAPI_EQUI_GETSTATUS and ITO3_EQUIPMENT_READ_STATUS with the exit IEQM0003, but both FM doesn't retrieve any status during the creation of the equipment (IE01), while both work fine during change operation (IE02).
    Someboday has an idea, regarding the right FM to use for solve my issue ???
    Thanks in advance for your help.
    Claudio

    For the first part of your query refer to the technical forums.
    For the second part - refer to Idoc - LOIPRO01, it has a segment for Order status, that should be of interest.
    Attn Moderators
    I think it would be better to move this thread to a technical forum, so the requester can get the most relevant information.

  • Manager for a user object during reconciliation

    Hi All,
    I have a task to reconcile user records from a DB containing manager information in the same table (referencing on itself). I planned to user a Post Process Event Handler to search for a Manager but just realized that I can't be sure that a manager for a user will be in OIM by the time of processing a user.
    What would be a solution for the task?
    Thank you in advance,
    Philipp

    I can think of this,
    Create all users with no manager initially.
    Write a custom scheduled task which will update manager information of all the users.
    Now,
    After all the users are created, execute this custom scheduled task to associate the managers to respective users.

  • Add user to role during reconciliation

    Hi,
    I have this scenario:
    We have a database resource on which we run reconciliation to link accounts to our users in IDM.
    I also have roles that contains this resource. When the reconciliation runs I would like to add the user
    to that role, instead of linking the user to the resource account directly.
    Our problem now is that if users gets linked to the resource, and then gets the role, if the role is removed, the user still has the link to the resource.
    Did that make any sense?
    I'm guessing that I need to use the "per account workflow" to make this happen, but I'm not sure how to do write this workflow.
    Regards,
    Henrik

    Hi Henrik,
    You could do it during reconciliation with a per-account workflow.
    Another approach is to use a regular workflow that lists users with accounts on that target resource and processes each of them to remove any unneeded direct assignments. That is what I went with, and I run the workflow periodically.

  • How to control user updates during trusted/target reconciliation

    Hi All,
    I am new bie to OIM.
    Currently working on OIM 11g R2.
    1. I have user type called 'blind' which is updated by OIM admin.
    2. when I do a trusted/taget recon, I should not update user whose oim user type is 'blind'.
    Note: User type 'blind' is updated by OIM admin. There is no user type called 'blind' in target system while doing trusted system all users will be in status 'alive' or 'dead'.
    Kindly suggest how we can add OIM filter to prevent 'blind' user accounts from being overwritten by trusted reconciliation.
    Appreciate your response

    Hi GP,
    Thank you for the response. Please excuse me for using the terms Live,Dead,Blind.
    But we are not receiving the user Type "blind" from the reconciliation data. We receive only the two states either "live" (active) or dead (disable). Blind is the User status which we set as OIM user type manually and we do not want this blind type user get updated by the reconciliation engine. More over this reconciliation is a GTC reconciliation from CSV feed.
    Please correct me if the recon is of type target reconciliation can I write a Pre-Process Event Handler which will
    a) Get the list of users in OIM whose type if blind
    b) compare the data with the recon data available through event handler, then skip the change.
    Is this possible.
    Regards
    Srinivas

  • Use of user status and business actions

    Hi all,
    I'm new at status profiles, user status and business actions.
    Currently we are using status profiles and user status for orders - but business actions aren't assigned to the user status. In a project I should evaluate whether we can use those business actions.
    After reading a lot of documentations there is still one question left. What are the business-actions for and how can I use them?
    Let's say I've a status profile with following user status with according business actions:
    - status: new;   business action: to progress
    - status: in progress;   business action: to confirm
    - status: confirmed;   business action: decline or close
    - status: closed;   business action: close
    What happens when a user sets the status of an order to "confirmed"? Will be done additional checks for my order? - If yes: Wich checks will be done and exists there an API to effect these checks or to implement additional checks?
    Regards,
    Christian

    Christian;
    If you´re wanting to speak about Status Profile in OP. You can execute whole theses steps in T-code BS02, when in this IMG:
    1. Enter a Status Profile.
    2. Assign the status profile to an Object Type.
    3. Define the User Status.
    4. Assign Business Transactions to user statuses.
    5. Translate the status profile and user statuses.
    You can also to use this function to simulate the status development for a particular object.
    To do this, select a status profile and branch to the screen "Allowed Object Types". Then place the cursor on one of the object types.
    Using the function Extras -> Status simulation, you can simulate the status changes that could be caused by performing various business transactions, or by changing the staus manually, during the lifetime of the object concerned.
    You can also branch directly from simulation to status maintenance for the object concerned, to display information on which transactions are allowed or disallowed in the current situation.
    The log function records all the changes you simulate and allows you to navigate freely to see what effects these are having.
    Status profile info
    Using the function Extras -> Status profile info, you can display a list of all the entries you have made for a particular status profile. The list is structured as follows:
    The first block contains the permitted object types.
    The second block contains the user statuses.
    The third block contains the following information for each user status:
    which transactions it allows
    which transactions it allows with a warning
    which transactions it disallows.
    I hope help to you
    Regards
    Luciano Nobrega

  • Changing User Status by activity confirmation

    Hi Experts,
    In my project , User status is maintained for WBS.
    My client want to Change the User Status of all the WBS when one activity is confirmed  .
    lets get an example: In  project there are WBS A, B and C. In WBS A there are Activity number 1 and 2.
    The WBS has user status Z and X. When Activity 1 is confirmed , all the user status of WBS will be Z.
    When the acvity 2 is confirmed , all the user status of WBS will be X.
    Please help how to do this. is there any enhancement or BAPI.
    BR,
    Morshed Alam

    You have to do development for this. Use BADI "Workbreakdown Update" to change the user status on WBS, whcih can be called during WBS save. The development needs to pick the correct user status from Activities. Status are stored in table JEST.
    Hope this helps.
    Sarang

  • STATUS_UPDATE error to update USER STATUS - Update termination error

    Hi All,
    I am using status_update FM in sales order user exit MV45AFZZ in a perform routine for updating user status in line item for sales order. There are 4 custom statuses created for the sales order line item. 1,2 3, and 4 by configuration. My job is to select one of those based on user selection.
    Scenario: During change order process using  VA02, I have to change the existing status to a third status when user selects the second one. That is for example, in VA02, user selects status 4 from previous status 3, and save, I have to make the status 4 inactive and save the new status 2 instead of 3 though user selected 3. How do I achieve this.?  ????Any programming example is really appreciated. Thanks!!!
    I am right now using STATUS_READ and reading the existing status 4. Then making it inactive using status_update FM. And updating the new status 2 as active one and 3 as inactive again. Two inactive updates and one active update is throwing an update termination error while saving the sales order.
    Any help is really appreciated. 
    Thanks
    Ricky

    Hi ricky,
    For saving any changes you need to have a Z-table.
    In programs we can't store the user selection. In your case you can create a z-table and store the status there and delete the last status. The process would be faster as you will always have one record in the table.
    . One more advantage is you can even track the changes through the Z-table(User who is changing it.)
    Hope this solution will surely help you.
    Cheers
    Suvi

  • User status to prohibit automatic creation of PR

    Hi Gurus,
    I have scenario when project needs to be released in the beginning of the project for incoming order analysis of the project. Now if I release the entire project, the PR is generated automatically, on release. I want to restrict this.
    For this I have created a user status. and I am trying to prohibit the creation of PR from project. But its not working.
    Can anyone please help on this
    Thanks

    Hi,
    I think I should now explain the scenario in detail.
    The PR should be generated on REL , Necessary settings have been done. Now  there is a need to do incoming order analysis, for this project should be released during the beginning only. Now the problem is that due to early release of project all the PR are created.
    But in practical situation this shud not happen, PR is only generated when material is really required.Hence ideally only the desired activites/ WBS should be released as and when required.
    Hence, if I change parameter to Never. No PR would be generated unless someone manually change it to Immediately. There are more than 500 materials on the project. So changing manually is not a good Idea.
    Hope this will clarify
    Thanks

  • How to define user status that forbids editing the document

    Hi All,
    Im working on CRM 7.0
    I need to define a user status say " ON HOLD" . when this user status is set the document should not be edited or changed by anyone.  However as soon as we move to next status document should be editable.
    I configured a user status and in the TRANS column
    selected CLks .
    in the transaction control i have change document set to forbidden.
    The problem is when i set this status on the document , the document is locked as desired and i am not allowed to change the status itself (not desired) .
    How do i configure the status so that i can also switch between on hold  and other user statuses  or  how can i release the On Hold status?
    How do you set the Delete  option in transaction control for any allowed transaction for a user status.
    Thanks In advance!
    Survee

    Robert,
    Thank you for your input.
    We have defined a simple status  where in editing is  not alllowed by validation during save.
    We are controlling the status change from "On hold" to next status  by authorization group.
    Basically if the user has access to the auth group he can change the status to next status.
    Cheers
    Survee

  • User status with reference to characteristic value of the Functional locati

    Hi,
    For a Functional location for which a characeteristic values is maintained as"1",i  want "user status of the mainteance order,when created  to be updated as "XXX".Can any one of you tell me the user exit and code changes for this.Please reply at the earliest.
    EX:A functional location(XXXX) has a Characteristic(xxx) has  value as "1"
    we have created an user status as"xxx" for the order(through status profie).Now,My requirement is
    When i have created a maintenance order for the functional location(XXXX),upon on saving of the order,or Assigning the priority for the maintenance order,i want the user status has to be modified as "XXX".
    Could you please tell us what to do?
    is our requirement will be fulfilled with the exit"IWO10009".If so,please tell us the code to be made>
    Can we map our requirement through "Object dependencies" or any other means to meet our requirement
    you will be highly appreciated
    with regards,
    Joshita

    HI joshita,
    I had a similar issue in the past where i wanted to attach permit to an order based on some characteristic of functional location at user exit 'IWO10002 - Customer check for order release'.
    This will solve your purpose during release of the order.
    You can also use the exit 'IWO10009 - Customer Check for 'Save' Event', this will check irrespective of the status of the order.
    Regards,
    Deepak

  • User Status LKD is active(ORDTMC1001)

    Hi,
    While doing capital purchase order through internal order a message is being appeard as "User status LKD is active(ORDTMC1001).
    What could be the possible solution ?
    Best Regards,
    Samrat Roy

    Dear Waman,
    Whenever I create new Internal Order user status shows PLIM and LKD under Control Data of Internal Order master. Go to Set / Reset and uncheck the tick from status LKD and save the record. Why this status become locked i.e, LKD automatically in every internal order creation ? How it can be removed and during creation of new internal order user status will show only "PLIM". What should be the actual status of Status Profile for Internal Order ?
    Best Regards,
    Samrat Roy

  • 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

Maybe you are looking for