Source determination in Purchase Requisition

Hi techies
Iam using the BAPI BAPI_PR_CREATE to create a purchase requisition. I have passed 'X' to auto source of prheader parameter of the BAPI but once the PR is created then if I check the source determination check box it is not selected.
Thanks in advance.

Hey Harini,
    Check the change parameter also marked  to 'X' in the importing structure PRHEADERX and field AUTO_SOURCE.
Regards,
Saravanan M

Similar Messages

  • Item category determination during Purchase Requisition creation from APO

    I’m creating a  SNP Purchase Requisition in APO and when it is  published to R/3, a Purchase Requisition document is created in R/3.
    When this PR is created in R/3, I want the Item Category to be determined based on the Material master Special Procurement Type. ( eg: I’d like the Item category to be ‘L’ if the Material master Special Procurement Type = 30 (Subcontracting) ). But by standard, this field is coming as ‘Blank’ and this field could only be populated during the creation from APO.
    I found a user exit ( CIFPUR02 :  Enhancement of Purchase Order Interface (Inbound) ) on R/3 where I tried to populate the Item Category, but  when I do this, all the purchase order related data is getting deleted and hence no PR’s are getting created in R/3.
    Could anyone please tell me if this could be resolved using configuration and if not any  tips to do this technically would be very helpful.
    Thanks,
    Harsha

    Hi Karun,
    This is the code i'm using...
    select single * from marc into lit_marc
    where  matnr = c_eban-matnr
    and    werks = c_eban-werks.
    append lit_marc.
    read table lit_marc with key matnr = c_eban-matnr
                                 werks = c_eban-werks
                                 sobsl = 30.
      if sy-subrc = 0.
      c_eban-pstyp = '3'.
      endif.
    Here sobsl = 30 is the Special procurement type
    But when i try to populate c_eban-pstyp = '3', during the creation of Purchase Requisitions in R/3, in the program SAPLEMPI -> LMEPIF01
    this condition is encountered which deletes all the data in the tables that is used to create Purchase requisitions.
    <i>* get rsnum in the case of subcontracting
          IF XEBAN-PSTYP EQ PSTYP-LOHN AND                      "RB240999
             EXITFLAG_ORDID IS INITIAL.                         "RB240999
    refresh all component tables
            CALL FUNCTION 'ME_COMPONENTS_REFRESH'
                 EXCEPTIONS
                      OTHERS = 1.</i>
    Could you please suggest me anything to get around this.
    Thanks,
    Harsha

  • Batch Determination for Purchase Requisitions

    Hi,
    Is it possible upon MRP, a batch determination occurs when creating the Purchase Requisition? So that even during PR, the batch number is already indicated.
    Thanks,
    Lee

    Hi
    You can create batch only under the following scenarios (as given below) and it is not logically correct to determine the batch during creation of batch. Generally we create it during GR and in specific cases it can be assigned during purchase order.
    The system creates a batch master record in the background in the following procedures:
    The first time goods are received for a batch
    During creation of a process or production order
    When a usage decision is made in quality management
    During a recurring inspection
    For transfer postings (when you want to split a batch, for example)
    When creating a purchase order
    Reward if useful
    Regards
    edwin

  • Output Determination for Purchase Requisition

    Hello
    I would like to know how do we configure the output messages for PReq's.
    Regards
    Sameer

    Hi Sameer
    I do not think, it can be explained/trained here.
    You will need an ABAPer for this
    Alternatively, if you just want items oevrview in a PR, you can do this:
    In Txn ME53N, there is a 'printer icon' above item overview table. You can click that to take printout. Or there is one more icon next to printer ('Views'). You can use that also to take items printed. Explore these icons.
    Best regards
    Ramki

  • Issuing storage location for purchase requisition

    Hi All,
    Anyone knew how to have a default issuing storage location on purchase requisition (source of supply tab) created through MRP?
    Thanks.
    Jump

    Hi,
    For this you need to implement BADI MD_EXT_SUP in combination with special procurement type 40 or 45.
    Documentation of this badi:
    Business Add-In for Determination of Issuing Storage Locatio
        Use
        You can use this Business Add-In (BAdI) to control the determination of
        the issuing storage location during stock transfer processing.
        The BAdI is used in the following components:
        Material requirements planning (PP-MRP)
        The BAdI runs both for manual creation of externally procured planned
        orders, and in the MRP during creation of stock transfer procurement
        proposals.
        Purchasing (MM-PUR)
        The BAdI runs as part of the source determination for purchase
        requisitions and during purchasing.
        Standard settings
        o   The Business Add-In is not active in the standard.
        o   The Business Add-In cannot be used multiple times.
        Example
        Sample coding is stored.
        Further notes
        Documentation on BAdI method GET_SUPPLYING_SL
        Documentation on BAdI method GET_PLIFZ
    MZ

  • User Exit/BADI for Purchase Order and Purchase Requisitions

    HI,
    I have a requireent where i have to check the the user does not enter both Subitems and Over a Limit for a Service Purchase Requisition.
    Is there a User Exit or Badi that i can use where this information is availaible.
    also i have to check that release strategy is assigned to every purchase order where the version has been completed.
    Is there a User Exit or Badi where Information of EREV table is availaible.
    Regards,
    Tarun Bahal

    For Purchachase requisition , the BADIs and USER EXITS are
    ME_COMMITMNT_PARKING BAdI for Redefining Commitment Interface When Parking
    ME_MEREQ_PARKING BAdI Purchase Requisition: "Hold"
    ME_REQ_HEADER_TEXT Copy Header Text: Enjoy Purchase Requisition
    try with the above BADI's
    MEREQ001 Customers' Own Data in Purchase Requisition
    for Purchase order , the BADIs and USER EXITS are
    ARC_MM_EKKO_CHECK BAdI: Enhancement of Archivability Check (MM_EKKO)
    ARC_MM_EKKO_WRITE BAdI: Enhancement of Scope of Archiving (MM_EKKO)
    EXTENSION_US_TAXES Extended Tax Calculation with Additional Data
    MEGUI_LAYOUT BAdI for Enjoy Purchasing GUI
    ME_ACTV_CANCEL_PO BAdI for Activating the Cancel Function at Header Level
    ME_BADI_DISPLAY_DOC BAdI for Internal Control of Transaction to be Invoked
    ME_BAPI_PO_CREATE_01
    ME_BAPI_PO_CREATE_02
    ME_BAPI_PR_CREATE_01
    ME_BAPI_PR_CREATE_02
    ME_BSART_DET Change document type for automatically generated POs
    ME_CCP_ACTIVE_CHECK BAdI to check whether CCP process is active
    ME_CCP_BESWK_AUTH_CH BAdI for authorization checks for procuring plant
    ME_CCP_DEL_DURATION Calc. of Delivery Duration in CCP Process (Not in Standard)
    ME_CHANGE_CHARACTER Customer-Specific Characteristics for Product Allocation
    ME_CHANGE_OUTTAB Enrich ALV Output Table in Purchasing
    ME_CHECK_ALL_ITEMS Run Through Items Again in the Event of Changes in EKKO
    ME_CHECK_OA Check BAdI for Contracts
    ME_CHECK_SOURCES Additional Checks in Source Determination/Checking
    ME_CIN_LEINRF2R BADI for CIN India - Delivery charges
    ME_CIN_LEINRF2V BADI for LEINRF03 excise_invoice_details
    ME_CIN_MM06EFKO Copy PO data for use by Country version India
    ME_CIP_ALLOW_CHANGE Configuration in Purchasing: Changeability Control
    ME_CIP_REF_CHAR Enables Reference Characteristics in Purchasing
    ME_COMMITMENT_RETURN Commitment for return item
    ME_COMMITMENT_STO_CH BadI for checking if commitments for STOs are active
    ME_COMMTMNT_PO_RELEV Check for Commitment-Relevance of Purchase Orders
    ME_COMMTMNT_PO_REL_C Check for Commitment-Relevance of Purchase Orders
    ME_COMMTMNT_REQ_RELE Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_REQ_RE_C Check of Commitment Relevance of Purchase Requisitions
    ME_DEFINE_CALCTYPE Control of Pricing Type: Additional Fields
    ME_DP_CLEARING Clearing (Offsetting) of Down Payments and Payment Requests
    ME_FIELDSTATUS_STOCK FM Account Assignment Behavior for Stock PR/PO
    ME_GUI_PO_CUST Customer's Own Screens in Enjoy Purchase Order
    ME_HOLD_PO Hold Enjoy Purchase Orders: Activation/Deactivation
    ME_INFOREC_SEND Capture/Send Purchase Info Record Changes - Internal Use
    ME_PO_PRICING Enhancements to Price Determination: Internal
    ME_PO_PRICING_CUST Enhancements to Price Determination: Customer
    ME_PO_SC_SRV BAdI: Service Tab Page for Subcontracting
    ME_PROCESS_COMP Processing of Component Default Data at Time of GR: Customer
    ME_PROCESS_PO Enhancements for Processing Enjoy Purchase Order: Intern.
    ME_PROCESS_PO_CUST Enhancements for Processing Enjoy Purchase Order: Customer
    ME_PROCESS_REQ Enhancements for Processing Enjoy PReqs: Internal
    ME_PROCESS_REQ_CUST Enhancements for Processing Enjoy PReqs: Customer
    ME_PURCHDOC_POSTED Purchasing Document Posted
    ME_RELEASE_CREATE BAdI: Release Creation for Sched.Agrmts with Release Docu.
    ME_REQ_OI_EXT Commitment Update in the Case of External Requisitions
    ME_REQ_POSTED Purchase Requisition Posted
    ME_TAX_FROM_ADDRESS Tax jurisdiction code taken from address
    ME_TRF_RULE_CUST_OFF BADI for Deactivation of Field T161V-REVFE
    ME_TRIGGER_ATP Triggers New ATP for Changes in EKKO, EKPO, EKPV
    ME_WRF_STD_DNG PO Controlling Reminder: Extension to Standard Reminder
    MM_DELIVERY_ADDR_SAP Determination of Delivery Address
    MM_EDI_DESADV_IN Supplementation of Delivery Interface from Purchase Order
    SMOD_MRFLB001 Control Items for Contract Release Order
    AMPL0001  User subscreen for additional data on AMPL             
    LMEDR001  Enhancements to print program                          
    LMELA002  Adopt batch no. from shipping notification when posting
    LMELA010  Inbound shipping notification: Transfer item data from 
    LMEQR001  User exit for source determination                     
    LMEXF001  Conditions in Purchasing Documents Without Invoice Rece
    LWSUS001  Customer-Specific Source Determination in Retail       
    M06B0001  Role determination for purchase requisition release    
    M06B0002  Changes to comm. structure for purchase requisition rel
    M06B0003  Number range and document number                       
    M06B0004  Number range and document number                       
    M06B0005  Changes to comm. structure for overall release of requi
    M06E0004  Changes to communication structure for release purch. d
    M06E0005  Role determination for release of purchasing documents 
    ME590001  Grouping of requsitions for PO split in ME59           
    MEETA001  Define schedule line type (backlog, immed. req., previe
    MEFLD004  Determine earliest delivery date f. check w. GR (only P
    MELAB001  Gen. forecast delivery schedules: Transfer schedule imp
    MEQUERY1  Enhancement to Document Overview ME21N/ME51N           
    MEVME001  WE default quantity calc. and over/ underdelivery toler
    MM06E001  User exits for EDI inbound and outbound purchasing docu
    MM06E003  Number range and document number                       
    MM06E004  Control import data screens in purchase order          
    MM06E005  Customer fields in purchasing document                 
    MM06E007  Change document for requisitions upon conversion into P
    MM06E008  Monitoring of contr. target value in case of release or
    MM06E009  Relevant texts for "Texts exist" indicator             
    MM06E010  Field selection for vendor address                     
    MMAL0001  ALE source list distribution: Outbound processing      
    MMAL0002  ALE source list distribution: Inbound processing       
    MMAL0003  ALE purcasing info record distribution: Outbound proces
    MMAL0004  ALE purchasing info record distribution: Inbound proces
    MMDA0001  Default delivery addresses                             
    MMFAB001  User exit for generation of release order              
    MRFLB001
    Regards,
    Anirban

  • Customer Subscreen for Purchase Requisition

    Hello All,
    I need a custom subscreen on requisition at <b>HEADER</b> level.  'MEREQ001' adds a screen at item level. Is there any Screen Exit / BADI to add a custom screen at header level? Any kind of help is really appreciated.
    Thank you all,
    Chandni

    Hi Chandi Reddy,
    The t.code is ME51 For this available exits are :
    AMPL0001  User subscreen for additional data on AMPL
    LMEDR001  Enhancements to print program
    LMELA002  Adopt batch no. from shipping notification when posting
    LMELA010  Inbound shipping notification: Transfer item data from
    LMEQR001  User exit for source determination
    LMEXF001  Conditions in Purchasing Documents Without Invoice Rece
    LWSUS001  Customer-Specific Source Determination in Retail
    M06B0001  Role determination for purchase requisition release
    M06B0002  Changes to comm. structure for purchase requisition rel
    M06B0003  Number range and document number
    M06B0004  Number range and document number
    M06B0005  Changes to comm. structure for overall release of requi
    M06E0004  Changes to communication structure for release purch. d
    M06E0005  Role determination for release of purchasing documents
    ME590001  Grouping of requsitions for PO split in ME59
    MEETA001  Define schedule line type (backlog, immed. req., previe
    MEFLD004  Determine earliest delivery date f. check w. GR (only P
    MELAB001  Gen. forecast delivery schedules: Transfer schedule imp
    MEQUERY1  Enhancement to Document Overview ME21N/ME51N
    MEVME001  WE default quantity calc. and over/ underdelivery toler
    MM06E001  User exits for EDI inbound and outbound purchasing docu
    MM06E003  Number range and document number
    MM06E004  Control import data screens in purchase order
    MM06E005  Customer fields in purchasing document
    MM06E007  Change document for requisitions upon conversion into P
    MM06E008  Monitoring of contr. target value in case of release or
    MM06E009  Relevant texts for "Texts exist" indicator
    MM06E010  Field selection for vendor address
    MMAL0001  ALE source list distribution: Outbound processing
    MMAL0002  ALE source list distribution: Inbound processing
    MMAL0003  ALE purcasing info record distribution: Outbound proces
    MMAL0004  ALE purchasing info record distribution: Inbound proces
    MMDA0001  Default delivery addresses
    MMFAB001  User exit for generation of release order
    MRFLB001
    For t.code we51n the available exits and badi are :
    Enhancement/ Business Add-in            Description
    Enhancement
    MEREQ001                                Customers' Own Data in Purchase Requisition
    Business Add-in
    ME_COMMITMNT_PARKING                    BAdI for Redefining Commitment Interface When Parking
    ME_MEREQ_PARKING                        BAdI Purchase Requisition: "Hold"
    ME_REQ_HEADER_TEXT                      Copy Header Text: Enjoy Purchase Requisition
    o.of Exits:          1
    o.of BADis:          3
    Rewards some points.
    Rgds,
    P.Naganjana Reddy

  • User exit/BADI  for Purchase requisition through release of Process order

    Hi ,
    i need to add some text to the Pur Req.
    The Pur Req will be created THROUGH the release of PROCESS order. Please let me know any exits are available for the same.
    regards

    Hi
    Check the following Exits and BADI for Pur Requisition
    Enhancement
    MEVME001                                WE default quantity calc. and over/ underdelivery tolerance
    MM06E001                                User exits for EDI inbound and outbound purchasing documents
    MM06E003                                Number range and document number
    MM06E004                                Control import data screens in purchase order
    MM06E005                                Customer fields in purchasing document
    MM06E007                                Change document for requisitions upon conversion into PO
    MM06E008                                Monitoring of contr. target value in case of release orders
    MM06E009                                Relevant texts for "Texts exist" indicator
    MM06E010                                Field selection for vendor address
    MM06E011                                Activate PReq Block
    MMAL0001                                ALE source list distribution: Outbound processing
    MMAL0002                                ALE source list distribution: Inbound processing
    MMAL0003                                ALE purcasing info record distribution: Outbound processing
    MMAL0004                                ALE purchasing info record distribution: Inbound processing
    MMDA0001                                Default delivery addresses
    MMFAB001                                User exit for generation of release order
    MRFLB001                                Control Items for Contract Release Order
    AMPL0001                                User subscreen for additional data on AMPL
    LMEDR001                                Enhancements to print program
    LMELA002                                Adopt batch no. from shipping notification when posting a GR
    LMELA010                                Inbound shipping notification: Transfer item data from IDOC
    LMEQR001                                User exit for source determination
    LMEXF001                                Conditions in Purchasing Documents Without Invoice Receipt
    LWSUS001                                Customer-Specific Source Determination in Retail
    M06B0001                                Role determination for purchase requisition release
    M06B0002                                Changes to comm. structure for purchase requisition release
    M06B0003                                Number range and document number
    MEQUERY1                                Enhancement to Document Overview ME21N/ME51N
    MELAB001                                Gen. forecast delivery schedules: Transfer schedule implem.
    MEFLD004                                Determine earliest delivery date f. check w. GR (only PO)
    MEETA001                                Define schedule line type (backlog, immed. req., preview)
    ME590001                                Grouping of requsitions for PO split in ME59
    M06E0005                                Role determination for release of purchasing documents
    M06E0004                                Changes to communication structure for release purch. doc.
    M06B0005                                Changes to comm. structure for overall release of requisn.
    M06B0004                                Number range and document number
    Business Add-in
    ME_PROCESS_REQ_CUST                     Enhancements for Processing Enjoy PReqs: Customer
    ME_PROCESS_REQ                          Enhancements for Processing Enjoy PReqs: Internal
    ME_PROCESS_PO_CUST                      Enhancements for Processing Enjoy Purchase Order: Customer
    ME_PROCESS_PO                           Enhancements for Processing Enjoy Purchase Order: Intern.
    ME_PROCESS_COMP                         Processing of Component Default Data at Time of GR: Custome
    ME_PO_SC_SRV                            BAdI: Service Tab Page for Subcontracting
    ME_PO_PRICING_CUST                      Enhancements to Price Determination: Customer
    ME_PO_PRICING                           Enhancements to Price Determination: Internal
    ME_INFOREC_SEND                         Capture/Send Purchase Info Record Changes - Internal Use
    ME_HOLD_PO                              Hold Enjoy Purchase Orders: Activation/Deactivation
    ME_GUI_PO_CUST                          Customer's Own Screens in Enjoy Purchase Order
    ME_FIELDSTATUS_STOCK                    FM Account Assignment Behavior for Stock PR/PO
    ME_DP_CLEARING                          Clearing (Offsetting) of Down Payments and Payment Requests
    ME_PURCHDOC_POSTED                      Purchasing Document Posted
    SMOD_MRFLB001                           Control Items for Contract Release Order
    EXTENSION_US_TAXES                      Extended Tax Calculation with Additional Data
    ARC_MM_EKKO_WRITE                       BAdI: Enhancement of Scope of Archiving (MM_EKKO)
    ARC_MM_EKKO_CHECK                       BAdI: Enhancement of Archivability Check (MM_EKKO)
    MM_EDI_DESADV_IN                        Supplementation of Delivery Interface from Purchase Order
    MM_DELIVERY_ADDR_SAP                    Determination of Delivery Address
    ME_WRF_STD_DNG                          PO Controlling Reminder: Extension to Standard Reminder
    ME_TRIGGER_ATP                          Triggers New ATP for Changes in EKKO, EKPO, EKPV
    ME_TRF_RULE_CUST_OFF                    BADI for Deactivation of Field T161V-REVFE
    ME_TAX_FROM_ADDRESS                     Tax jurisdiction code taken from address
    ME_REQ_POSTED                           Purchase Requisition Posted
    ME_REQ_OI_EXT                           Commitment Update in the Case of External Requisitions
    ME_RELEASE_CREATE                       BAdI: Release Creation for Sched.Agrmts with Release Docu.
    ME_DEFINE_CALCTYPE                      Control of Pricing Type: Additional Fields
    ME_CHANGE_OUTTAB                        Enrich ALV Output Table in Purchasing
    ME_CHANGE_CHARACTER                     Customer-Specific Characteristics for Product Allocation
    ME_CCP_DEL_DURATION                     Calc. of Delivery Duration in CCP Process (Not in Standard)
    ME_CCP_BESWK_AUTH_CH                    BAdI for authorization checks for procuring plant
    ME_CCP_ACTIVE_CHECK                     BAdI to check whether CCP process is active
    ME_BSART_DET                            Change document type for automatically generated POs
    ME_BAPI_PR_CREATE_02
    ME_BAPI_PR_CREATE_01
    ME_BAPI_PO_CREATE_02
    ME_BAPI_PO_CREATE_01
    ME_BADI_DISPLAY_DOC                     BAdI for Internal Control of Transaction to be Invoked
    ME_ACTV_CANCEL_PO                       BAdI for Activating the Cancel Function at Header Level
    MEGUI_LAYOUT                            BAdI for Enjoy Purchasing GUI
    ME_CHECK_ALL_ITEMS                      Run Through Items Again in the Event of Changes in EKKO
    ME_COMMTMNT_REQ_RE_C                    Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_REQ_RELE                    Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_PO_REL_C                    Check for Commitment-Relevance of Purchase Orders
    ME_COMMTMNT_PO_RELEV                    Check for Commitment-Relevance of Purchase Orders
    ME_COMMITMENT_STO_CH                    BadI for checking if commitments for STOs are active
    ME_COMMITMENT_RETURN                    Commitment for return item
    ME_CIP_REF_CHAR                         Enables Reference Characteristics in Purchasing
    ME_CIP_ALLOW_CHANGE                     Configuration in Purchasing: Changeability Control
    ME_CIN_MM06EFKO                         Copy PO data for use by Country version India
    ME_CIN_LEINRF2V                         BADI for LEINRF03 excise_invoice_details
    ME_CIN_LEINRF2R                         BADI for CIN India - Delivery charges
    ME_CHECK_SOURCES                        Additional Checks in Source Determination/Checking
    ME_CHECK_OA                             Check BAdI for Contracts
    Reward points if useful
    Regards
    Anji

  • Creation of Purchase requisition with reference to Contract documents

    Dear All
    I am not able to create the Purchase requisition with reference to Contract documents, in outline agreement field if I enter the contract document number which is already existing it is not copying the details, again I have to enter all the details like Plant, Material, document type, Qty etc.  Even after selecting the PR document type as RV for outline agreement also it is not coping. Kindly let me know that can we not able to give reference of Contract number in this outline agreement field to create Purchase requisition.
    regards
    Dhanu

    1.Logistics--Materials Management--Purchasing ---Purchase Requisition --Follow-on functions --- Assign and Process
    2.ME57
    3.Select the Assigned Purchase Requisitions checkbox if you also want to see requisitions already assigned, and choose Execute.
    4.On the Assign and Process Purchase Requisitions screen, select the requisition lines for your material.
    5.Choose Assign Manually if the info record already exists.
    6.On the pop-up Assign Source of Supply Manually dialog box, make the following entries:
    Agreement     46XXXXX            Agmt item     10          
    7.Choose Assign Source of Supply.
    For assign the source of supply, you can also choose Assign Automatically (only if not already assigned by MRP due to existing source list). If more than one source exists, select the contract in the Source Overview for Purchase Requisition 100XXXXX window and confirm with Enter.
    When assigning a source, make sure to select the contract.
    8.Choose Save.
    9.Select the line item, and then choose Assignments Overview (SHIFT+F5).
    10.On the Assign and Process Requisitions: Overview of Assignments screen, select the line below Vendor (you can only select one at a time), then choose Process Assignment.
    11.On the Process Assignment: Create PO window, check and make sure the Order Type (NB), Purchasing Group and Purch. Organization fields then choose Continue (Enter) to confirm.
    12.On the Create Purchase Order screen, select the requisition in the Document Overview section and choose Adopt in the left part of the Document Overview screen.
    13.Choose Save.

  • Purchase Requisition and Reservation Print out - Output Message determinatn

    Dear Experts,
    Can Anybody please explain the process of Output Message determination for Purchase Requisition and reservation.
    Thanks in Advance
    Vijay

    Hi,
    There is not standard message determination, you have to customized the transaction and output for PR & Reservation.

  • Several purchase requisition same day MRP

    Hello,
    I hace materials with lot size EX Lot-for-lot order quantity. The problem is when I have 2 planned issuses the same day, When I run MRP, SAP add quantities and create only a purchase requisition. I need sap create one PR for a planned iissue, with the same quantity.
    Thanks in advance.

    Hi,
    While executing MRP run it gets triggered  when the available stock falls below reorder point. It is basically reorder point which determines the purchase requisition creation while MRP is created.
    The reorder point is set considering  the past consumption material. If you want to trigger separate purchase requisition after each good issue you need to schedule MRP run after every good issue.
    This will generate separate purchase requisition after every good issue.
    Br,
    Tushar Patankar

  • Supply source determination

    what is meaning of supply source determination, how it works purchase price determinations sequence used in the calculation of sales price, Please explain me what is source determination and purchase price dterminatiion type whcih are used in sales price calculation.

    Hi Madhuri,
    The sales price calculation function contains three subfunctions:
           1.      Determining the purchase price (purchase price determination)
           2.      Determining the sales price (sales price determination)
           3.      Determining the margin, or the actual markup
    So your question is about the first step i.e Purchase Price Determination
    To determine the sales price of an article which is determined based on the purchase price of the articles ( markup), the purchase price of the article needs to be determined first.
    Supply Source Determination
    An article in a store can be procured from a DC or from a vendor. This is differentiated by using the "Supply source" which is in the Article Master - Store (or DC) view ( Field Name: MARC-BWSCL).
    So when you enter a sales organisation and distribution channel in the VKP5 screen for Sales price calculation, the supply source needs to be found out first to find who is the supplier. The site for determining the supply source is based on the reference site that is assigned for every distribution chain ( Sales org + Dist Channel) and the Sales OrgDist ChannelPrice List
    This configuration of assigning the reference site to the dist chain is in
    Logistics general -> Retail Pricing ->Sales Price Calculation ->Assign Pricing Type/Reference Site to Organisation level
    So once the reference site is determined the supply source of the article can be determined from that store. Then once it is done using the source determination of checking the
    1. source list for the store/DC,
    2. Supply Region
    3. Regular vendor
    etc then vendor will be identified ( the sequence may not be correct). Please refer to the below link for more detail on the source determination.
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/32/fa424287cf9923e10000000a155106/frameset.htm
    Once this is done, now we know the cost of the article ( PB00) but we need to find the purchace schema.
    The standard purchase price determination sequence is based on the Vendor Schema Group + Purchase Organisation ( Porg Schema group ) if its an external vendor else the STO schema will be determined.  Once the Net  purchase price is determined through the purchase price, this is used for determination of the sales price using the another process of sales price determination sequence.
    Hope this clarifies your query.
    Regards
    Prabhu

  • Exclude Purchase Requisition as a source of requirement

    Hi All,
    Please help me to configure the scenario.
    Sales order is created - Plant A, Sales Org u2013 A. (Item category u2013 BANC, Plant B is created as a vendor for Stock Transfer Purchase Order)
    Production Happens in - Plant B
    Present scenario u2013 we create sales order in SO u2013A, against plant A----automatic purchase requisition is created in Plant A against vendor Plant B. whenever we run MRP against plant B it create planned order against stock transfer requisition. From that planned order we get prod order and produce the material and deliver STO and finally customer.
    ***but our requirement is whenever we run mrp in Plant B it should not consider purchase requisition as source of requirement and will not create Planned order until or unless PR in plant A is converted to PO.
    I will be waiting for your valuable reply.
    Regards
    Nirmal

    hi,
    I am sorry as I was away  for  2 weeks.
    I think the  OPPQ settings may not do the trick for you  as  that is just stock in transfer  ( not stock transfer request from other plants).
    For the user exit details  which I was talking before,  you can see the link below
    How is the requirement type for STO materials determined
    hope this helps.
    regards
    Rav

  • BAPI for assing source of supply for purchase requisitions

    Hi,
    can any one let me know if there is any bapi or function module to assing source of supply for purchase requisitions. 
    Points will be given
    regards,
    siva prasad.

    Define fixed indicator in the source of supply , and set the source list usage of MRP to "1 "
    Below is help from sap:
    ==================================================================
    Determining the Source of Supply via the Source List
    The system first checks whether a quota arrangement has been maintained for the material, which has a validity period that covers the requirements date of the purchase requisition.
    It then checks whether only one entry exists in the source list that is relevant to MRP. The indicator for source list usage must therefore be set for a particular vendor so that purchase requisitions and delivery schedules, which are created during the planning run, are automatically assigned to this vendor. In the case of a delivery schedule, you must also have maintained a scheduling agreement for this entry.
    If you have maintained all the entries correctly, the system creates a purchase requisition with the source of supply that is recorded in the source list.

  • How to attach Source of Supply to Purchase requisition(by MRP)

    Hi Friends,
    Source list - we are maintaining Source list for source of supply.
    Please tell me how to attach Source of supply by means of source determination to the Purchase requisition(generated by MRP) ?. What are the configuration and transaction steps?.
    Thanks

    Define fixed indicator in the source of supply , and set the source list usage of MRP to "1 "
    Below is help from sap:
    ==================================================================
    Determining the Source of Supply via the Source List
    The system first checks whether a quota arrangement has been maintained for the material, which has a validity period that covers the requirements date of the purchase requisition.
    It then checks whether only one entry exists in the source list that is relevant to MRP. The indicator for source list usage must therefore be set for a particular vendor so that purchase requisitions and delivery schedules, which are created during the planning run, are automatically assigned to this vendor. In the case of a delivery schedule, you must also have maintained a scheduling agreement for this entry.
    If you have maintained all the entries correctly, the system creates a purchase requisition with the source of supply that is recorded in the source list.

Maybe you are looking for