IMG config menu  for  J_1inexcgrp

Friends under CIN one important maintenance is J_1inexcgrp
I want to know whether IMG config menu exist for this or it is always maintained manually?
Regards,
Akhileshwar K

Hi,
Pls check below link.
http://help.sap.com/bp_bblibrary/500/Documentation/J83_BB_ConfigGuide_EN_IN.doc#_Toc104193037
http://help.sap.com/bestpractices/BBLibrary/Documentation/J83_BB_ConfigGuide_EN_IN.doc
Regards,
Anil

Similar Messages

  • URGENT HELP REQUIRED - E-filing for GB - IMG CONFIG

    Hi
    We are on ECC 6.0 and have just installed XI. I am trying to complete the SAP IMG Config, however there is limited documentation about this, particularly the constants and e-mail content.
    Does anyone have any useful (ideally step by step) documentation on how to complete the customisation?
    Your URGENT assistance is greatly appreciated.
    Thanks
    Michelle

    Hi refer theses links
    http://help.sap.com/saphelp_erp2005/helpdata/en/cd/5a0641f753f523e10000000a155106/frameset.htm
    EOY2007 GB (E-Filing)

  • Config steps for regular ofcycle payroll

    Hi All,
    plz let me know the config steps for regular ofcycle payroll
    SD

    Hi,
    1) Firstly follow the IMG Menu path  PM>PA>Payroll data>Additional Payments-offcycle>wage types    
    Create ur desired wage types for off-cycle and configure them accordingly
    2) Now IMG >Payroll>India>Off-cycle activities>
    Configure as u need
    Maintain IT 0267 with entries like Off cycle reason.... Identifier...... Amount ..... Date...etc.
    Run payroll with the parameters u have maintained in IT 0267
    Try and revert back if any dificulties
    Nasim

  • Config settings for AP, AR from SD and MM prospect?.

    Hello Guru's,
    Will anyone share your expertise,  what are the config settings for AP and AR from SD, MM point of view and what are the Integration points for AP and AR with FICO.

    You may check the links to understand the link between SD and FI.
    https://www.sdn.sap.com/irj/sdn/wiki?path=/pages/viewpage.action&pageid=33768
    http://www.sapscene.com/sapscene/accassg.html
    http://www.sap-img.com/financial/fico-interview-questions.htm
    http://www.sap-img.com/sap-sd/link-between-sap-sd-mm-and-fi.htm
    http://sap-img.com/financial/integration-of-fico-with-other-modules.htm
    Regards,
    GSL.

  • No languages visible in drop down menu for spelling under preferences

    My IT department just gave me a new computer and we downloaded a copy of Dreamweaver 4 (we use this version for various reasons although it is old). When I went tot he preferences, under 'General' and 'Spelling Dictionary' the drop down menu is blank and I cannot select anything. The spell checker works but I no longer get the red squiggly line under spelling errors when working on a web page (like you get in a Word document). I don't know how to get this feature back.

    Spell check in DW, at least the built in spell checker, is a manual process with a dialogue pop up that allows you to Ignore, Change, Ignore All or Change All on a word by word basis. There's never been a live red squiggly line like Word, and just about every other program under the sun, as far back as at least DWCS3 (the oldest version I've used).
    You should still have a little over a dozen options in the language drop-down though.
    I'd try clearing the cache/personal config file for the program: Deleting a corrupted cache file
    Then restore preferences if that doesn't work: Restore preferences | Dreamweaver CS4, CS5, CS5.5, CS6

  • Why there are two IMG steps provided for Home Page configuration?

    Dear experts,
    I wonder why there are two IMG steps provided for configuring ESS home page.
    1. Cross Application Components --> Employee Self Service --> General Settings
    2. Personnel Management --> Employee Self-Service --> General Settings
    Both tables contents are also similar.
    Why SAP has provided same configuration steps in two areas?

    Your first one is wrong. It is under Cross App. Components but not in an ESS node....I am sure it is a typo on your part. Anyways......
    It's NOT two steps. It's just the same configuration in two places. It makes it easier to locate for instance if you are in ESS to just have it there. BUT the Homepage Framework is used elsewhere (MSS for example) as well as you can use it for whatever else you like (building an easier interface for other things) therefore, it has it's "true" place up as a "cross application component".
    This is very similar to say Benefits. If you look under the Benefits config area in the IMG, you will actually see a lot of ESS settings there that are the exact same ones you see under the ESS node too.
    Don't let it confuse you.

  • Need help fixing a CSS Drop-Down menu for IE6

    Hello.
    I have created an entirely CSS drop down menu for my website
    which works perfect in Firefox, Safari, Opera and IE7 however when
    I tested in IE6 it displayed like this -->
    image
    here or go to http://www.runecentral.net/index.php (Must have
    /index.php as i have redirected / to the community forum.)
    Here is my code

    Thank you for your reply.
    To answer your first question, I tried it with just one
    before and it caused Internet Explorer to display the background
    incorrectly so I just kept them both.
    I have replaced background-image with background:
    url(/img/defmenu.png) repeat-x;
    But, I cannot access my XP machine until tomorrow so I cannot
    view the site in IE6, if you could test it and tell me if it is the
    same as the image linked to in my first post that would be great.
    Kind Regards,
    Perry

  • Creating an auto-generating menu for fluxbox

    Fluxbox is one of the best wms for linux. If there's something that could replace any desktop, with low resources consumption, still being accessible and handy, than that's Fluxbox. The thing is when you install Fluxbox for the first time you feel something is lacking. That thing is the possibility of an auto-generating menu. Of course there's
    fluxbox-generate_menu
    and other likewise possibilities  but they kinda fail in doing what they should.   I'm a bit new to programming and even fresher when it comes to scripting in linux but I've though of a script that could do just that as it follows:
    #!/bin/bash
    while true
    do
    men="ArchSoft"
    ver=$(grep "$men" ~/.fluxbox/menu | sed 's/.*(//; s/).*//' | tail -1)
    if [ $men == $ver ]
    then
    data="$(date +%Y-%m-%d\ %k:%M)"
    data2="$(grep "$data" /var/log/pacman.log | grep installed | sed "s/\[//g; s/\].*//g" | tail -1)"
    if [ "$data" == "$data2" ]
    then
    nr="$(grep "$data" /var/log/pacman.log | grep installed | wc -l)"
    int=$(seq 1 $nr)
    for i in $int
    do
    ch=$(grep "$data" /var/log/pacman.log | grep installed | sed 's/.*installed//g; s/(.*//g; s/ //g' | head -$i | tail -1)
    chr=$(grep "$ch" ~/.fluxbox/menu | sed 's/.*(//; s/).*//' | tail -1)
    chb=$(ls /usr/bin | grep "$ch" | sed "s/.*$ch.*/$ch/" | tail -1)
    la=$(ls /usr/share/icons/hicolor/48x48/apps | grep $ch | sed "s/.*$ch.*/$ch/"| tail -1)
    lb=$(ls /usr/share/pixmaps | grep $ch | sed "s/.*$ch.*/$ch/" | tail -1)
    if [ $ch == $chb ]
    then
    if [ $ch == $chr ]
    then
    echo "there's already a menu entry"
    else
    if [ $ch == $la ]
    then
    sed -i "/^\[submenu\] ($men)$/a[exec] ($ch) {$ch} </usr/share/icons/hicolor/48x48/apps/$ch.png>" ~/.fluxbox/menu
    sleep 1
    fluxbox restart
    elif [ $ch == $lb ]
    then
    sed -i "/^\[submenu\] ($men)$/a[exec] ($ch) {$ch} </usr/share/pixmaps/$ch.png>" ~/.fluxbox/menu
    sleep 1
    fluxbox restart
    fi
    fi
    fi
    done
    fi
    rdata="$(grep "$data" /var/log/pacman.log | grep removed | sed "s/\[//g; s/\].*//g" | tail -1)"
    if [ "$data" == "$rdata" ]
    then
    nrem="$(grep "$data" /var/log/pacman.log | grep removed | wc -l)"
    inrem=$(seq 1 $nrem)
    for i in $inrem
    do
    rem=$(grep "$data" /var/log/pacman.log | grep removed | sed 's/.*removed//g; s/(.*//g; s/ //g' | head -$i | tail -1)
    remr=$(grep "$rem" ~/.fluxbox/menu | sed 's/.*(//; s/).*//' | tail -1)
    if [ $rem == $remr ]
    then
    sed -i "/$rem/d" ~/.fluxbox/menu
    sleep 1
    fluxbox restart
    else
    echo "no menu entry to remove"
    fi
    done
    fi
    else
    sed -i "/^\[begin\] (Fluxbox)$/a[submenu] ($men)\n[end]" ~/.fluxbox/menu
    fi
    clear
    sleep 7
    done
    Explanation:
    I've used
    whilde true
    do
    sleep 7
    done
    to create an endless loop where "sleep" was used so it could take a break, therefore reducing hardware consumption
    men="ArchSoft"
    ver=$(grep "$men" ~/.fluxbox/menu | sed 's/.*(//; s/).*//' | tail -1)
    if [ $men == $ver ]
    then
    else
    sed -i "/^\[begin\] (Fluxbox)$/a[submenu] ($men)\n[end]" ~/.fluxbox/menu
    fi
    This checks if the submenu where everything should automatically be added as entries  are already there, if not it creates them under the beginning of fluxbox menu script with the name ArchSoft. 
    data="$(date +%Y-%m-%d\ %k:%M)"
    data2="$(grep "$data" /var/log/pacman.log | grep installed | sed "s/\[//g; s/\].*//g" | tail -1)"
    if [ "$data" == "$data2" ]
    then
    fi
    this compares the actual data from the system clock with the data of the installed apps shown in pacman .log and if it finds a similar data of the installed apps it procedes to further steps
    nr="$(grep "$data" /var/log/pacman.log | grep installed | wc -l)"
    int=$(seq 1 $nr)
    for i in $int
    do
    ch=$(grep "$data" /var/log/pacman.log | grep installed | sed 's/.*installed//g; s/(.*//g; s/ //g' | head -$i | tail -1)
    chr=$(grep "$ch" ~/.fluxbox/menu | sed 's/.*(//; s/).*//' | tail -1)
    chb=$(ls /usr/bin | grep "$ch" | sed "s/.*$ch.*/$ch/" | tail -1)
    la=$(ls /usr/share/icons/hicolor/48x48/apps | grep $ch | sed "s/.*$ch.*/$ch/"| tail -1)
    lb=$(ls /usr/share/pixmaps | grep $ch | sed "s/.*$ch.*/$ch/" | tail -1)
    if [ $ch == $chb ]
    then
    if [ $ch == $chr ]
    then
    echo "there's already a menu entry"
    else
    if [ $ch == $la ]
    then
    sed -i "/^\[submenu\] ($men)$/a[exec] ($ch) {$ch} </usr/share/icons/hicolor/48x48/apps/$ch.png>" ~/.fluxbox/menu
    sleep 1
    fluxbox restart
    elif [ $ch == $lb ]
    then
    sed -i "/^\[submenu\] ($men)$/a[exec] ($ch) {$ch} </usr/share/pixmaps/$ch.png>" ~/.fluxbox/menu
    sleep 1
    fluxbox restart
    fi
    fi
    fi
    done
    Here  because in pacman.log, the data of installed apps is shown in this manner YY-MM-DD hh:mm I had to consider using "for do", because in a minute a lot of applications can be installed using only a single "$pacman -S apps" command. Therefore I had to add somehow every app installed in a minute, separately to ~/fluxbox/menu. If the data of the installed apps in pacaman.log was show in this manner YY-MM-DD hh:mm:ss, therefore including seconds things would had been a lot more easier and precise, but I had to find a solution to that matter, and that solution was using "for do" .
    Also here it checks if the installed program shows as an executable in /usr/bin and if it has an icon in  /usr/share/icons/hicolor/48x48/apps/ or in /usr/share/pixmaps/, and only than it procedes in adding an entry to fluxbox menu for that app. This was necessary because not all programs installed, that have executables in /usr/bin are meant to be displayed as a fluxbox menu entry. Checking for an icon being a filter and at the same time something kinda useful for the overall aspect of the menu.
    rdata="$(grep "$data" /var/log/pacman.log | grep removed | sed "s/\[//g; s/\].*//g" | tail -1)"
    if [ "$data" == "$rdata" ]
    then
    nrem="$(grep "$data" /var/log/pacman.log | grep removed | wc -l)"
    inrem=$(seq 1 $nrem)
    for i in $inrem
    do
    rem=$(grep "$data" /var/log/pacman.log | grep removed | sed 's/.*removed//g; s/(.*//g; s/ //g' | head -$i | tail -1)
    remr=$(grep "$rem" ~/.fluxbox/menu | sed 's/.*(//; s/).*//' | tail -1)
    if [ $rem == $remr ]
    then
    sed -i "/$rem/d" ~/.fluxbox/menu
    sleep 1
    fluxbox restart
    else
    echo "no menu entry to remove"
    fi
    done
    fi
    This part of the script removes the data from the menu entry pretty much in the same manner it was added, so I won't give further explanations.
    The Trouble:
    Most applications are added and removed just fine in the fluxbox menu entry, but some like chromium are added more than once and after pacman -R app they aren't removed. The script has still a lot of flaws, most of them because I'm new to scripting, but if someone can improve it or give suggestions it would be highly appreciated. Also if anybody that finds the script worthy enough, wants to develop it as his own I have nothing against it, just tell what changes and improvements you have brought as I wanna learn too.
    Also my goal is to make a daemon out of it, any suggestions in this direction would be highly appreciated.
    Thanks for your time and understanding, mostly thanks to those that helped me a bit in understanding the syntax, like  @Karol & @falconindy. You rule, 'cause  you make linux  seam like one big happy family
    George
    Last edited by I'mGeorge (2011-06-20 19:43:08)

    This is an awesome idea. I've wanted to do something like this for a little while, though not in bash...
    Since I'm not great in bash, I may make one in C (for learning) or Python (ditto) and comment on your implementation.
    If I understand right, you're building a menu first, then deleting parts of it as you go. Would it not be smarter to create a function for adding entries and call it only after you've decided whether an app belongs in the menu? Something like this:
    function add_to_menu() {
    # echo whatever to the config file
    if (app is on system && has an icon somewhere in /usr/share or /opt) {
    add_to_menu(foo)
    Personally, I would approach this by using a definition or grouping list (so you can make submenus) and organize your apps that way. I'd probably use an sqlite db or an ini file or some other way to store the heirarchy, then generate the menu. It looks like you've already put a lot of effort into this, though, so I wish you luck on it!

  • CIN Config Guide for MM

    Hello Gurus,
    Can any one provide me the Best Practice Config guide for CIN.
    Thanks N Regards,
    Venu M Gannu
    SAP MM Consultant

    Dear Venu
    You can get material from forum itself for your information
    Please find some details mention below:
    What is CIN?
    CIN Means Country India Version
    In Indian Taxing procedure, Excise Duty plays a vital role in manufacturing cenariou2019s. Excise related configuration is known as CIN configuration. CIN Configuration is a topic in itself.
    Some info on CIN Configuration (it may not appear as understandable below, but if you check on screen, it will be understood better)
    Country Version India comes with four pricing procedures as follows:
    u2022 JINFAC (Sales from manufacturing plants)
    u2022 JINEXP (Export sales)
    u2022 JINDEP (Sales from depots)
    u2022 JINSTK (Stock transfers
    CIN: IMG > Logistics - General > Tax on Goods Movement > India > Basic Settings > Maintain Excise Registrations
    In this IMG activity, you maintain the data relating to your excise registrations.
    u2022 Enter each of your excise registrations, specifying a four-character code for each Excise Registration Ids
    In this activity, you maintain excise registration IDs. You create one ID for each of your business's excise registrations.
    u2022 For each excise registration in your business create a registration ID, and state:
    u2022 Which taxes the registration covers (additional excise duty, special excise duty, and cess) Fields for any taxes that are not covered will be hidden in transactions involving excise duty.
    u2022 The maximum number of items to be printed on each excise invoice
    u2022 Whether you are allowed partial CENVAT credits
    Maintain Registration ID NUMBER, Excise code number, excise registration number
    ECC Number: Specifies the organization's ECC number.
    Excise Registration Number: A number assigned to each premises or location that has registered as a manufacturer with the excise authorities.
    Every entity with an excise registration number is required to keep its own excise books.
    Excise range: Specifies the excise range in whose area the excise registration is located.
    Excise Division: Specifies the excise division in whose area the excise registration is located.
    Excise Collectorate: The code of the excise collectorate in whose area the excise registration is located.
    Indicator for confirming, AED usage Additional Excise duty Percentage.
    These are livable under the additional duties of excise act. These duties are in addition to basic excise duty and special excise duty. Example - Additional Excise duty is livable in case of textile products, tobacco and sugar.
    Similarly for SED CESS Number of Items in Excise Invoice Shows the maximum number of line items that the authorities allow per excise invoice.
    Dependencies - This information is used when you create an excise invoice in Sales and Distribution (SD) for factory sales and for other movements. This information is used to split the transfer postings' items into multiple subcontracting challans.
    Excise register set description: Description of the excise registers set.
    Partial CENVAT Credit: Indicates that the excise registration ID is allowed to credit only a portion of its input excise duty to its CENVAT account
    Dependencies - When you post a goods receipt, the system splits the input excise duty on the material into its deductible and nondeductible amounts. It posts the deductible duty to the appropriate CENVAT account, and adds the nondeductible duty to the material value.
    This information is also shown when you post the vendor's excise invoice.
    Maintain Company Code Settings.
    In this IMG activity, you maintain the data relating to your company codes.
    Document Type for CENVAT Postings.
    It controls, which document type the system uses when making CENVAT postings in Financial Accounting (FI). Here ED is document type for cenvat posting.
    Indicator for providing debit account overwriting
    Debit Account Overwrite Indicator. X - Indicates debit accounts can be overwritten. Use In excise journal voucher transaction. It provides the flexibility to the user to enter the debit account of his choice depending on the nature of transaction.
    Automatic balance Indicator - Excise year start month. The calendar month marking the beginning of the excise year. This start month represents the month for the start of the excise invoice number range. The month 04 is entered here indicating April of the calendar year as the start month for excise invoices. Any change by the Excise authorities regarding start month should be taken care of by an entry in this field and initialization.
    Excise invoice selection procedure :Excise invoice selection type. To indicate the method opted by the company for selecting the excise invoice. It can be either earliest or latest invoices that were received. Number of excise invoices to be selected Indicates the number of excise invoices that needs to be selected in the excise invoice selection.
    Days to be considered for excise invoice selection Number of days from document date for excise invoice selection.
    Example - If the value of this field is 20 and today is 28-03-97. The excise invoice selection will show the related invoices only for the period 08-03-97 to 28-03-97.
    Document type for TDS FI posting: Financial accounting document type for TDS posting.
    Document type for FI posting on Utilisation Financial accounting document type for TDS posting.
    Indicator for item level excise duty round off - This indicator is to be used for deciding whether Item level excise
    duty amount rounding off is required during procurement cycle. If marked 'X' then the excise duty amount will be rounded off to the nearest rupee at the Purchase order level. This will not round off the CENVAT credit to be taken. If the duty amount is less than one rupee then no rounding is done
    Rounding off of Excise duty for outgoing excise invoice - You can round off the Excise amount to be paid during an outgoing
    Excise invoice by marking this indicator as 'X'. The rounding is done at the item level for each item where the amount is greater than 1 Rupee.
    Immediate Credit on Capital Goods - Instructs the system, when you verify a goods receipt for capital goods, to immediately post half of the input excise duty to the appropriate CENVAT accounts. The rest is posted the CENVAT on hold account, for use in the following year.
    CVD Clearing Account - Specifies which G/L account the system credits when you take a CENVAT credit on countervailing duty in the Incoming Excise Invoices transaction.
    Exchange rate type - Key representing a type of exchange rate in the system.
    u2022 You enter the exchange rate type to store different exchange rates. Example - You can use the exchange rate type to define a buying rate, selling rate, or average rate for translating foreign currency amounts. You can use the average rate for the currency translation, and the bank buying and selling rates for valuation of foreign currency amounts.
    Exchange rate type to be used for Export excise duty converts - When you are creating an Excise invoice for export sales then the exchange rate for duty calculation will be picked up using this Exchange rate type.
    Maintain Plant Settings - In this IMG activity, you maintain excise information relating to your plants.
    Plant Settings - In this activity, you maintain excise information relating to your plants.
    For each plant:
    u2022 Specify whether it is a manufacturing site or a depot.
    u2022 Assign it an excise registration ID. - You can assign the same ID to more than one plant, if required.
    Depot - Indicates that the plant in question is a depot. - Depots are required to prepare register RG 23D, and follow different procedures for goods receipt and invoice generation.
    u2022 Number of goods receipt per excise invoice.
    u2022 Multiple GR for one excise invoice, Single credit
    u2022 Multiple GR for one excise invoice, multiple credit
    Maintain Excise Groups - In this IMG activity, you define your excise groups. For each excise group, you can also control how various excise invoice transactions will work.
    Excise Groups - In this activity, you define excise groups. An excise group allows you to maintain a separate set of excise registers and excise accounts. The RG 23A, RG 23C and PLA serial numbers are created for an excise group.
    Recommendation - Under normal circumstances, excise authorities require every business to maintain only one set of excise registers and one set of accounts. But through exemption from the authorities, multiple books can be maintained.
    If your company has only one set of excise registers, then you need to maintain only one excise group.
    1. Create one excise group for each set of registers that you need to keep.
    2. Assign the excise groups to plants.
    3. Maintain whether this Excise group is for a depot or not.
    If you receive only one consignment for an Excise challan then you can leave GR's per EI as blank. If you receive multiple GR's for a given Excise challan and would like to avail multiple credit mark the GRs per EI as 'Multiple GR's for one excise invoice, multiple credit'. Alternatively if you want to availa the credit only after all the goods receipts have been made mark it as ' Multiple GR for one excise invoice, single credit'.
    4. If you want to automatically create Excise invoice during Sales cycle at the time of billing the tick the indicator 'Create EI'
    5. During depot sales if you do not want to do RG23D selection and posting separately and would like to complete RG23D selection in one step mark the indicator 'RG23D Auto post'. This will post the selected records into RG23D automatically. You cannot cancel the selection later.
    6. If the indicator 'Default GR qty' is marked system will default the Excise challan quantity on to the Goods receipt if the Excise invoice number is given in the pop-up.
    7. If the indicator 'Folio no create' is marked system will generate Folio numbers for RG23D during receipt of excise invoice into depot.
    8. 'Automatic posting' when ticked will post the Excise invoice other movements automatically along with creation in single step.
    9. 'Create Part1 for Block Stock' when marked will create a Part1 during the receipt of material into Blocked stock .
    10. 'Create Part1 for STO' when marked will create a Part1 during the receipt of material through inter plant transfers.
    11. 'Create Part1 for consumption stock' when marked will create a Part1 during the receipt of material into consumption stock. Excise Group Governs which set of excise registers a business transaction will be included in.
    Following is the relation between excise group, plant and registration. - In define excise groups in Customizing.
    Then, in transactions involving excise duty, for example, when you post a vendor's excise invoice, you specify which excise group you are using. This information tells the system which G/L accounts to post the excise to. At the end of the period, when you come to prepare your excise registers, you create different sets for each excise group.
    Indicates that the plant in question is a depot. - Depots are required to prepare register RG 23D, and follow different procedures for goods receipt and invoice generation.
    u2022 GR Per Excise Invoice
    u2022 Multiple GR for one excise invoice , Multiple credit
    u2022 Multiple GR for one excise invoice , Single Credit
    Create Excise Invoice Automatically - Instructs the system to automatically create a Sales and Distribution (SD) excise invoice immediately you create a commercial invoice or a pro forma invoice.
    The excise invoice is created in the background. - If you want to make use of this function, you must also define the
    default plant, excise group, and series groups in Customizing for Sales and Distribution (SD), by choosing Excise Group - Series Group Determination.
    RG23D Sales Creation and posting option - RG23D Automatic Option if selected will create Depot excise invoice by posting the selection of excise invoices in single step. If this is not selected then you need to separately do RG23D selection
    followed by PGI and then RG23D verification and posting. If you need automatic posting of RG23D selection then the Post Goods Issue should have been completed before running RG23D selection.
    Default excise qty in GR - If this indicator is ticked then while doing Goods Receipt using 'MB01' system will default the excise invoice quantity on to the Goods receipt document.
    Folio number for depo Posting - If this indicator is marked then while creating Excise invoice for other movements system automatically does the Verify and Post. You need not separately Post the excise invoice
    Also we can set indicator for creation of part 1 for:
    u2022 Blocked stock
    u2022 Stock transport order
    u2022 Consignment stock
    Maintain Series Group - In this IMG activity, you define the different excise series groups within your company. Series groups allow you to maintain multiple number ranges for the outgoing excise documents. Based on excise regulations and exemptions from the authorities you can maintain multiple number series for outgoing documents. But each of these series has to be declared to the excise authorities.
    u2022 Define excise series groups based on type of outgoing document
    u2022 Assign series group to excise registration ID
    u2022 If no financial postings are required for an Excise invoice in this seris group then you tick the 'No utilization' indicator.
    u2022 If the CENVAT has to be paid immediately and you need not wait for the Fort nightly payment then mark the 'Immediate Utilization' Iindicator. Example - You could define two series groups, group 001 for excise invoices, and group 002 for 57 F4 documents.
    u2022 No account postings for CENVAT in sales cycle
    u2022 No utilization Flag
    If you do not need any CENVAT utilization for an excise invoice but would like to just generate an excise invoice then you need to mark this indicator.
    If the flag is checked then system will create an Excise invoice in the given Series group but there will not be any account postings or Part2 postings.
    Immediate Utilization of CENVAT - Specifies that when you create an excise invoice, the system immediately pays the amount from CENVAT and creates the Part II entry. Such invoices will not be listed for fortnightly utilization.
    If you have both fortnightly and immediate utilization for the same excise group, the account determination within CIN IMG should point to the ED interim account.
    Account determination for immediate payment will be done exactly the same as being done for fortnightly utilization program.
    Maintain Excise Duty Indicators - In this IMG activity, you maintain the excise duty indicators.
    IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination of Excise Duty > Select Tax Calculation Procedure
    In this IMG activity, you specify which tax procedure you want to use for determining excise duties and sales taxes on input materials in India.
    u2022 If you use condition-based excise determination, use a copy of the tax procedure TAXINN.
    u2022 If you use formula-based excise determination, use a copy of the tax procedure TAXINJ.
    This tax procedure also supports condition-based excise determination, so that you can work with both concurrently.
    We strongly recommend that new customers use condition-based excise determination. Note that once you have started using a tax procedure, you cannot switch to another one, otherwise you will not be able to display old documents.
    Maintain Excise Defaults - In this IMG activity, you define which tax procedure and pricing condition types are used in calculating excise taxes using formula-based excise determination.
    If you use condition-based excise determination, fill out the CVD cond. field and leave all the others blank.
    If you use formula-based excise determination, fill out all of the fields as follows:
    u2022 Enter the tax procedure and the pricing conditions that are relevant for excise tax processing.
    u2022 Specify the purchasing and sales conditions types used for basic excise duty, additional excise duty, special excise duty, and cess.
    u2022 Specify the conditions in the sales order that are used for excise rates.
    u2022 Specify the countervailing duty condition type used for import purchase orders.
    See also : SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> Condition-Based Excise Determination and -> Formula-Based Excise Determination.
    IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination of Excise Duty >
    Condition-Based Excise Determination
    When you enter a purchasing document, for example, a purchase order, the R/3 System automatically calculates the applicable excise duties using the condition technique.
    Features : The standard system comes with two tax calculation procedures. TAXINN is only supports condition-based excise determination, whereas TAXINJ supports condition-based excise determination and formula-based excise determination. Both tax procedures contain condition types that cover all of the excise duties and sales taxes applicable.
    Since the exact rates of excise duty can vary on a large number of factors, such as which vendor you purchase a material from, or which chapter ID the vendor stocks the material under, you create condition records for every sort of excise duty.
    When you come to enter a purchasing document, the system applies the excise duty at the rates you have entered in the condition records.
    Customizing : Make the settings in Customizing Basic -> India -> for Logistics u2013 General, by choosing Taxes on Goods Movements Account -> Excise Duties Using Condition Technique and u2026-> Settings Determination.
    These activities include one activity where you define a tax code for condition-based excise determination.
    Master Data - Create condition records for all excise duties that apply, and enter the tax code for condition-based excise determination in each.
    Day-to-Day Activities - When you enter a purchase order or other purchasing document, enter the tax code for condition-based excise determination in each line item. The system then calculates the excise duties using the condition records you have created.
    When the ordered materials arrive, you post the goods receipt and the excise invoice. The system posts the excise duty to the appropriate accounts for deductible input taxes when you enter the excise invoice.
    Creating Condition Records for Excise Duty
    1. In the command field, enter FV11 and choose .
    2. Enter the condition type that you want to create a condition record for and choose .
    The Key Combination dialog box appears.
    3. Select the combination of objects that you want to create the condition record for. On the dialog box, Control Code means "chapter ID." So, for example, to create a condition record for a tax that applies to a combination of country, plant, and chapter ID, select Country/Plant/Control Code.
    4. Choose .
    5. Enter data as required. - In the Tax Code field, enter the dummy tax code that you have defined.
    6. Save the condition record.
    Formula-Based Excise Determination - When you execute a business transaction involving materials that are subject to excise duty, the system automatically calculates the duty for you.
    In order for the system to be able to determine which rate of excise duty to apply, you must have maintained all the data on the Excise Rate Maintenance screen, which you can Master Data®access from the SAP Easy Access screen by choosing Indirect Taxes Excise Rate Maintenance.
    You maintain the following types of data:
    u2022 Plant master data
    You assign each of your plants an excise duty indicator. You can use the same indicator for all the plants with the same excise status from a legal point of view, such as all those that are in an exempt zone. See also the information about manufacturers that are only entitled to deduct a certain portion of the duty (see Partial CENVAT Credit).
    u2022 Vendor master data
    For each of your vendors with the same excise status from a legal perspective, you define an excise duty indicator. You must also specify the vendor type u2013 for example, whether the vendor is a manufacturer, a depot, or a first-stage dealer. You must also stipulate if the vendor qualifies as a small-scale industry. For each permutation of plant indicator and vendor indicator, you then create a final excise duty indicator.
    u2022 Customer master data
    Similarly, you assign the same excise duty indicator to each of your customers that share the same legal excise status.
    Again, for each permutation of plant indicator and customer indicator, you then create a final excise duty indicator.
    u2022 Material master data
    Each material is assigned a chapter ID.
    u2022 Excise tax rate
    For every chapter ID and final excise duty indicator, you maintain the rate of excise duty.
    If your business only qualifies for partial CENVAT credit, you must customize your system accordingly.
    Let us consider an example to illustrate how the system determines which rate of excise duty to apply to a material. Assume you are posting a sale of ball bearings to a customer. The system automatically determines the rate of excise duty as follows:
    1. Looks up the customer master data to see what status you have assigned the customer.
    Let's assume you've assigned the customer status 3.
    2. Looks up the plant master data to see what status you have assigned the plant. Similarly, your plant has status 2.
    3. The system looks up the table under Excise Indicator for Plant and Customer to see what the final excise duty indicator is for customer status 3 and plant status 2: It is 7.
    4. The system determines the chapter ID of the ball bearing for the plant.
    Letu2019s assume the chapter ID at plant for the ball bearings is 1000.01.
    5. Finally, the system looks up the table under Excise Tax Rate to see what rate of duty applies to chapter ID 1000.01 under
    status 7.
    Define Tax Code for Purchasing Documents - In this IMG activity, you define a tax code for the purposes of calculating excise duty when you enter purchasing documents. Only carry out this activity if you use condition-based excise
    determination.
    u2022 Create a new tax code, and set the tax code type to V (input tax). Do not make any other settings for it.
    u2022 Assign Tax Code to Company Codes
    In this IMG activity, assign the tax code for purchasing documents to the company codes where it will be used.
    Only carry out this activity if you use condition-based excise determination.
    Classify Condition Types - In this IMG activity, you specify which condition types you use for which sort of tax. Note that this only applies to condition types that you use with the new excise determination method. The system uses this information when you create a document from another one. For example, when you enter an incoming excise invoice from a
    purchase order, or when you create an outgoing excise invoice from a sales order, the system determines the various excise duties in the excise invoice using the information that you have entered here. In addition, when you create a purchasing document, the system only uses the condition types that you enter here.
    u2022 For taxes on purchases, use the condition types contained in the tax procedure.
    u2022 For taxes on sales, use the condition types contained in the pricing procedures.
    The standard system comes with sample settings for the tax calculation procedures and pricing procedures.
    Use these settings as a basis for your own.
    IMG > Logistics - General > Tax On Goods Movement > India > Account Determination
    Define G/L Accounts for Taxes - In this IMG activity, you specify which G/L accounts you will use to record which taxes.
    Requirements - You have set up G/L accounts for each of the processing keys listed below.
    u2022 Assign an account to each of the following posting keys. The accounts for VS1, VS2, and VS3 are used as clearing accounts during excise invoice verification.
    u2022 VS1 (basic excise duty)
    u2022 VS2 (additional excise duty)
    u2022 VS3 (special excise duty)
    u2022 VS5 (sales tax setoff)
    u2022 MWS (central sales tax)
    u2022 MW3 (local sales tax)
    u2022 ESA (service tax)
    u2022 ESE (service tax expense)
    Specify Excise Accounts per Excise Transaction - In this IMG activity, you specify which excise accounts (for excise
    duty and CENVAT) are to be posted to for the various transaction types. Enter all the accounts that are affected by each transaction type. If you use sub transaction types, enter the accounts for each sub transaction type as well.
    Transaction type UTLZ is used for determining accounts only while posting excise JVs and also if the payment of excise duty has to be done fortnightly. The fortnightly CENVAT payment utility picks up the credit side accounts from the transaction types of GRPO, EWPO, and TR6C for determining the CENVAT and PLA accounts. There is no separate transaction type for fortnightly payment.
    Example:
    u2022 Excise TT DC ind Account name
    u2022 GRPO CR CENVAT clearing account
    u2022 GRPO CR RG 23 BED account
    u2022 GRPO DR CENVAT on hld account
    Specify G/L Accounts per Excise Transaction - In this IMG activity, you assign the excise and CENVAT accounts to G/L
    accounts. When you come to execute the various transactions, the system determines which G/L accounts to post to by looking at the:
    u2022 Excise group
    u2022 Company code
    u2022 Chart of accounts
    Furthermore, if you want separate account determination settings within an excise group, you can also use sub transaction types.
    Requirements
    You have already:
    u2022 Defined the G/L accounts
    u2022 Defined the excise groups
    u2022 Maintained the transaction accounts
    Activities - For each excise group, assign the excise and CENVAT accounts to G/L accounts. For most businesses, one set of accounts will suffice for all transactions.
    Note : you need not remit the CENVAT to the excise department immediately, so maintain the credit account for transaction type DLFC as an excise duty interim account. This will be set off when you remit the duty. Config setting needed to be done in order to get the Excise Details Screen in Material Master.
    Even though this functionality is available in enterprise version, a small configuration step has to be made in Screen Sequences for Material Master.
    Following document helps you to do this configuration.
    u2022 Material Master à Logistics General
    1. Go to IMG Define Structure of Data Screen for each Configuring the Material master Screen Sequence.
    2. Select your screen sequence. Usually it would be 21. Select the same and click on Data Screen in the left frame.
    3. Once the data screens are exhibited, select data screen no. 15, ie. SSq. 21and Scrn 15, which is u201CForeign Trade: Import Datau201D. Select the same and click on Sub screens in the left frame.
    4. Go to the last sub screen i.e. 21-15-6 - SAPLMGD1- 0001 and select the same. Click on tab view sub screen and ensure that the sub screen is blank.
    5. Now in the last sub screen i.e. no.6 you delete SAPLMGD1 u2013 0001 and instead add SAPLJ1I_MATERIAL_MASTER and in the screen no. 2205.
    6. Save the setting.
    7. Create a Material Master and check whether in Screen Foreign Trade
    u2013 Import, Excise related sub screen appears.
    ***CIN CONFUGURATION***
    1.1 Maintain Excise Registration
    SPRO BasicSAP Ref. IMG Maintain Logistics general  tax on Goods MovementsIndia setting Excise Registrations
    APPLICABLE
    1.2 Maintain Company Code Settings
    SPRO Maintain Company Code SAP Ref. IMG  Logistics general tax on Goods Movements SettingsIndia Basic setting
    APPLICABLE
    1.3 Maintain Plant Settings
     tax on Goods MovementsIndia  Basic setting SPRO SAP Ref. IMG Maintain Plant SettingsLogistics general
    APPLICABLE
    1.4 Maintain Excise Groups
     Logistics general  tax on Goods MovementsIndia SPRO Basic setting Maintain Excise GroupsSAP Ref. IMG
    APPLICABLE
    1.5 Maintain Series Groups
    SAP Ref. Logistics general  tax on Goods MovementsIndia  Basic settingSPRO Maintain Series GroupsIMG
    APPLICABLE
    1.6 Maintain Excise Duty Indicators
    SAP Ref. Logistics general tax on Goods MovementsIndia  Basic setting SPRO Maintain Excise DutyIMG Indicators
    APPLICABLE
    1.7 Maintain Sub transaction Type with Text
    SPRO SAP Ref. IMG  Logistics general  tax on Goods MovementsIndia  Basic settingMaintain Sub transaction Type with Text
    APPLICABLE
    1.8 Determination of Excise Duty
    SPRO SAP Ref. IMG  Logistics general tax on Goods MovementsIndia  Determination of Excise DutySelect Tax Calculation Procedure
    APPLICABLE
    1.9 Maintain Excise Defaults
    SPROSAP Ref. IMG Logistics general  tax on Goods MovementsIndia Determination of Excise DutyMaintain Excise Defaults
    APPLICABLE
    1.10 Condition-Based Excise Determination
    SPRO Define Tax SAP Ref. IMG  Logistics general tax on Goods Movements PurchasingIndia  Condition-Based Excise DeterminationCode for Documents
    APPLICABLE
    1.11 Condition-Based Excise Determination
    tax SPRO Assign Tax Code to SAP Ref. IMG  Logistics general on Goods Movements CompanyIndia Condition-Based Excise Determination Codes
    APPLICABLE
    1.12 Classify Condition Types
    SPROSAP Ref. IMG Logistics general  tax on Goods MovementsIndia Condition-Based Excise DeterminationClassify Condition Types
    APPLICABLE
    1.13 Maintain Chapter IDs
    SPRO Maintain SAP Ref. IMG  Logistics general tax on Goods MovementsIndia  Master dataChapter ids
    APPLICABLE
    1.14 Assign Users to Material Master Screen Sequence for Excise Duty
    MasterSPRO  SAP Ref. IMG Assign Logistics general  tax on Goods MovementsIndia data Users to Material Master Screen Sequence for Excise Duty
    APPLICABLE
    1.15 Specify Excise Accounts per Excise Transaction
    SPRO Specify SAP Ref. IMG  Logistics general tax on Goods MovementsIndia  Account determinationExcise Accounts per Excise Transaction
    APPLICABLE
    1.16 Specify G/L Accounts per Excise Transaction
    SPRO Specify G/L SAP Ref. IMG  Logistics general tax on Goods MovementsIndia  Account determinationAccounts per Excise Transaction
    APPLICABLE
    1.17 Incoming Excise Invoices
    SPROSAP Ref. IMG Incoming Logistics general  tax on Goods MovementsIndia Business TransactionsExcise Invoices
    APPLICABLE
    1.18 Define Processing Modes Per Transaction
    SPRO Define Processing SAP Ref. IMG  Logistics general  tax on Goods Movements PerIndia  Business TransactionsModes Transaction
    APPLICABLE
    1.19 Define Reference Documents Per Transaction
    SPRO Define Reference SAP Ref. IMG  Logistics general tax on Goods MovementsIndia  Business TransactionsDocuments Per Transaction
    APPLICABLE
    1.20 Maintain Rejection Codes
    SPROSAP Ref. IMG Maintain Logistics general  tax on Goods MovementsIndia Business TransactionsRejection Codes
    APPLICABLE
    1.21 Specify Which Movement Types Involve Excise Invoices
    SPRO Specify Which SAP Ref. IMG Logistics general Movement Types tax on Goods MovementsIndia Business Transactions Involve Excise Invoices
    APPLICABLE
    1.22 Outgoing Excise Invoices
    Outgoing ExciseSPRO Assign SAP Ref. IMG  Logistics general tax on Goods Movements Billing Types to DeliveryIndia  Business TransactionsInvoices Types
    APPLICABLE
    1.23 Maintain Default Excise Groups and Series Groups
     Outgoing Excise Invoices SPRO  SAP Ref. IMG  Logistics general  tax on Goods Movements Maintain Default ExciseIndia Business Transactions Groups and Series Groups
    APPLICABLE
    1.24 Subcontracting Attributes
    SPRO Subcontracting SAP Ref. IMG  Logistics general tax on Goods MovementsIndia  Business TransactionsSubcontracting Attributes
    APPLICABLE
    1.25 Maintain Movement Type Groups
    SPRO SAP Ref. IMG Logistics general  tax on Goods MovementsIndia Business Transactions Attributes SubcontractingSubcontracting
    APPLICABLE
    1.26 Utilization Determination
     tax on Goods MovementsIndia SPRO BusinessSAP Transactions UtilizationRef. IMG UtilizationLogistics general Determination
    APPLICABLE
    1.27 Specify SAP script Forms
    tax on GoodsIndia SPRO Business ExciseSAP Ref. IMG Specify SAP script Logistics general Movements Transactions FormsRegisters
    APPLICABLE
    1.28 Number Ranges
    SAP Logistics general tax on Goods MovementsIndia  ToolsSPRO NumberRef. IMG Ranges
    APPLICABLE
    1.29 Message Control
    SPRO SAP Ref. IMG  Logistics general tax on Goods MovementsIndia  ToolsMessage Control
    APPLICABLE
    J1I2
    Prepare a sales tax register
    J1I3
    Create outgoing excise invoices in batches
    J1I5
    Update the RG 1 and Part I registers
    J1IEX
    Incoming Excise Invoices (central transaction)
    J1IEX_C
    Capture an incoming excise invoice (excise clerk)
    J1IEX_P
    Post an incoming excise invoice (excise supervisor)
    J1IF01
    Create a subcontracting challan
    J1IF11
    Change a subcontracting challan
    J1IF12
    Display a subcontracting challan
    J1IF13
    Complete, reverse, or recredit a subcontracting challan
    J1IFQ
    Reconcile quantities for subcontracting challan
    J1IFR
    List subcontracting challan
    J1IH
    Make a CENVAT adjustment posting
    J1IIN
    Create an outgoing excise invoice
    J1IJ
    Assign excise invoices to a delivery for sales from depots
    J1INJV
    Adjust withholding tax Item
    J1INREP
    Reprint a withholding tax certificate for a vendor
    J1IQ
    Year-End Income Tax Depreciation Report
    J1IR
    Download register data
    J1IS
    Process an excise invoice (outgoing) for other movements
    J1IU
    Process exemption forms
    J1IW
    Verify and post an incoming excise invoice
    J1IX
    Create an incoming excise invoice (without reference to purchase order)
    J2I8
    Transfer excise duty to CENVAT account
    J2IU
    Remit excise duty fortnightly
    J2I9
    Monthly CENVAT return
    J1IG
    Excise invoice entry at depot
    J1IGA
    Create additional excise entry at depot
    J2I5
    Extract data for excise registers
    J2I6
    Print excise registers
    Regds
    shailesh

  • Application wide popup menu for JTextComponent descendants

    Hi!
    I'm working on large project with reach Swing GUI and I got stuck with one small but wery annoing problem. I have to append simple popup menu to all text input fields (JTextComponent descendants) in whole application. I'm realy lazy to append mouse listener on each component, so I'm asking, is there any way to append "default" popup menu for all components. Please, don't answer about custom components instead of Swing plain JTextComponent descendants - it's worse to change classes for all fields then add mouse listener to them.
    As an example of what I want I could forward you to UIManager.put() method, which affects all properties of component behaviour thoughout application. I want to find same solution, maybe there any registry or smth. else in API.
    Than you in advice.

    You could always try extending something like MetalTextFieldUI so that it adds the listeners to the text field automatically. You'd then need to register that UI class with the UIManager at startup:
    public class MyTextFieldUI extends MetalTextFieldUI {
      protected void installListeners() {
        super.installListeners();
        // TODO - Install your listener here
      protected void uninstallListeners() {
        super.uninstallListeners();
        // TODO - Uninstall your listener here
    UIManager.put("TextFieldUI", MyTextFieldUI.class.getName());Personally, I think you're just being lazy... getting your components to extend a subclass of JTextField should be no trouble at all and will leave you with clearer code.
    Hope this helps.

  • You changed the order of the menu for "Open in a new window" or "Open in new Tab", How can I change it back? Or how can I omit any reference to tabs? I do not use them at all.

    You changed the order of the menu for "Open in a new window" or "Open in new Tab", How can I change it back? Or how can I omit any reference to tabs? I do not use them at all.

    You can use the Menu Editor add-on to rearrange or remove menu items - https://addons.mozilla.org/firefox/addon/menu-editor

  • Specifying coherence-cache-config.xml for multiple clusters

    Hi,
    I am running two cache clusters (Cluster A and B that hold different cache types). we have a web application that needs to communicate with both the clusters. we have two coherence-cache-config-g.xml files, one for each cluster.
    where do we specify the two coherence-cache-config.xml for each of these clusters in our coherence.jar that we deploy on the web app server.
    pls provide some inputs...
    thanks in advance,
    - G.

    Hi G,
    You can define a path to the cache configuration descriptor in your operation configuration override file (tangosol-coherence=override.xml) or specify it in the system property "tangosol.coherence.cacheconfig".
    Please see this Wiki page for details:
    http://wiki.tangosol.com/display/COH32UG/configurable-cache-factory-config
    Regards,
    Gene

  • How can i create a drop down menu for set qty in my store?

    I'm wondering how i can create a drop down menu for the qty module that sits on the individual product page. My client sells in quantities of 6 packs. I currently have the minimum order at 6 but i would like to give consumers the option for 6,12,18...and so forth. I was told that it could be accomplished? Hopefully someone can help me.

    Hi Chris -
    Thank you for your reply! I had seen your article before, and just now again attempted to follow it, but I get stuck. There are two things that I'm confused by.
    First off, toward the top, referring to the initial button, you say to add this interaction:
    ON CLICK; Play Transition to comboBox: selected
    ON ROLL OUT; Play Transition to comboBox normal if comboBox is in over state
    ON ROLL OVER; Play Transition to comboBox over if comboBox is in normal
    However, I do not see these transition options. When I select the button, the only interactions I have are to Play transistion to state, Play action sequence, Go to URL, and two for videos. So that's the first roadblock for me.
    But, trying to get passed that, I went down to the portion of the article that refers to adding interaction to the dataset items. Again, I don't get it, as I see no way to add interaction to a dataset item. When I open my design-time data menu, I do see the items, and am able to rename each item, add additional rows, and change the shape of the datalist layout. However, I see no way to add an interaction to a dataset item. I must be missing a step ... Can you help with this?
    Again, thank you!
    Amy

  • Is there a way to create a vertical menu for tablet that stays in place?

    I am a novice in web design, and I want to make a vertical menu for a tablet page that stays in place.
    It should not scroll, and  it has to resize depending on screen size, so it looks the same across different tablet sizes.
    Is this possible in Muse? After reading some posts I am getting the feeling this is not possible at all, is that really true?
    If it can't be done in Muse, can I do it another  way? In Dreamweaver for instance?
    The reason I want this is that in my opinion horizontal menu's for tablets are ergonomically bad design, and just plain annoying. You always have to use two hands, lift one hand and then you probably block the view of the screen.
    Vertical menu's for tablets just make more sense since they can be made so that you could place them on the side of the screen so it would be possible to navigate with the hand that is holding that side of the tablet.
    I hope someone can help me.

    Yes, I am using the widget.
    It seems it is not possible to make the menu stick in tablet design (the pin options are greyed out). Nor is it possible to make the menu scale with screen sizes.
    A possible solution would be the ability to make it stretch to 100% screen size, like you can with horizontal objects.
    I have noticed though, that, for some reason, in web design it is discouraged or very hard to make things stretch 100% vertically. It seems to cause problems, and I don't understand why.
    Since I have started in web design, I have seen many posts of people having design problems, where stretching 100% vertically would be the obvious solution.

  • I could no longer find hotspot menu for sharing my cellular data on IOS 8.1.3. Please help!

    i have just upgraded to IOS 8.1.3 from IOS 7.1.2 , and I could no longer find my hotspot menu for sharing my cellular data with my other devices.
    what should I do?

    Hello rotimifelix,
    Thank you for contributing to the Apple Support Communities.
    If Personal Hotspot doesn't seem to be enabled on your iPhone after updating to iOS 8, check for the option in both of these locations in Settings:
    Turn Personal Hotspot off and on: Tap Settings > Personal Hotspot or Settings > Cellular > Personal Hotspot.
    If the menu option can't be found, you may want to contact your carrier to ensure your account is set up correctly:
    Verify that your carrier supports Personal Hotspot for your device and that you have Personal Hotspot enabled on your cellular plan:
    iPhone: View a list of carriers that support Personal Hotspot on the iPhone.
    If the issue continues, try these troubleshooting steps next:
    Reset your network settings: Tap Settings > General > Reset > Reset Network Settings.
    If you still see the issue, restore the iPhone.
    You can find the information and steps above, as well as more troubleshooting advice, in these support articles:
    iOS: System requirements for Personal Hotspot - Apple Support
    iOS: Troubleshooting Personal Hotspot - Apple Support
    Best Regards,
    Jeremy

Maybe you are looking for