Document Type at Company Code Level

Hi All,
I need a clarification with reference to the Number Range for PO Document Type say for NB.
I am having two company codes which uses different number range against the Document Type NB. As we know the Number Range is client dependent, we must create two document types NB and ZNB (ex) to get digfferent Number Range to be effective.
I would like to know if any SAP Standard Solutions available without using two document types, controlling the Number Range with reference to Company Code.
Can any one know how to do this?
Thanks for the Help,
Prakash

Hi
SAP does not have any standard functionality , but you can use the User exit / Enhancement
MM06E003
Number range and document number
function exit - EXIT_SAPMM06E_001
in this you can write the logic for derivation of number range based on the Compnay code.
Maintain the Combintaion in a Z table. & derive the number range group from the table.
This is a well used user exit,
Thanks & Regards
Kishore

Similar Messages

  • Where we assign Exchange rate type at company code level,

    Dear All,
    Where we assign Exchange rate type at company code level, In 0BA7 we assign by Document type wise and OB22 will assign by controlling area wise , but we are not maintain Controlling area, exactly where we assign , and how it will pick at the time of PO creation ,
    Thanks in advance
    Vijay

    Hi,
    In OB22 we assign Exchange rate type against company code and not against controlling area .
    Regards,
    Shayam

  • Restrict PO at company code level

    Hi,
    We have near about 10 number of company code and lot of plants attached to each company code.
    and only one purchase organisation.
    Now business require that PO shold be created only for 2 company codes not for all. there are alreday roles available for PO creation .
    Now how to restrcit the PO creation at company code level because at plant level it is not possible due to large number of plants.
    Regards,
    Pardeep Malik

    Hi,
    Please kindly be informed that the following authorization objects are checked when an Enjoy purchase order is created (activity 01) or changed (activity 02):
    - M_BEST_BSA (document type in PO)
    - M_BEST_EKG (purchasing group in PO)
    - M_BEST_EKO (purchasing organization in PO)
    - M_BEST_WRK (plant in PO)
    So this is somthing you can not solve by only using roles. You will need as suggested to make the check in the BADI.
    Best Regards,
    Arminda Jack.

  • Release Strategy @ Company Code Level

    Hi Guys:
    We have a two plants under one compant code, when we issue PO to the vendor it consists quantities that are required for both plants ( Central purchasing org).
    Release strategy for PO is at header level , I.e Total PO Value can we release strategy @ company code Level?
    with Characteristics as Company Code ,PO Document Type and PO Value?
    Thanks
    Sweth

    Hi
    For example if the release strategy set at c.code level all the documents created for several plants belonging to the c.code will affect the release strategy,so that is not the purpose of release strategy,
    The main purpose of release strategy is certain documents created for particular plant or particular purchasing group or more than the value need to be blocked based on your business,so you cant able to set the release at c.code level because thre is no logic.
    The characteristics for release strategy for external purchasing documents are
    Plant                - WERKS
    Pur.group        - EKGRP
    Pur.org            -EKORG
    Acc.assignment category-KNTTP
    Document value-GNETW
    Document type-BSART
    The table is CEKKO
    Thanks

  • Client level , company code level , chart of account level

    Hi experts
    Pls expline me which are we define under client level , company code level and COA level
    like :
    1) field status variant:
    2) Dunning procedure:
    3) document types:
    4) doc.number range:
    4) posting periods variant
    5) controlling area
    6) account groups
    7) vendor/cust master data
    8) dep key
    9) chart of dep area
    10) like...............................
    get points
    Geeta

    hi geeta,
    ClientA Client is the highest unit within an SAP system and contains Master records and Tables. Data entered at this level are valid for all company code data and organizational structures allowing for data consistency. User access and authorizations are assigned to each client created. Users must specify which client they are working in at the point of logon to the SAP system.
    A CompanyA Company is the unit to which your financial statements are created and can have one to many company codes assigned to it. A company is equivalent to your legal business organization. Consolidated financial statements are based on the companyu2019s financial statements. Companies are defined in configuration and assigned to company codes. Each company code must use the same COA( Chart of Accounts) and Fiscal Year. Also note that local currency for the company can be different.
    Company CodesCompany Codes are the smallest unit within your organizational structure and is used for internal and external reporting purposes. Company Codes are not optional within SAP and are required to be defined. Financial transactions are viewed at the company code level. Company Codes can be created for any business organization whether national or international. It is recommended that once a Company Code has been defined in Configuration with all the required settings then other company codes later created should be copied from the existing company code. You can then make changes as needed. This reduces repetitive input of information that does not change from company code to company code as well as eliminate the possibility of missed data input.
    Business Area Business Area is optional and is equivalent to a specific area of responsibility within your company or business segment. BA (Business Area) also allows for internal and external reporting.
    Another configuration requirement for set-up in SAP are the Basic settings consisting of the following:
    Chart of Accounts(COA)
    Fiscal Year Variants.
    Currencies
    The COA(Chart of Accounts)
    The COA(Chart of Accounts) lists all General Ledger accounts that are used by the organization. It is assigned in configuration to each company code and allows for daily General Ledger postings.
    Fiscal Year configuration
    Fiscal Year configuration is a must and can be defined to meet your companyu2019s reporting periods whether Fiscal (any period combination that is not calendar) or Calendar( Jan-Dec).
    Posting Periods are defined and assigned to the Fiscal Year.
    Within the periods you specify start dates and finished dates.
    SAP allows for 12 posting periods along with specially defined periods that can be used for year-end financial closing.
    Rohit Agrawal

  • Client level, chart of accounts level, company code level

    Generally what are the areas under client level, chart of accounts level, company code level.
    For Ex. document types are client level, number range company code level
    like the above does we have any list which is falling in the above levels.

    1. Generally during customising when co code data is not asked , then settings are client level.
    Country, Currency, Document types, all variants of diff types, chart of accounts, etc
    2. Every master is having data - General data level (client level) for use by all co codes, Co code data level(basically for accounting purposes) and so on.
    These are applicable to GL, Vendor, Customer, Asset, Matlerials, etc
    For particular application we have more information at another object level also- Vendor- Purchasing, Customer-Sales, materials-Plant- controlling, etc
    3. Chart of accounts level assignments are done for all automatic posting definitions-which is applicable to all company codes which are using same chart of accounts.
    4. In material setting- valuation can be grouping level, co code level or plant level as these are related to costing and product costing.
    Hope the above will give some idea.
    In the above nothing is written about CO as you have not asked-

  • Manage vendor bank account in company code level - Best practice

    hi,
    we have on our client several company codes, and we are thinking how to manage the vendor bank accounts in company codes level or in centeral level.
    our problem with company codes level is that the vendor bank accounts define in a centeral level so technically with sap standard it is not possible. if anyone can tell me that this is possible i will be very happy to know.
    in centeral level our problem is with the business process because of we do not have a person (functionalism ) that can be responsible for all the company codes, basically every company shoule be responsible for her vendors
    please advice what is the best practice to manage vendor bank accounts in enviroment of several company code
    regards,
    meir

    hi Raghu,
    i know that but this is not my qusition.
    which company code will be responsible to enter the bank account in the vendor master data? as i say the vendor bank accounts manage in centeral level and not in company code level and this is our problem and i like to know how other companies with the same situation handle with this issue
    and also after we have the bank accounts in the vendor master data what happend if for one vendor has several bank accounts one for every company code? how the payment program F110 could know automaticaly which bank account to take (i know that there is an optoin to use Partner bank type in the vendor master data, and enter this PBT when posting the invoice of the vednor, but this is not good because of we do not want the the accountant will be responsible from which bank the vendor get his money).
    regards,
    meir

  • Material valuation at company code level

    Hi,
    We have the valuation at company code level and when we transfer material from one plant to another (Two step stock transfer) the system dont post  fi document. When the profit center of the material is assign an fi document is posted. Somebody knows why?
    Thanks
    Edited by: Elisabete Cuellar on Jul 27, 2010 11:56 AM

    you have valuation at company code level.
    both plants are in same company code, so same valuation level, so no FI document created , the FI docuement not required here
    For profit center, FI document will be ceated for that profit center.
    This is standard process only

  • MRP at company code level

    Dear Experts,
    We required MRP at Company code level.
    We have 33 plants for MRP run , While running MRP system has to consider Finish Goods stocks of all plant's location should be consider for Availiblity check
    MRP run carried with scope of planning , in this scope of planning all the
    required plants are assigned , during planning Run , the stocks at other
    plants are not consider during NET requirement calculation.
    In turn it creates the planned independent requirement directly.
    So kindly suggest where we are going wroung. 
    Thanks 
    Material with scope of planning for all required plants.
    1. material with MRP type --- PD
    2.procurement type --- F and X (since planning external )
    3.Planning strategy --10

    Don,
    We required MRP at Company code level
    SAP PP does not explicitly support this requirement.  Since each plant is owned by a single company, you can run MRP against all plants owned by a specific company.  This will at least select the right materials for processing.
    While running MRP system has to consider Finish Goods stocks of all plant's location should be consider for Availability check
    MRP is not related to availability check.  FYI, if you are actually talking about availability check, and not MRP, there is no availability check available in ECC that will check inventory across plants.
    the stocks at other plants are not consider during NET requirement calculation.
    Yes.  This is normal.
    In turn it creates the planned independent requirement directly.
    MRP does not create Planned independent requirements.
    In short, you are doing nothing wrong.  This is the way that it works.  If this is unacceptable, then you will need to create a customized solution with Enhancements or BADIs.
    Best Regards,
    DB49

  • SAP ISU- Can you help on Invoice Rounding steps at company code level,

    Dear Friends,
    Can you help on SAP ISU Invoice Rounding steps at company code level,
    Client requirement is: - for one company code they need round the Invoice and other company codes they does not required the round option.
    We have configured some steps, which are given below,
    Contract Accounts Receivable and Payable - Basic Functions - Postings and Documents
    1.     Define Rounding Rules for Currencies
    2.     Define Accounts for Rounding Differences
    3.     Accounts for Rounding Gross Amounts (IS-U)
    4.     IS-U: Define Acct Assignment Data Relevant to Transactions
    a.     (Main Transaction 0010 and Sub Transaction 0040)
    SAP Utilities u2013 Invoicing
    1.     Define Basic Settings for Invoicing
    2.     Define Invoice Rounding Rules
    Please provide the solution; I will be appreciating for earliest answer...
    Thanks and Regards,
    Prudhvi

    Hello Christiane,
    Thanks for your quick reply, and valuable information,
    But we have u201CNo roundingu201D option available at client level, path has given below, 
    SPRO u2013 SAP Utilities Invoicing u2013 Basic setting u2013 Define Basic setting for invoicing
    We are not authorized to change any configuration at client level,
    If you can able to guide me at company code level that could be great,
    Thanks for the support
    Thanks and Regards,
    Prudhvi

  • Payment block non editable on the basis of company code level

    Dear Gurus,
    we had made payment block "A" non editable in payment praposal through transaction code ob27.as per reqeust from
    our partent company in India but our subsidiary in France wants the payment block "a"  to be editable (to be insert
    payment block "a" in document to make document deselect). Is it possible to make payment block editable on the basis of
    company code level.
    Regards,
    Rajesh

    Hi,
    In this scenario, you need to have a NEW Payment block key like Z. Create Z with reference to A in OB27.
    For Z, you need to select check box Change in Payment Proposal and SAVE.
    Now maintain this Z in vendor masters of company code, where you want the payment block can be edited.
    Note: Payment Block codes are not company code dependent.
    Regards,
    SRinu

  • Split valuation while Valuation is on Company Code Level

    Dear Experts
    I have tested before the split valuation while valuation is the plant level ... the problem now that the FI consultants need to work with valuation on company code level ..
    I have activated the categories for the company code , but When i tried to crate Material the field Valuation Category is just displayed and i can't enter any value in it ... how every i have created a new field reference to make it mandatory .. still the same problem
    so what is the solution ?
    Please Advice

    Solved by checking the two indicators : Value Update and Quantity Update in the quantity folder in the attributes of the Material Type
    Edited by: Sap Sap on Apr 14, 2010 11:28 AM

  • Document Currency Vs Company code Currency.

    As per business requirement Company code level currency is mainatained as USD but when i am generating the Excise invoice for loacl currency INR.,  the Excis edocument posting in USD . can any body helpme out to Post excise invoice as document currency where Excise tables is also updating the USD.
    rgadrs
    Ramesh.

    Closing this Thread as I found the answer
    Within the Purchase Order, when the new TOTAL NET ORDER VALUE is higher than the old one, release strategy will be triggered once release charateristic is set for checking rule
    System will check through The total net order value which is linked to CEKKO-GNETW for a purchase order.
    In purchase order, the currency conversion will act as below:
    Purchasing documents: Header currency converted to company code currency.
    Company currency converted to characteristic currency
    Hence, eventhough the exchange rate is increased but document currency is remained unchanged, the company code currency is increased and hence trigger release strategy.
    for more information, please refer to http://wiki.sdn.sap.com/wiki/display/ERPSCM/RELEASE+PROCEDURE

  • Account Determination at Company code level for an interface

    Hi All,
    We need an account determination table at company code level that will be used by an interface to find the GL accounts for a particular company code.
    This is required for interfacing certain GL documents onto SAP and the account determination need not be hardcoded in the program.
    Kindly revert with your ideas.....
    Regards,
    Gangs.

    Hi Gangesh,
    All the account determinations will be done only at the Chart of Accounts level only.  You cant show me even one account determination which will be done at the company code level.  (without giving chart of accounts before assigning a GL)
    So only table T030 will be the right table for you.  Hope you understood,
    Regards,
    Sreekanth....

  • Need a output based on document no and company code

    Hello All,
    I am new to BI and appreciate your cooperation
    I have a requirement where in I need a total count based on Document no and company code in the Report where in a document no can exist in multiple company code
    Say for eg
    Doc No CompanyCode
    123456          1000
    123456          2000   
    222222          2000
    333333          2000    
    Now I need the count based on document no and company code in the report. Kindly advice
    Thank you
    Poonam

    Hi Poonam,
    I don't know if this is possible in Query Designer level..
    Here is my suggestion:
    1. Create a new infoobject that will be used for the combined Doc No and Comp Code
    2. In transformation level, create a field routine that will CONCATENATE the Doc No and Comp Code in the infoobject you have created in STEP 1
    3. In Query Designer, make a FORMULA VARIABLE and choose REPLACEMENT PATH (select the infoobject you have created in STEP 1)
    4. In replacement path tab, choose INFOOBJECT, then ATTRIBUTE, and select CONSTANT 1 (forgot the exact name but there is constant 1 something in the selection)
    5. Create a global CKF with this formula (FORMULA VARIABLE * 1), this is necessary because sometimes the FV doesn't work without doing this
    6. Use the global CKF in your keyfigure structure, it will show the number of UNIQUE combination of Doc No and Comp Code
    Regards,
    Loed

Maybe you are looking for