One pr for multiple materials with line items while running mrp

Hi SAP gurus,
              I am config the system for MRP as per my client requerement.
                 We use CBP for different RAW materialsfor example they having a 10 materials for planning,were,
         MRP type is VB,
          LOT size is FX,with Different Reorder points and fix order quantity for all materials,
         My client whant run MRP for all these materials in single time that means they whant multiple item at single levels,
        i soles these requirement with the help of Product Group(sop) and its working but when we running md02 for product group all materials have planed and they give different purchase requistion numbers for all these materials but my client Wants single purchase requistion with line items for all these materials.
     Pls give me the solution for that requirement.
thanks and Regards,
abhi

this is not the way SAPs MRP run works.
Where is the benefit for this?
the requisitions are not even split into header and item table, it is just one table EBAN, and either way you would get exact the same number of records in EBAN.

Similar Messages

  • ALV Report for multiple headers with Line Items

    Hi Sap All.
    here i have got a requirement to change the exisiting Zprogram which writes all the header information with line items in a normal simple report,now i have got to change the program in order to display in an ALV Format .
    in the exisiting program they are using EXTRACT ,INSERT Statement and multiple select statements for getting the values into each field ofheader and line items for writing in a simple report.
    so ijust want to know how i can populate all the data into alv grid.
    can any one help me in this.
    regards.
    Varma

    you have to store all header records in an internal table and all item records in a second table
    then you call function module REUSE_ALV_HIERSEQ_LIST_DISPLAY with both parameters T_OUTTAB_HEADER and T_OUTTAB_ITEM

  • Taking too much time for saving PO with line item more than 600

    HI
    We are trying to save PO with line items more than 600, but it is taking too much time to save. It is taking more than 1 hour to save the PO.
    Kindly let me know is there any restriction for no. of line items in the PO. Pls guide
    regards
    Sanjay

    Hi,
    I suggest you to do a trace (tcode ST05) to identify the bottleneck.
    You can know some reasons in Note 205005 - Performance composite note: Purchase order.
    I hope this helps you
    Regards
    Eduardo

  • How to add the line items while running the VA01

    HI All,
    I want to add the line items while I am running the VA01 t-code(In run time).Could anybody give the FM to create the line items....Its urgent

    Hi ,
    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
    P.

  • UserExit or Customer Exit for F110 - '*' on Vendor Line Item Payment Run

    Dear all,
    Background
    Currently in F110, when processing for vendor payments, the item text ( or segment text) is only printed out when item text begins with an asterik ' * '. The asterik is meant to indicate that this document/item is posted from external system. You may do a F1 on the text field for detail explanation.
    In the event, asterik is not present on the item text even if the text is not blank, it will not be printed at all.
    Here are two OSS notes on the asteriks: 312623 and 1292333.
    Include: F110SFS0_SATZ_KOMPLETTIEREN
    *------- Segementtext
      IF REGUP-SGTXT(1) NE '*'.
        REGUP-SGTXT = SPACE.
      ENDIF.
    Requirement
    User is requesting for item text to be printed at all time, when the text exist, regardless of ' * '.
    Question
    Does anyone know of a user exit / customer exit that i could use to do modification for SGTXT ?
    Would appreciate it, if you could share your suggestions / experiences - on this matter, even if it doesn't need to be resolved through user exits.  Thanks in advance

    BTW..you have fot following exits for F110;
    Transaction Code - F110                     Parameters for Automatic Payment
    Enhancement/ Business Add-in            Description
    Enhancement
    RFFOX074                                Frame for user exit RFFOX074 (in program RFFOCH_U)
    RFFOX075                                Frame for user exit RFFOX075 (in program RFFOCH_U)
    RFFOX081                                Frame for user exit RFFOX081 (in program RFFOF__T)
    RFFOX082                                Frame for user exit RFFOX082 (in program RFFOF__T)
    RFFOX100                                Frame for user exit RFFOX100 (in program RFFOUS_T)
    RFFOX101                                Frame for user exit RFFOX101 (in program RFFOUS_T)
    RFFOX102                                Frame for user exit RFFOX102 (in program RFFOUS_T)
    RFFOX103                                Frame for user exit RFFOX103 (in program RFFOUS_T)
    RFFOX104                                user exit
    RFFOX105                                Frame for user exit RFFOX105 (in program RFFOUS_T)
    RFFOX200                                Frame for user exit RFFOX200 (in program RFFONZ_T)
    RFFOX210                                Frame for user exit RFFOX210 (in program RFFOAU_T)
    RFFOX211                                Frame for user exit RFFOX211 (in program RFFONZ_T)
    RFFOX230                                General program for user exit RFFOX230 (in program RFFOJP_L)
    RFFOX240                                Enhancement for User Exit 240 (RFFOAT_P)
    RFFOX250                                Enhancement for User Exit 250 (RFFODK_E)
    RFFOX901                                Framework for user exit RFFOX901 (in program RFFOM100)
    RFFOX902                                Framework for user exit RFFOX902 (in program RFFOM100)
    FDTAX001                                Enhancement to Transaction FDTA (event after the download)
    FEDI0002                                Function exits for EDI DOCS in FI - Incoming pyt adv.notes
    FEDI0003                                Function exits for EDI docs in FI - Save PEXR segments
    FEDI0004                                Function exits for EDI docs in FI - particular events
    FEDI0006                                Function Exits for EDI-docs in FI: Save IDCR Segments
    RFFOX003                                Frame for user exit RFFOX003 (in program RFFOM100)
    RFFOX041                                Framework for user exit RFFOX041 (in program RFFOBE_I)
    RFFOX042                                Framework for user exit RFFOX042 (in program RFFOBE_E)
    RFFOX043                                Framework for user exit RFFOX043 (in program RFFOBE_D)
    RFFOX061                                Frame for user exit RFFOX061 (in program RFFOCH_P)
    RFFOX062                                Frame for user exit RFFOX062 (in program RFFOCH_P)
    RFFOX063                                Frame for user exit RFFOX063 (in program RFFOCH_P)
    RFFOX064                                Frame for user exit RFFOX064 (in program RFFOCH_P)
    RFFOX065                                Frame for user exit RFFOX065 (in program RFFOCH_P)
    RFFOX066                                Frame for user exit RFFOX066 (in program RFFOCH_P)
    RFFOX071                                Frame for user exit RFFOX071 (in program RFFOCH_U)
    RFFOX072                                Frame for user exit RFFOX072 (in program RFFOCH_U)
    RFFOX073                                Frame for user exit RFFOX073 (in program RFFOCH_U)
    Business Add-in
    FI_BSTM_MC_EXIT                         FI Account Statement: Exit from MultiCash Conversion
    FI_F110_SCHEDULE_JOB                    F110: Check before scheduling a proposal/update run

  • One inspection lot for multiple materials of purchase order line items

    Hi All,
    My client requirement is one inspection lot for multiple materials of purchase order line items.
    Please share your thoughts.
    Thanks in advance for early reply.
    Regards,
    Jishu

    I totally agree with Amol.
    I don't think I would touch that development nor would I ever tell a client it could reliably be done through development.
    Knowing what I know about the table structures, I don't think you could create any development for this that could use a significant amount of the existing tables and functionality.  I think you'd have to create all your own Z tables and basically rebuild the functionality.  Tying it back in with SAP data will be difficult.
    You're even looking at all custom screens for your results recording and UD as well.  And if you have follow-on functions like batch classification requirements, batch determination, COA publication, results copy functions, use of DMR and sampling procedures, physical samples, quality notifications, etc. etc.. you could be looking a whole lot of development.
    Craig

  • Is it possible to combine multiple Pur Reqs for multiple materials to one vendor into one PO through MD07?

    We have material planners who use MD07 (traffic signal screen) Stock/Requirements List, Collective Access tab to review material requirements by MRP Controller.  Once the list is created, they select individual materials and review them in MD04.  In a lot of cases, Purchase Reqs (PRs) are reviewed and adopted into POs individually for each material.  Sometimes they will combine multiple PRs for one material into one PO.  This is a good practice.  However, from what I have found, it is not possible to combine multiple PRs for multiple materials into one PO.  If this was done it would dramatically reduce the number of POs that we are issuing to suppliers.  Problem statement:  We issue too many POs which causes additional influxes down the line (receiving dock/goods receipts processing, receiving issues, invoices, invoice issues, etc.).  Does anyone know of a way to address this problem without a major overhaul in approach or customization of the system?  Thank you in advance!   

    Hello Michael
    As far as I know, this is not possible directly from MD07, only from the MM transactions.
    The following thread suggests the following procedure to convert several PRs into one PO:
    Conversion of multiple PR into single P.O
    Drag and drop the first PR from the item overview to the shopping card on top of ME21N,
    then open the PO detail delivery schedule tab and drag  and drop all other PR to the shopping card shown  in the schedule tab
    You can use the same procedure, calling the order conversion from MD07 and then drag and drop another PRs into this PO.
    BR
    Caetano

  • One tray for multiple button group items

    Hi,
    I have 3 button group items in my templaate ,in the propoerties of these button grps the tray is on .NOw I can see 3 trays when I execute my template instead I want to have one tray for these 3 button group items . How is this possible?
    THanks
    Sany

    OK, I'm having trouble again. I need multiple items to drag
    to one target. I'm putting all my actionscript in the same frame,
    and here's how it looks:
    stop();
    name_mc.onPress = function():Void {
    this.startDrag(true);
    name_mc.onRelease = function():Void {
    this.stopDrag();
    if (eval(this._droptarget) == safe_mc) {
    this.swapDepths(this._parent.getNextHighestDepth());
    this.removeMovieClip();
    address_mc.onPress = function():Void {
    this.startDrag(true);
    address_mc.onRelease = function():Void {
    this.stopDrag();
    if (eval(this._droptarget) == safe_mc) {
    this.swapDepths(this._parent.getNextHighestDepth());
    this.removeMovieClip();
    And I'm getting the following error message:
    **Error** Scene=Recap, layer=actions, frame=1:Line 21:
    Statement block must be terminated by '}'
    address_mc.onRelease = function():Void {
    **Error** Scene=Recap, layer=actions, frame=1:Line 27: Syntax
    error.
    Total ActionScript Errors: 2 Reported Errors: 2
    Do you know what I'm doing wrong?

  • Availability Check at Multiple Plants for the Sales Order line Item.

    Hi Friends,
    We are having two plants, Plant A and Plant B. Plant A is used to issue the orders to the vendors and stock them, while Plant B is used to manufacture the Product and Stock.
    When we create the sales order, we want to check the Current Stock Plus Incomming Purchase order stock for plant A and also check current stock plus Production orders in plant B.
    for ex if the current stock is 100 in Plant A and No physical stock in Plant B but there are some production orders for 400 Qty which will be ready in 1 week.
    If i create a sales order for 500 qty which is scheduled for delivery 10 days later.  then we want to commit to the customer ( Looking at both the plants stock situation )  the system should check the stock availability for both the plants and automatically create two different line items , Line item 1 for plant A and line item 2 for plant b.
    I know there is a user exit for Multiple plant selection USEREXIT_PLANT_SELECTION  in program RV03VFZZ. The Description of the USer exit says ( This user exit may be used to provide a list of plants for which availability is to be checked)  But we have never used this one. Will this user exit do exactly what i want ??
    Did any of you, have used the above User exit in your implementations ? If so please let me know whats the purpose of this user exit
    Your reply is much appreciated.
    Thanks & Regards
    Srinivas

    Hi
    I dont know about the userexit which you are referring about
    But this is not available in R3 The system makes a Availability Check only in the plant which has got determined in the item details shipping tab and stops there
    The same is available in APO
    If there are 2 plants say 1000 and 2000
    In sales order the plant determined is 1000 and there is no stock
    In R3 system stops there
    But in APO  system checks the plant 2000 and if stocks are available it creates an STO in the background automatically from 2000 to 1000 if configured accordingly
    Even if the material is maintained in 10 plants the system will make a  Availability Check at all 10 plants and act accordingly
    Regards
    Raja

  • How to maintain One product cost collector for multiple materials and configuration setting

    Hi experts,
    my requirement is that i want to maintain one product cost collector for multiple materials ans also i want to know the configuration setting for the same.
    I have used KKF6N but it is not working in my case. I went through KKF6M also but there i found multiple cost collectors.
    please guide me in the same.
    Thanks in advance.

    Hi Shripad,
    you cannot assign same  Product cost collector to different material.
    Because you creating cost collector for material combination of material /production version,material /Bom Routing.
    so please create individual cost collector for every material.
    if you have any query kindly revert back.
    Please mark the answer as helpful if it is helpful to you.
    Because march 5 onwards scn has stopped awarding points to liked content.
    Starting now: No more points for likes on comments/replies
    Thanks & Regards
    Sandeep Kumar Praharaj

  • Field Char(255) for texts in accounting line item

    Hi Experts,
    I need a field with type/len char(255) for texts in accounting line item.
    I know I can use Long Text (EENO_DYNP-ZEILE) but it is not shown in TCode FAGLL03 and that is my need.
    Please help me.
    Best regards,
    Itajaci Júnior

    Hi Paul,
    Thanks for your reply.
    I already have these fields active, but unfortunately the sum of their sizes is not enough. Also, I would have to split the text into four fields and I think that it is not the best option for the customer.
    One more time, thanks for your answer.
    Any other ideas? It can be a Z field. The most important is that it be shown in Tcode FAGLL03.
    Regards,
    Itajaci Júnior

  • MRP FOR MULTIPLE MATERIALS

    Dear cons
    For MRP we are using t-CODE- md62 for requirement demand.Then we have created a z- t-code which is a replica of t-code- MD02. In MD02 T-CODE one single material option is availble. so we chose one BDC of new t-code- ZMD02. In this Z-t-code it is possible to upload multiple material.But the problem is for each material the system is creating an individual Purchase requisition even though I have uploaded multiple materials, Our motto is to create  a single purchase requisition for these multiple material just like the t-code- ME51N where entering of multiple items .are available. So is there any standard T-code availble to create a single pur. requisition for multiple materials in one time.Any advice for other option.

    Hi Nirupama,
    In standard system we dont have any such facility/transaction to create a single PR for a bulk of material. Which ever T-codes are available to run MRP for multiple materials (ex:MD01), those give individual PR for each individual material. You may refer to SAP notes also for this.
    Regards,
    sachin

  • Manual TO for multiple materials

    Hi All,
    I want to create manual transfer order for multiple materials in a single TO, but when I use LT01 I have the option of entering only one material code. So, please tell me how can I create a transfer order with multiple material codes manually...
    Thanks in advance..
    Reg
    Noopur

    Hi,
    In standard system you can use only LT01 and LT10 for creating manual TO. In LT10 you can select several materials (quants) at once (but e.g. you cannot change the quantity).
    If you want something better, you have to go to development in my opinion.
    Regards,
    Csaba

  • Customer/Vendor A/C with line item details and with opening and closing Bal

    Dear Sir / Madam,
    Is it possible to have a customer and / or vendor Sub-Ledger account-
    with line item details and with opening and closing balance detail
    for a particular period.?
    Regards
    Chirag Shah
    I thank for the given below thread which has solved the same problem for G/L Account
    Re: Report to get the ledger printout with opening balances

    Hello Srinujalleda,
    Thanks for your precious time.
    I tried the referred T-Code
    But this report is not showing Opening balance, closing balance detail.
    It only gives transactions during the specified posting period and total of it.
    Please guide me further in case if I need to give proper input at selection screen or elsewhere.
    Client Requires Report in a fashion
    Opening Balance as on Date
    + / -  Transactions during the period
    = Closing Balance as on date
    As that of appearing for G/L Account by S_ALR_87012311
    Thanks once again & Regards
    Chirag Shah

  • Work Order to cost center settlement with line item detail

    Iu2019m having difficulty finding a method to settle from a work order to a cost center with line item detail.  When an order is settled with KO88 or KO8G the total value for that work order/cost element combination is combined and posted to the cost center as a lump sum with the description of CTR\######.  Users would like to see the individual values that posted to the work order in a cost center report such as  KSB1.
    I donu2019t see anything in the settlement rule, settlement profile or allocation structure that will allow line item settlement from work order to cost center.     Is line item settlement possible when settling to a cost center?   Is there an alternate way to see these expenses as line items in KSB1?
    Thanks,
    Jeff

    Thanks Christian,
    We've defined an allocation structure that we use for Project System and Work Order settlement and have Receiver Categories established as FXA, CTR and WBS with "by Cost Element"  checked.  Work order costs do settle to the cost center entered in the settlement rule, the problem is it combines all items values as a single amount when posting to the cost center.
    For example:  
    expenses post to the work order under cost element 500000 for $500, $200, $300 and cost element 600000 for $250 and $250.  The settlement rule says to settle to cost center 170000.  When the settlement takes place cost center 170000 is debited $1000 to cost element 500000 and $500 to cost element 600000.  We would prefer to see individual posting of $500, $200, $300 to 500000  and $250, $250 to 600000.
    Thanks,
    Jeff

Maybe you are looking for