Prevent creation of a PO to a non company code Vendor

Hi,
We have had a scenario where we have been ableo to create a purchase order to a vendor that doesnt exist in that company code.  The purchase order will let you Goods receipt this also and will only cause a problem upon invoicing it.
Since a Purchase order is considered a legal document we believe we should be able to prevent PO being saved if the vendor used does not exist in the company code selected in the PO header data. 
I can see why sap allows it as you put in the vendor before the company code is entered but can we prevent this being saved or a message coming up on the system when this combination is entered?
Thanks

Hi Tracey Sparry,
This can achieved as below.
An organizational unit in Logistics, subdividing an enterprise according to the requirements of Purchasing.
A purchasing organization procures materials and services, negotiates conditions of purchase with vendors, and is responsible for such transactions.
You specify the form of procurement by assigning purchasing organizations to company codes and plants.
Possible forms are:
Enterprise-wide: One purchasing organization procures for all the company codes of a client - that is, for all companies belonging to a corporate group
Company-specific: One purchasing organization procures for one company code
Plant-specific: One purchasing organization procures for one plant
In this way you can assig purchase orgnization to company code which is not necessary but in you case it is necessary so when you are creating vendor with purcahse org and company code it will establish link when you are creating purchase org and company code it will not not allow to proceed further it gives error that xxx vendor id not defined in company code and purchase org and stop further to save PO.

Similar Messages

  • PO creation-ME21n-Why SAP does not check company code and Plant relation

    Hi All,
    Does someone know, why SAP does not check Plant and company code relation at the time of PO creation or how can we put validation between plant and company code at the time of PO creation.
    <b>Example:</b> Suppose i have a company 0001 which is assinged to Plant 0001. when i am creating a PO with another company code 0002(Entering at header level-Org, data) and using Plant 0001 at line item level. SAP does not do this validation.
    How can we put this check in place?
    Thanks in advance.
    Deepak

    Hello Deepak,
    There are three types of purchasing
    - Company code specific :You need to assign company code to Pur organization
    - Plant specific : You must assign plant to pur organization
    - Cross company purchasing: No assignment between company code and pur organization.
    In the case 3, the system will not check company code and plant relationship, but it will check plant and pur organization specific.
    The following is the copy of sap help text:
    You can assign a purchasing organization to one company code. This is company-specific purchasing.
    You can assign a purchasing organization to no company code. This purchasing organization can then procure for all plants assigned to it, irrespective of the company code to which the plant belongs.
    Since each plant must be assigned to a company code, the company code can be determined via the plant in each procurement transaction, even if the procuring purchasing organization is not assigned to a company code.
    A purchasing organization must be assigned to one or more plants. This is plant-specific purchasing.
    Now, check your company-code and purchase organization assignment.
    Hope this helps.
    Regards
    Arif Mansuri

  • How to prevent settlements from AE to wbs with different company code

    Hi gurus,
    i'm currently facing a problem regarding settlements from activity elements to wbs above.
    we have one controllign areas with various company codes.
    For some projects, we have wbs assigned to company code A and activity elements assigned to Company A and B.
    We have an automatic settlement rule generation so that we settle all activity element costs to wbs. But, for activity elements assigned to company B, we don't want to settle the costs, we want to go through a sd/mm invoicing between the two companies.
    How can we prevent the settlement to take place, apart from manually removing the settlement rule for each activity element?
    can we put a validation rule that check that whenever the company code in the wbs is different from the one in the activity element, then the settlement doesn't take place? or remove the automatic settlement rule generation and use cjb1 to generate settlement rules only when an activity element as the same company code as the wbs above. would it be possible?
    would the WBS_SETTLEMENT_RULE BADI or badi proj be of any help?
    Any help is welcome.
    regards
    tim
    Edited by: Tim Ursulet on Jan 22, 2009 5:29 PM

    Hi Tim,
    The transaction CJB1 or CJB2 creates the settlment rules for WBS only, therefore the transactions and Badi WBS_SETTLEMENT_RULE BADI are NOT relevant for the settlement rules of activity and elements at all.
    For the settlement rules of activity (and elements) the default rule is inserted, as soon as the user navigate to the settlemenent rule overview screen, if the activity do not have the settlement rule at that time. I am not sure, if there is BaDi or substituation to prevent the system apply this default rule in certain case. Other alternative is to specify the objects during settlement,  e.g. using selection variant with the company code.
    Kind regards,
    Zhenbo

  • Creation of new COPA by copying previous Company code config

    Hi Guys:
    We have copied new COPA configuration for new company code with reference to already existing company code's config.
    I could not able to see Actual Flow of values by comparing different screens between old and new config. New config is not having flow of actual's data.
    Could someone guide me with verfication procedure to see why it has not transfferred a full config to new thing.
    Please advice.
    Thanks
    Sri

    Hi
    It is not clear what you copied for COPA configuration
    Please check whether the new co code is assigned to the same controlling area as the old ones.
    S Jayaram

  • Creation of same personnel number for different company codes

    Hi All,
    I am having the requirement to cerate same personnel number under different compant codes.
    Eg. There are 2 company codes MO10 and MO20 for the same country
    Personnel number- 0100000023 should exist for both company code MO10 and MO20.
    Please help.
    regards,
    Gaurav

    Dear Roger,
    Thanks for replying, I have been waiting for this. We are a group  of copmanies with the name of orient and have  four different  companies and currently  using one payroll area Z1 for payroll processing for  OEL; company code 1000. we have these company codes 2000, 3000 and 4000 for rest three companies and want to use same payroll area Z1 for processing payroll of these three companies. is that possible to do in SAP HCM if yes then how?
    Can you please guide on this? Look forward for your response.
    Stay Blessed,
    Waqar

  • Problem for creation of PO for different company code

    I have problem for creation of PO using ME21 for different company code.Order is not created.
    Please give reply it is urgent.

    Hi Mansih,
    I don´t understand what is your exact problem, as I don´t see any company code being specified. But maybe you should check in XK03 that the vendor master data is created for this company code/purchasing organisation!
    Have a nice day!

  • Restrict PO creation for multiple plants for same company code

    Hi Gurus,
    We want to restrict PO creation for multiple plants in the same company code. Based on Standard SAP settings for Purchasing organization assignment with multiple Plant and multiple Plant assignment with single company code, this is happening. Is there a way that we can restrict by doing some customization change.
    Any thoughts or ideas will be highly appreciating.
    Thanks and Best regards,
    Karun Kumar

    Hi,
    Said functionality is not available in SAP standard.
    To avoid the same ,i can suggest implement release strategy for PO,and then higher authority / commercial team can check created PO,if multiple plants available in single po then they have the option of rejection for the same.
    Or else check BADI-ME_PROCESS_PO_CUST,take the help from abapor and apply the restriction to select multiple plant in PO.
    Hope this will resolve your query,
    Thanks & Regards,
    Sandesh Sawant

  • How do we Prevent Creation of Production Orders for Phantom materials.

    Dear Experts;
    We have some materials which are Phantoms.
    We have set "special procurement type" as 50 in MRP2 and "Strategy Group" as 59 in MRP3
    These are non stchable items, but have BOMS.
    We dont create orders for them, however at the mement the system allows order creation. How do we prevent creation of production orders for these items in the system.
    Thanks in Advance
    Richard.

    Dear Richard,
    Check using this BADI - WORKORDER_UPDATE using method IN_UPDATE or Release by including a check if MATNR and for
    WERKS combination if SOBSL = 50 from table MARC,then do not allow to save.
    Check whether this works or else you have to set a plant specific status using OMS4  for not allowing production order
    creation and assign this value in the material master of the phantom assemblies.
    Check and revert
    Regards
    Mangalraj.S

  • Prevent creation of additional common objects at the  same time ...

    Context: A Super User group may require to be allowed to create and/or change queries in Production
    Would be possible to prevent creation of additional common objects like rectricted and calculated key figures and variables at the same time allowing creation of queries in terms of dragging and dropping filters, free characteristics, rows and columns?
    I know that keeping the system closed to changes and using the transport connection Object Changeability it is possible to restrict change of query elements to those that are original in the system.
    Points will awarded.
    Thanks
    Mathew.

    In transport connection Object Changeability, you can only set query elements as modificables but you cant distint between diferent query elements (queries, calculated/restricted key figures, structures, etc).
    You can do that distiction in authorization object in rs_comp and rs_comp1.
    You should combine transport connection Object Changeability and authorization objects in roles

  • Prevent creation of duplicate material master record

    Hi Experts
    1)  Is there any control or validation to prevent creation of duplicate material? I mean, if the description of new material is 100% or 95% matching with an existing material, there should be a validation.
    2) Is there any feature of usage of catelogs for creation of material master description?
    warm regards
    ramSiva

    Hi,
    Have a try to use Enhancement: MGA00001, user exit: EXIT_SAPLMGMU_001 for control you need.
    You can also use BAdI for this:
    BADI_MATERIAL_CHECK -> method CHECK.
    In both enhacements there is a structure STEXT - here short text(s) of new created material should be found for validation.
    Here you can make some ABAP works necessary.
    Hope it helps,
    regards,
    w.
    Edited by: Wojciech Zalech on May 19, 2010 9:43 AM

  • New Company code creation

    Hi,
    Client wants to split one company code to 8 company codes.
    Could you please explain what are the neccessary steps to take for this ?
    What are the precautions to take in creating Company code, Chart of accounts, AP,AR related,AA and consolidation ?
    Regards
    Madan

    Hello,
    You can keep concentration on the following transaction codes.
    These may be useful guide to you.
    FI Enterprise Structure Transaction Codes     
    Transaction Code     Description
    OBY7     Copy Chart of Accounts
    OB29     Fiscal Year Variant
    OBBO     Posting Period Variant
    OX02     Company Codes - Create Check and Delete
    OBY6     Company Code Global Parameters
    EC01     Copy Company code
    OY01     Country Definitions
    OB22     Parallel Currencies
    OX03     Business Areas
    OKBD     Functional Areas
    FI Enterprise Structure Transaction Codes (Continued)     
    Transaction Code     Description
    OBBG     Assign Country to Tax Calculation Procedure
    OBCO     Specify Structure for Tax Jurisdiction Codes
    OBCP     Define Tax Jurisdiction Codes
    FTXP     Maintain Tax Rates
    OBCL     Set Tax Codes for Non-Taxable Transactions
    General Ledger / Chart of Accounts Transaction Codes     
    Transaction Code     Description
    OBD4     Account Groups
    OB53     Retained Earnings Variant
    OB15     Sample Account Rule Types
    FSK2     Sample Account Data Transfer Rules
    OB67     Allocate a Company Code to a Sample Account Rule Type
    OBY9     Transport Chart of Accounts
    OBY2     Copy GL Accounts from the Chart to the Company Code
    OBC4     Field Status Variants
    OB41     Posting Keys
    FBKP     Automatic Account Assignments
    OB40     Define Tax Accounts
    OBYA     Cross Company Code Automatic Account Assignment
    OBYC     MM Automatic Account Assignment
    VKOA     SD Revenue Account Assignment
    OB58     Financial Statement Version
    O7Z3     Line Item Layouts
    OBVU     Special Fields
    O7S7     Sort Variants
    O7R1     Totals Variants
    OBA4     Tolerance Groups
    OB57     Allocate Users to Tolerance Groups
    FBN1     GL Number Ranges
    OBA7     Document Types
    OBU1     Assign Default Posting Keys to Document Types
    O7E6     Fast Entry Screens
    ORFB     Financial Accounting Configuration Menu
    OBL1     Automatic Postings Documentation
    OB32     Maintain Document Change Rules
    General Ledger / Chart of Accounts Programms     
    Transaction Code     Description
    RFBISA10     
    RFBISA20     
    RFTAXIMP     
    General Ledger / Chart of Accounts Tables     
    Transaction Code     Description
    BSEG     GL Document Line Item Table
    TTXD     Tax Jurisdiction Code Structure Table
    T030     Automatic Account Assignments Table
    TZUN     GL Account Sort Key (Allocation Field) Table
    Accounts Payable Transaction Codes     
    Transaction Code     Description
    FI12     House Banks
    FCHI     Check Lots
    FCHV     Void Reason Codes
    FBZP     Payment Programme
    OBD3     Vendor Groups
    XKN1     Create Number Ranges for Vendor Groups
    OBAS     Assign Number Ranges to Vendor Account Groups
    FK15     Copy Vendor Master Records Creation Programme
    FK16     Copy Vendor Master Records Creation Programme
    Accounts Receivable and Credit Management Transaction Codes     
    Transaction Code     Description
    OBB8     Terms of Payment AP and AR
    OB46     Interest Indicator
    OB82     Make Interest Indicator Available to the Interest Calculation Program
    OBAC     Reference Interest Rates
    OB81     Assign Reference Interest Rates to Interest Indicators
    OBV1     Interest Calculation Automatic Account Assignment
    OBBE     Reason Codes
    OBCR     Reason Code Conversion Version
    OBCS     Map External Reason Codes to Internal Reason Codes
    OBXL     Assign GL Accounts to Reason Codes
    OBXI     Cash Discount Amount
    OBA3     Customer Tolerance Groups
    OB45     Credit Control Areas
    OB01     Credit Risk Categories
    OB02     Credit Representative Groups
    OB51     Assign Employees to Credit Representative Groups
    OB39     Days in Arrears Calculation
    OBD2     Customer Groups
    Treasury Transaction Codes     
    Transaction Code     Description
    OB10     Create Lockbox Accounts
    OBAY     Define Lockbox Control Parameters
    OBAX     Lockbox Posting Data
    OT05     Source Symbols
    OT14     Planning Levels
    OT13     Planning Groups
    OT47     Assign Logistics Transactions to Planning Levels
    OT17     Treasury Groupings
    OT18     Treasury Grouping Headers
    OT16     Cash Management Account Names
    OT29     Activate Company Code Treasury Updates
    OBBY     Electronic Bank Statement Transaction Types
    OT55     Assign Transaction Types to House Banks
    OT57     Electronic Bank Statement Posting Rules
    OT51     Map External Transactions to Posting Rules
    OT59     Posting Rules Automatic Account Assignment
    GCRF     Currency Translation Ratios
    Regards,
    Ravi

  • Creation of SC or POs based on the Company Code restriction

    Dear All,
    I am abaper and I am new to SRM. Ours is SRM 4.0 using Extended Classic Scenario
    we got one requirement that one company ex: SE04 should be blocked for further ordering of SC and POs. i.e. when creating any SC or PO they dont want to use 'SE04'.  If selected it should throw an error message "Company Code SE04 can't be used for Procurement".
    I wrote code in BBP_DOC_CHECK_BADI-BBP_DOC_CHECK like this..
    IF  flt_val = 'BUS2121'. "When create SC
      LOOP AT lt_item INTO ls_item WHERE be_co_code = 'SE04'
                                        AND del_ind <> 'X'.
        CLEAR ls_message.
        ls_message-msgty   = 'E'.
        ls_message-msgid   = 'BBP_PU'.
        ls_message-msgno   = '001'.
        ls_message-msgv1   = text-001.
        APPEND ls_message TO et_messages.
      ENDLOOP.
    endif.
    and for po also BUS2201 we done the same.
    it is working fine for creation of SC and POS, but when we are chaning old SC or POs for 'SE04'  then also error is coming "Company Code SE04 can't be used for Procurement".
    When I put break point in BBP_DOC_CHECK_BADI-BBP_DOC_CHECK it is not stopping there also.
    Please guide me for this..
    Thanks,
    Kiran Madineni

    I written code like this: now working for old SC and POs.
    IF  flt_val = 'BUS2121'. "When create SC
        IF cs_header-created_at >= '20110110000000'.
    *if sy-title = 'Shop' and ( sy-tcode = 'BBPSC01' or sy-tcode = 'BBPSC02' or sy-tcode = 'BBPSC03' ).
          IF sy-tcode = 'BBPSC01' OR sy-tcode = 'BBPSC02' OR sy-tcode = 'BBPSC03'
            OR ( sy-tcode = 'BBPSC04' AND sy-title = 'Change Shopping Cart' ).
            LOOP AT lt_item INTO ls_item WHERE be_co_code = 'SE04'
                                              AND del_ind <> 'X'.
              CLEAR ls_message.
              ls_message-msgty   = 'E'.
              ls_message-msgid   = 'BBP_PU'.
              ls_message-msgno   = '001'.
              ls_message-msgv1   = text-001.
              APPEND ls_message TO et_messages.
            ENDLOOP.
          ENDIF.
        ENDIF.
      ENDIF.
    For POS BUS2201
    Thanks
    Kiran.

  • PO creation where discount is given after taxes for few Vendors

    Hi pankaj,
    Need a pricing stucture in PO creation where discount is given after taxes for few Vendors.
    please give the solution with brief steps.
    Regards,
    Pandi

    Hi,
    Take a copy of RA01 in M/06 as YA01(as Discount) and keep it as following;
    Cond. class A Discount or surcharge
    Calculat.type A Percentage
    Cond.category Blank
    And Plus/minus - A (Positive)
    Use this in Pricing Procedure ( M/08 ) after Gross Price ad Discount conditions (before Subtotal) and assign Subtotal "6" against this condition type.
    In OBQ3 - Tax Procedure, assign AltCBV 363 to CST/VAT Condition Type (JIP1/JIP5)
    Now check the calculation will happen as following;
    Gross Price = 10000 INR
    Discount (as -ve/+ve) = 1000 INR
    BED 14% = 1400 INR
    ECS 2% = 28 INR
    SECess 1% = 14 INR
    CST 2% = 248.84 INR
    Also refer following thread for the same;
    [Calculation Procedure;

  • Company code creation issue

    Hi All,
    When I am creating company code I am getting an error as below.
    "you may not change the currency since documents exist with this currency"
    Above issue is coming while new co code creation or copying of existing co code also.
    Please advice on the above issue.
    Regards,
    Riyaz

    Hi,
    I hope you are creating new company code by copying from the exiting company code. If you copy one company code to another company code then you will get few pop- up message like do you want to use same chart of account or do you want to use same currecny like that. So may be you have selected different currecny. Sap has come up with country template for each country. So you can use country template to create the new company code.
    Thanks & Regards
    R.K

  • Company code creation...what option is better?

    Hi Gurus,
    My client has an existing company code in US and the parant company code abroad. They have now acquired another company is US. I need to decide whether we create a new company code for the new acquired company or do we just merge the acquired company with the existing company code in US.
    What are the pros and cons of merging vs, creation of a new company code?
    Note: Using FI-Consolidation is out of scope.
    I am not sure how the FI entries are transfered from the legacy system to the new company code or merged with an existing company code.
    Would appreciate any insite and links on such a topic.
    Thanks & Regards

    Hi Sunny this is a very wide question.
    Here are some questions to consider.
    Do you need to show the new company code as a seperate company code?
    Can they use your Chart of Accounts?
    Is the new company keeping its name?
    Have you got any common master data, customers, vendors?
    When will you be making the transfer?
    Do you use ERP 6.0? If you did not want to create a new company code you could use document splitting.
    You can copy your US Company Code, and then extend any common master data, GL accounts, Customers Accounts and Vendor Accounts?
    Are you buying all of the debt from the new company, if so you will need to keep the debt seperate to that of your current debtors.
    Hope some of this helps.

Maybe you are looking for