E Rec - Approval for requisition, position creation

Hi Gurus,
I understand that we can attach positions created in OM to a requisition at the time of creating the requsition.
Can we create positions via E-rec process & the same can be release after workflow is approved 
Please confirm that is thr any standard functionailty for below
For different requisitions created approval is clubed and only one approval request goes to the assigned person in UWL
For each requistion different approvers are assigned, eg: For HR>HR Head, Finance> Finance Department Head then Competent Authoriy.
Where and how to incorporate checks for candidate to apply & restrict for an opening. eg: Trainees requirement and checks for age has to applied- only 30 years and below can apply. The system should restrict all other candidates on this validation.
Restrict an candidate to apply only against a Reference no. or position title & restrict unsolicited applications.
Please assist with your valuable comments on the above.
Regards

Hi Pavan & Vijaya,
   I also have requirement of modifying Standard Workflow WS WS51800008.
  I have done following setting in SPRO.
SAP E-rec->Technical Settings>Workflow--> Click On documentation of Set Up Approval Process for Requisition (Workflow) and there it has given you the clear Explanation about defining parameters in the Txn WF_EXTSRV
after this i did GENERATE TASK  and  it generated a new TASK. but in this config it ask for Logical system and i am not  sure  which logical system  i have  to give   so  i have kept  is  blank..
I have also done URL settings in WF_Handcust.
Also  in SICF when i tested my service /sap/bc/bsp/sap/hrrcf_approval/application.bsp it gives me following error...
SAP Note
The following error text was processed in the system:
BSP Exception: Das Objekt default.htm in der URL /sap/bc/bsp/sap/hrrcf_approval/default.htm?sap-client=668&sap-sessioncmd=open ist nicht gültig.
so gurus  kindly suggest me  what  should  be  done to make this workflow  running...also i m modifying this workflow to add  1 dialog  task   so do i need to make this entry foe this task in SWFVISU??
thanks in advance....

Similar Messages

  • Approval for Material Master Creation !

    Dear All ,
    My requirement is to have approval process for Material master. is it possible.?
    My Client is expecting approval process same like PO ( release strategy )
    Is there any standard approval  process for every masters which are  created as part of MM transactions.
    Can it  be achieved by means of any workflow.?
    Thanks
    Jinoy

    Hi,
    Yes it can be achieved by Work flow & also through the Enterprise Portal development.
    If you have Workflow consultant you can take a help in setting up the approval for Material master creation.
    If you want high fund & centralization of Material master you can go for EP development but Cost & effort will be on higher side.
    Discuss with your Workflow consultant he will help you.
    rgds
    gsc

  • HCM/OM workflow template - approval for creating positions

    Hi Guys,
    My requirement is to create a custom workflow for the approval process of creating positions. I have the follwing questions:
    1. Is there any workflow template that can be used?
    2. What BO should be used?
    3. On what event should the WF be triggered?
    Many Thanks in advance,
    Cristian

    Please check with these Business objects
    PDOTYPE_S  Position
    PDOTYPE_SH HR Position
    Thanks
    Arghadip

  • Report - who is the current approver for purchase requisition

    Hi Experts
    Is there a report that can give information the status / who is the current approver for purchase requisition?
    currently if we open the PR directly, we can only know the release strategy, release code, status of approver, but we cannot have the information who is the person that should approve this PR.
    Thanks in advance
    Prashanth.v

    Hi All.
    Unfortunately we want to have this information for our end user, and they will not have the access to SE16.
    Another thinks is from CDHDR we will have the information if changes are made in PR. So it will give information user that already approve the PR
    What we want to have is a report of outstanding PR (not yet released) that have information who is the user (the user complete name / user id)  that should approve the PR.
    Thanks In Advance
    Prashanth.Venkategowda

  • Configuration to setup approval for vendor changes and creation

    Can anyone help to know where to switch on the approval for vendor changes and creation?

    Just a quick thanks that it worked, aesiris.
    Also on the that page:  https://wiki.archlinux.org/index.php/Po … Management
    i2c device power management can be managed with very much the same rule structure:
    ACTION=="add", SUBSYSTEM=="i2c", TEST=="power/control", ATTR{power/control}="auto"
    Can't for sure say the same for spi devices, since I apparently have none.  I'd edit that page, but I can't.

  • Is it possible Line level approval for purchasing requisition in AME?

    hi
    is it possible Line level approval for purchasing requisition  in AME?
    so that send each line to separate approver ?

    If using AME, it should be possible. Check AME Guide for POs for details. Let me know if you run into issues.
    Thanks
    Shree

  • Approval process for requisitions after RFQ

    Hi there
    We are using the classic scenario to purchase items.  In many cases these items require an RFQ process to be followed to determine vendor and price.  The business requires that after a price change the initial shopping cart is updated and if the price is significant it goes through re-approval.  Has anyone got any suggestions on how this could be done cleanly in the system?
    My one thought is to combine the SC and P Req approvals - and final approval only occurs when the RFQ is complete and the correct information is added to the SC.  Is this possible?
    The business will not accept change release procedures on the purchase requisition due to high maintenance. 
    Thanks
    Roz

    Hi Venkatesh,
    1) Is it possible to read comments in UWL on a button Click? Is there any API available to achive this?
    Ans: There are no APIs as fas as I know. Normally you see comments after clicking the feedback button in the approvers inbox.
    2) If I store this comments in a repository, how can I set approver for that comment?. (Because approver is varying for each respository)
    Ans: You are having different reps on the basis of different criteria. Take this criteria also as input from user in the comment input form and place the comments in separate comment repositories.
    3) If Comments gets approval, it is needed to be display in comments column in KM Navigation iView.Is it Possible?
    Ans: I suggest you to make your own navigation iview having the "comments" column (or check if there is some configuration required to show comments on docs in a rep). You have to device a way for catching the "Approve" event and then make the contents of Comment repository visible in the navigation iview.
    Please see this [blog|https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1424].
    I know this is a complex solution.
    But, this is all what I have got.
    Hope it helps.
    Regards,
    Sumit

  • Configuring Email notifications for approval of requisitions and Pos

    Configuring Email notifications for approval of requisitions and Pos - Using the EBS Server to send the mails as opposed to separate mail-server

    For sending emails, you have to setup the workflow notification mailer.
    Once this setup is done you can send approval worklist in mail and also it can be approved. ( If PO setup is done.)

  • Process Controlled Workflow - 1-step approval for shopping cart approval

    Hi,
    I have configured a one-level approval for SC (Process Controlled Workflow):
    Object Type: BUS2121
    Additional 1 level under schema: 3C_SC_600_000 (the last level is the automatic approval)
    Level Type: Approval with completion
    Eval ID: 0EV_SC_SL1
    RR Name: RR_SPENDING_LIMIT_APPROVER
    RR Param: USTONY.Y (I hardcoded it using my user ID, for the moment)
    Task ID: 40007953 (I have checked, it's generalized as well)
    Decision Type: Item-based decision for entire document
    For PPOMA_BBP:
    Under my org unit (Position):
    Approval Limit: 1000
    Output Limit: 1000
    I didn't do any BADI implementations yet.
    During creation of SC by other user, before "Order" the SC, the approval preview can show correctly that the Processor is as indicated in the config.
    Once the SC is ordered, the whole step is gone and the event linkage becoming delinked (because there is error, and according to the config in SWEQADM).
    However, I cannot find the workitem (no workitem generated) and SLG1 does not give any clue whatsoever.
    I tried debugging method APPROVAL_LIMIT, and it seems fine as well.
    Please help, what did I do wrong here?
    Thanks,
    Tony Y

    Hi Sahil,
    I even changed to first process level to:
    Level Type: Approval
    Eval ID: 0EV000
    RR Name: RR_MANAGER
    RR Param: (Blank)
    Task ID: 40007953 (I have checked, it's generalized as well)
    Decision Type: Decision for entire document
    Under PPOMA_BBP:
    I made myself as a head of the org unit with the role manager.
    The requester is "Exclude" the role manager.
    The agent can be determined now.
    But the workitem ID is still cannot be generated. It's always no workitem generated.
    Please everyone, any help?
    Thanks in advance,
    Tony

  • E Recruitment : Requisition - Position Validity issue

    Hi All,
    In Requisition creation, I am trying to assign a Position ID in Org Structure assignment Tab.
    When I search for position ID here, in the result of search list it also shows the positions whose status is NOT "vacancy open" as on today.
    If the position's status was "Vacancy Open" in the past, but not valid as on today's date, still that position shows in the search list. Which ideally it should not.
    Any clue will be appreciated.
    Thanks.
    Tejas

    Hello Tejas,
    it is standard behaviour of sap e-recruiting to allow the assignment any position, a vacancy is not required.
    When searching for positions there should be a checkbox to search for vacant positions only. This should reduce your result list.
    Best Regrads
    Roman

  • Customization to Add Approver to Requisition Approver List

    Hi
    We use a Position Hierarchy to determine the Approver List for a PO Requisition Approval
    However we also use Project Costing, and would like to dynamically add the Project Managers into the Approver List for Requisition lines coded to their Projects.
    Does anyone have any experience doing this ? Know of any Open API calls that will allow this?
    I have been through the Workflow and have designed the Process flow changes required, but cannot find any documentation on "dynamically" adding an additional approver into the Approver List.
    Thanks

    I have completed work on this and it will require use of the Applications Framework to add in the appropriate user. You will need to work with the Controller for the page as well as the AM for some validation.
    In short you need to complete Applications Framework customisations to get this information.

  • Need RFC/BAPI to Create Requisition,Position, Hiring an Employee

    Hi,
    I need RFC/BAPI to Create Requisition,Position,Hiring an Employee.
    Regards,
    R.Ragu

    Hi,
    For creation of a Posiotn you can use FM 'RH_OBJECT_CREATE'.

  • PURCHASING-How to change the next approver for the Purchase Requistion(PR)-

    Hi All,
    Could you please let me know how to change the next approver for the Purchase Requistion(PR) from User "X" to "Y", as Y was manager of "X" and 'X' left the organization. how can i acheive this? can you please let me know the process ?
    Thanks,

    Hi,
    You have not mentioned the version you are using (11i or R12).. Are you using iProcurement... ? Are you using positional or Employee-Supervisor hierarchy..?
    Your question : How to change the next approver for the Purchase Requistion(PR) from User "X" to "Y", as Y was manager of "X" and 'X' left the organization.
    Ans: You can achieve this through below workarounds
    - Through *"Mass Update of Requisitions" functionality* (Conc. request) you can update the Approver name from User "X" to "Y" for existing PRs.
    - Replacing the Supervisor name of the requestor/requisitioner in the HR record (assignment) from User "X" to "Y"..
    Hope it helps.
    Kind Regards,
    S.P DASH

  • User Exit for ME21 PO Creation at the time of saving--Urgent

    Hi,
    Can some one help me out in finding the user exit for PO creation at the time of saving.
    The Requirement is:
    I need to create a custom field in EKKO table.
    After appending the structure with the field to the EKKO table, i need to create a PO.
    Now i need to update the field which has been created at the time of pressing the SAVE button.
    I need to update the EKKO table it self.
    I could find the user exits but none of them have the EKKO table either in Changing or in Tables.
    Thanks,

    Hi,
              You may want to check this user exits.
    EXIT_SAPMM06E_012 - Check Customer-Specific Data Before Saving
    EXIT_SAPMM06E_013 - Update Customer-Specific Data in Purchasing Document
    Here is the list of available user exits for ME21.
    EXIT_SAPMM06E_001 - Other Number Range or Own Document Number
    EXIT_SAPMM06E_004 - User Exit for Cust.-Specific Control of Import Data Screens in Purchasing
    EXIT_SAPMM06E_005 - Field Selection Control: Vendor Address Screen
    EXIT_SAPMM06E_006 - Export Data to Customer Subscreen for Purchasing Document Header (PBO)
    EXIT_SAPMM06E_007 - Export Data to Customer Subscreen for Purchasing Document Header (PAI)
    EXIT_SAPMM06E_008 - Import Data from Customer Subscreen for Purchasing Document Header
    EXIT_SAPMM06E_009 - Reset Customer Data at Beginning of New Document (Without Dialog)
    EXIT_SAPMM06E_012 - Check Customer-Specific Data Before Saving
    EXIT_SAPMM06E_013 - Update Customer-Specific Data in Purchasing Document
    EXIT_SAPMM06E_014 - Read Customer-Specific Data when Importing Purchasing Document
    EXIT_SAPMM06E_016 - Export Data to Customer Subscreen for Purchasing Document Item (PBO)
    EXIT_SAPMM06E_017 - Export Data to Customer Subscreen for Purchasing Document Item (PAI)
    EXIT_SAPMM06E_018 - Import Data from Customer Subscreen for Purchasing Document Item
    EXIT_SAPMM06E_020 - User Exit: Change Document for Requisitions (Conversion into PO)
    EXIT_SAPMM06E_021 - Fulfillment of Target Value: Release Orders Against a Contract
    <b>Reward points</b>
    Regards

  • What are the User Exits for Sales Order creation process?

    Hi,
    what are the User Exits for Sales Order creation process? how can I find them?
    thanks in advance,
    will reward,
    Mindaugas

    Please check this info:
    User Exits In Sales Document Processing
    This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
    Involved program components
    System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
    MV45ATZZ
    For entering metadata for sales document processing. User-specific metadata must start with "ZZ".
    MV45AOZZ
    For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ".
    MV45AIZZ
    For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ".
    MV45AFZZ and MV45EFZ1
    For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.
    User exits in the program MV45AFZZ
    The user exits which you can use for modifications in sales document processing are listed below.
    USEREXIT_DELETE_DOCUMENT
    This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
    For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
    The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
    USEREXIT_FIELD_MODIFICATION
    This user exit can be used to modify the attributes of the screen fields.
    To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
    The usage of the field groups (modification group 1-4) is as follows:
    Modification group 1: Automatic modification with transaction MFAW
    Modification group 2: It contains 'LOO' for step loop fields
    Modification group 3: For modifications which depend on check tables or on other fixed information
    Modification group 4: is not used
    The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
    This FORM routine is called up by the module FELDAUSWAHL.
    See the Screen Painter manual for further information on structuring the interface.
    USEREXIT_MOVE_FIELD_TO_VBAK
    Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
    The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
    USEREXIT_MOVE_FIELD_TO_VBAP
    Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".
    The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
    USEREXIT_MOVE_FIELD_TO_VBEP
    Use this user exit to assign values to new fields at the level of the sales document schedule lines.
    The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
    USEREXIT_MOVE_FIELD_TO_VBKD
    Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document".
    The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
    USEREXIT_NUMBER_RANGE
    Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
    The user exit is called up in the FORM routine BELEG_SICHERN.
    USEREXIT_PRICING_PREPARE_TKOMK
    Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
    USEREXIT_PRICING_PREPARE_TKOMP
    Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
    USEREXIT_READ_DOCUMENT
    You use this user exit if further additional tables are to be read when importing TA01 or TA02.
    The user exit is called up at the end of the FORM routine BELEG_LESEN.
    USEREXIT_SAVE_DOCUMENT
    Use this user exit to fill user-specific statistics update tables.
    The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
    Note
    If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
    USEREXIT_SAVE_DOCUMENT_PREPARE
    Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
    The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
    User exits in the program MV45AFZA
    USEREXIT_MOVE_FIELD_TO_KOMKD
    Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
    USEREXIT_MOVE_FIELD_TO_KOMPD
    Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
    USEREXIT_MOVE_FIELD_TO_KOMKG
    Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".
    USEREXIT_MOVE_FIELD_TO_KOMPG
    Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
    USEREXIT_REFRESH_DOCUMENT
    With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.
    For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.
    The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.
    The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
    User-Exits in program MV45AFZB
    USEREXIT_CHECK_XVBAP_FOR_DELET
    In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
    USEREXIT_CHECK_XVBEP_FOR_DELET
    In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).
    USEREXIT_CHECK_VBAK
    This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.
    USEREXIT_CHECK_VBAP
    This user exit can be used to carry out additional checks (e.g. for completion) at item level.
    USEREXIT_CHECK_VBKD
    The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.
    USEREXIT_CHECK_VBEP
    This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
    USEREXIT_CHECK_VBSN
    You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
    USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
    USEREXIT_FILL_VBAP_FROM_HVBAP
    You can use this user exit to fill additional fields in the sub-item with data from the main item.
    USEREXIT_MOVE_FIELD_TO_TVCOM_H
    You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
    USEREXIT_MOVE_FIELD_TO_TVCOM_I
    You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
    User-Exits for product allocation:
    The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
    USEREXIT_MOVE_FIELD_TO_COBL
    Option to include new fields in structure COBL.
    USEREXIT_COBL_RECEIVE_VBAK
    Option to assign values from the document header to the new fields.
    USEREXIT_COBL_RECEIVE_VBAP
    Option to supply values from the item to the new fields.
    USEREXIT_COBL_SEND_ITEM
    A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).
    USEREXIT_COBL_SEND_HEADER
    A changed field can be copied from the structure to the header (see source text MV45AFZB)
    USEREXIT_SOURCE_DETERMINATION
    You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.
    USEREXIT_MOVE_FIELD_TO_ME_REQ
    With this user exit you can include additional fields for the following fields:
    EBAN (purchase requisition)
    EBKN (purchase requisition-account assignment)
    USEREXIT_GET_FIELD_FROM_SDCOM
    Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.
    USEREXIT_MOVE_WORKAREA_TO_SDWA
    You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.
    User-Exits for first data transfer:
    The following user exits can only be used for the first data transfer.
    Note
    Only use the user exits if the names/fields do NOT have the same name.
    USEREXIT_MOVE_FIELD_TO_VBAKKOM
    Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)
    USEREXIT_MOVE_FIELD_TO_VBAPKOM
    Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)
    USEREXIT_MOVE_FIELD_TO_VBEPKOM
    Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)
    USEREXIT_MOVE_FIELD_TO_VBSN
    You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
    USEREXIT_MOVE_FIELD_TO_KOMKH
    You can use this user exit to include new fields for batch determination (document header).
    USEREXIT_MOVE_FIELD_TO_KOMPH
    You can use this user exit to include new fields for batch determination (document item).
    USEREXIT_CUST_MATERIAL_READ
    You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)
    USEREXIT_NEW_PRICING_VBAP
    Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.
    USEREXIT_NEW_PRICING_VBKD
    Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.
    User-Exits in Program MV45AFZD
    USEREXIT_CONFIG_DATE_EXPLOSION
    The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
    User exits in the program FV45EFZ1
    USEREXIT_CHANGE_SALES_ORDER
    In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
    If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
    User-Exits in Program RV45PFZA
    USEREXIT_SET_STATUS_VBUK
    In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
    The following workareas are available for this user exit:
    VBUK (header status)
    FXVBUP (item status)
    FXVBUV (Incompletion)
    USEREXIT_SET_STATUS_VBUP
    In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
    The following workareas are available for this user exit:
    FXVBAP (Item data)
    FXVBAPF (Dynamic part of order item flow)
    FXVBUV (Incompletion)
    USEREXIT_STATUS_VBUK_INVOICE
    You can use this user exit to influence billing status at header level.
    User exits in the screens
    Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
    Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
    For field transports, you do not have to make changes or adjustments.
    Example
    A new field, VBAK-ZZKUN, should be included in table VBAK.
    If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
    User Exits in Program MV45AFZ4
    USEREXIT_MOVE_FIELD_TO_KOMK
    You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
    USEREXIT_MOVE_FIELD_TO_KOMP
    You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.
    User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs
    EXIT_SAPFV45P_001
    You can use this user exit to decide whether intercompany billing data is used in the profitability segment for cross-company code sales, or whether the data comes from external billing (external customer, sales data from the selling company code.
    Regards
    Eswar

Maybe you are looking for