Payslip related Configurations..

Hi All,
Need your assistance.
Weu2019re implementing New company code in HR u2026
We have company 1000 and 2000 company code u2026,
Now we want user who belong to 1000 company code, when they log-in on portal and see the salary slip then company code 1000 logo should display on Salary Slip.
User who belong to 2000 company code, when they log-in on portal and see the salary slip then company code 2000 logo should display on Salary Slip.
Could you please share what configuration need to perform for this u2026

the feature is HRFOR, You need to implement the BADI or proxy class to ensure different forms are picked depening on employees company code.
Please check if BADI XSS_REM_INTERFACE(note 901850)

Similar Messages

List of BW Related Configurations

Hi All,
Does anyone here know if there is a list that contains all the SAP BW 7 related configurations that are not transportable?
As i am preparing to transport the BW Objects from my development to quality environment, i am wondering if such a list exist so that i can check what needs to be configured directly in the new environment like Number Range, Factory Calendar, Exchange Rates etc.
Many thanks in advance! =)

Hello,
Hello,
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/30422873-8369-2d10-ddb5-e516359259f1?QuickLink=index&overridelayout=true
http://help.sap.com/saphelp_nw04/helpdata/en/e6/beb24053c13f5fe10000000a155106/content.htm
Hope the below links will help you for BW configuration.
Regards,

Managing Consumer Proxies and related configuration in the System Landscape

Hi,
I have successfully created and tested the Consumer proxy in our development server.
Scenario background: A Java Web Service has been developed and deployed on the Portal server which i am consuming in ECC6.0 in ABAP.
We would soon need to move it through the system landscape concerning which i have the following queries:
1. The Consumer Proxy was created with the WSDL URL of the Development Portal server. I checked the Consumer proxy and did not find any signature of the WSDL URL in the Consumer proxy object generated. Can we therefore transport this consumer proxy to QA/Production without any issues?
2. The Logical port configuration - What's the standard used in its maintenance across the landscape? Will we need to manually do it in every system? Can this also be made generic and transported across the landscape?
regards
Nitesh

Hi,
Logical port you can create in two ways.
One using LPCONFIG and other is using the SOAMANAGEr.
When you create a logical port using LPCONFIG you get the Customizing transport request which is client dependent. you can move this to any land scape. Only the thing we need to do change in the port is just accessing URL.
But the latest transaction SOAMANAGER does't give any transport number. I guess there should be a way for this too. If not then there is only one choice left is configure on each client.
Thanks,
Kishore.

Sabrix related configuration in SAP system

Can anyone let me know, what are the necessary configuration we need to do in SAP system to use Sbrix for the tax calculation?

Hi,
Logical port you can create in two ways.
One using LPCONFIG and other is using the SOAMANAGEr.
When you create a logical port using LPCONFIG you get the Customizing transport request which is client dependent. you can move this to any land scape. Only the thing we need to do change in the port is just accessing URL.
But the latest transaction SOAMANAGER does't give any transport number. I guess there should be a way for this too. If not then there is only one choice left is configure on each client.
Thanks,
Kishore.

Cisco 6500 Power Supply and related configurations if any?

Hi,
My query is with regards to the best practices deployed for connecting Cisco 6509 switches in the DC, attached is the existing and proposed setups, also would appreciate getting the related switch configs to acheive redundancy and high availability of the switches in the DC network.
Regs,
Mahesh

Hi,
this depends on what power-supplies you have and how loaded your chassis is.
For Example:
When your chassis is loaded with
     1x Sup720
     8x GE-TX Linecard (WS-X6748)
     2x 3kW Power-Supplies (WS-CAC-3000W)
Then you have to run the chassis in Combined-Mode because, even if there is no second Sup, the same power is allocated to the second sup-slot as if there were one installed.
Having 2x 6kW Power-Supplies, then you should run your chassis in Redundancy-Mode and go with your proposed setup.
for combined-mode use:
cat6k(config)# power redundancy-mode combined
for redundancy-mode use:
cat6k(config)# power redundancy-mode redundant
verify with:
cat6k# show power
system power redundancy mode = combined
Hope this helps!
regards,
    Dirk

Relation configuration problem

I have association between dms assembler
<destination id="company">
<adapter ref="java-adapter"/>
<properties>
<source>samples.crm.CompanyAssembler</source>
<scope>application</scope>
<metadata>
<identity property="companyId"/>
<one-to-many property="employees"
destination="employee"/>
</metadata>
</properties>
</destination>
<destination id="employee">
<adapter ref="java-adapter"/>
<properties>
<source>samples.crm.EmployeeAssembler</source>
<scope>application</scope>
<metadata>
<identity property="employeeId"/>
</metadata>
</properties>
</destination>
In client side i fill collection of Company object from
dsCompany DataService
I make on client side new Company and add for this company
some of employees, execute
dsCompany.createItem(company).First executes EmploeeAssembler
and create collection Employee but Company
no exist yet. How configurate assotiation for dms assembler
that first cratete new company and afrer create collection of
employee?

I have association between dms assembler
<destination id="company">
<adapter ref="java-adapter"/>
<properties>
<source>samples.crm.CompanyAssembler</source>
<scope>application</scope>
<metadata>
<identity property="companyId"/>
<one-to-many property="employees"
destination="employee"/>
</metadata>
</properties>
</destination>
<destination id="employee">
<adapter ref="java-adapter"/>
<properties>
<source>samples.crm.EmployeeAssembler</source>
<scope>application</scope>
<metadata>
<identity property="employeeId"/>
</metadata>
</properties>
</destination>
In client side i fill collection of Company object from
dsCompany DataService
I make on client side new Company and add for this company
some of employees, execute
dsCompany.createItem(company).First executes EmploeeAssembler
and create collection Employee but Company
no exist yet. How configurate assotiation for dms assembler
that first cratete new company and afrer create collection of
employee?

Populating configuration items: Computers, Services and People under Related Items tab in Computer CI form

Hi,
We have integrated SCCM and SCOM with SCSM to import the CI information in CMDB.
We are able to import few CI information from SCCM regarding softwares, OS, etc and from SCOM regarding hardware and discovered objects.
When we open the Computer CI in SCSM, we are able to relate almost all the fields from SCCM and SCOM expect Related items tab.
The Configuration Items: Computers, Services and People are empty under related items tab on Computer CI form.
Kindly please help me to understand regarding this related items tab.
Any help will be very much appreciated.
Thanks
Kumaresan Lakshmanan

Hi,
The Related Items is not automatically populated by any out-of-box connector. You can manually add related configuration items there. What were you expecting to show up under this section?
Regards,
Dieter

[SOLVED}_How can I configure ALSA to use usb-soundcard as default?

Hello,
I am trying to figure out how to configure ALSA correctly on my system. I have tried several times following those guides : ALSA_Arch_Wiki, ALSAProject_WIKI_Usb-audio and ALSAProject_hda-intel .
As I understand there are three main files for alsa-configuration. /etc/modprobe.d/file_name.conf, /etc/asound.conf, ~/.asoundrc . Right now I have tried this:
# This File is empty for NOW
pcm.usb-audio {
type hw
card 0
ctl.usb-audio {
type hw
card 0
pcm.softvol {
type softvol
slave {
pcm "dmix"
control {
name "Master"
card 0
pcm.!default {
type plug
slave.pcm "softvol"
pcm.hda-intel {
type hw
card 1
ctl.hda-intel {
type hw
card 1
pcm.softvol {
type softvol
slave {
pcm "dmix"
control {
name "Master"
card 1
pcm.!default {
type plug
slave.pcm "softvol"
But after second reboot My built in soundcard is default again.
cat /proc/asound/cards
0 [SB ]: HDA-Intel - HDA ATI SB
HDA ATI SB at 0xfe024000 irq 16
1 [HDMI ]: HDA-Intel - HDA ATI HDMI
HDA ATI HDMI at 0xfdffc000 irq 27
2 [CODEC ]: USB-Audio - USB Audio CODEC
Burr-Brown from TI USB Audio CODEC at usb-0000:00:12.1-3, full speed
I want to have usb-soundcard as default without disabling my HD built in soundcard. For example, when i am using specific apps i want both soundcards available for example mixxx.
Can anybody guide me to the right direction?
Last edited by zabrielza (2015-03-27 17:07:27)

V1del wrote:
You don't have to have to use every config file theoretically possible and your current setup is probably in such a mess that you are blocking yourself with conflicting configuration. Post the contents of all ALSA related configfiles you might have
/etc/asound.conf
~/.asoundrc (and other ones in your home directory)
In general on a one user standard system you only need an /etc/asound.conf and a /etc/modprobe.d/alsa-base.conf any other file is for user-specific configuration which you don't need on a one user system.
EDIT: If that what you posted up there is your current asound.conf, you are resetting your default card away from the usb again. Remove all other definitions except the ones pertaining to your usb card for now to see if you get it working then (and they should have unique names so you should use e.g. pcm.softvolhda-intel if you want softvol for your intel etc otherwise you overwrite previous definitions)
Personally I'd also suggest you switch to using pulseaudio, as it covers all your usecases with way less specific configuration necessary, you could remove all your ALSA config (except the modprobe one) and install pulseaudio-alsa and pavucontrol to control the correct devices. But that's just me, we can still get ALSA to work if you want to get ALSA to work.
I do not have other alsa-related configuration files. /etc/asound.conf and .asoundrc do not exist. In other thread about resetting/restoring alsa, i was told to remove all three files, /etc/modprobe.d/alsa-base.conf, /etc/asound.conf and .asoundrc . So i did. And then I created again /etc/modprobe.d/alsa-base.conf with the contents i wrote above. So, no, these contents are not in /etc/asound.conf. but in /etc/modprobe.d/alsa-base.conf .
Oh, I prefer to work with alsa for now. As I told before there are educational reasons for that too
Last edited by zabrielza (2015-03-26 09:35:44)

IDOC configuration in 46C for BI 7

Dear Experts
Is there a set of steps to create the idoc configurations in R/3 for data transfer between R/3 46C and BI 7?
After refresh, the idoc related configurations are lost and BI is unable to load from Source System R/3.
Thanks for reading and hope you can advise on the above.
Best regards
Pascal

Hello Pascal,
Maybe a thread in the PI forum would help you better:
Process Integration (PI) & SOA Middleware
Check the following thread:
Re: interface help
Regards,
Eduardo Rezende

CIN configuration in TAXINJ and TAXINN !!

Friends !!
Please help in configuring TAXINJ and TAXINN for VAT, Higher Edn.cess.If possible send me screen shots for the same and how to maintain taxcodes.
Thanks.
Yours sincerely,
sreedhar

Dear sreedhar kodali,
CIN Means Country India Version
In Indian Taxing procedure, Excise Duty plays a vital role in manufacturing cenarios. 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:
- JINFAC (Sales from manufacturing plants)
- JINEXP (Export sales)
- JINDEP (Sales from depots)
- 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.
- 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.
- For each excise registration in your business create a registration ID, and state:
- 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.
- The maximum number of items to be printed on each excise invoice
- 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.
- 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:
- Specify whether it is a manufacturing site or a depot.
- 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.
- Number of goods receipt per excise invoice.
- Multiple GR for one excise invoice, Single credit
- 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.
- GR Per Excise Invoice
- Multiple GR for one excise invoice , Multiple credit
- 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:
- Blocked stock
- Stock transport order
- 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.
- Define excise series groups based on type of outgoing document
- Assign series group to excise registration ID
- If no financial postings are required for an Excise invoice in this seris group then you tick the 'No utilization' indicator.
- 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.
- No account postings for CENVAT in sales cycle
- 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.
- If you use condition-based excise determination, use a copy of the tax procedure TAXINN.
- 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:
- Enter the tax procedure and the pricing conditions that are relevant for excise tax processing.
- Specify the purchasing and sales conditions types used for basic excise duty, additional excise duty, special excise duty, and cess.
- Specify the conditions in the sales order that are used for excise rates.
- 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 General, by choosing Taxes on Goods Movements Account -> Excise Duties Using Condition Technique and -> 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:
- 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).
- 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 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.
- 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.
- Material master data
Each material is assigned a chapter ID.
- 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.
Lets 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.
- Create a new tax code, and set the tax code type to V (input tax). Do not make any other settings for it.
- 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.
- For taxes on purchases, use the condition types contained in the tax procedure.
- 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.
- 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.
- VS1 (basic excise duty)
- VS2 (additional excise duty)
- VS3 (special excise duty)
- VS5 (sales tax setoff)
- MWS (central sales tax)
- MW3 (local sales tax)
- ESA (service tax)
- 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:
- Excise TT DC ind Account name
- GRPO CR CENVAT clearing account
- GRPO CR RG 23 BED account
- 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:
- Excise group
- Company code
- 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:
- Defined the G/L accounts
- Defined the excise groups
- 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.
- 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 Foreign Trade: Import Data. 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 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
Import, Excise related sub screen appears.
A small search on SDN SD forum will help you to answer your query.
I will suggest you to visit http://sap-img.com/sap-sd.htm. It will give you the overview of SAP SD module.
Moreover there is a separate section of FAQs with answers which will help you in great deal.
Hope this helps you.
Do award points if you found them useful.
Regards,
Rakesh
P.S. you can send me a mail at my mail id [email protected] for any specific details

Collaboration Room iViews give error -- Database related errors -- Pls Help

Hello Everyone,
We are on EP 6.0 SP 17 (Netweaver 2004).
KMC component was installed separately (Deployed manually).
We are trying to create simple Collaboration Rooms and we are facing some issues with the same.
I am following the documentation on SAP Help for the Room Creation:
Help  SAP Netweaver 2004  People Integration  Collaboration  Administration Guide
http://help.sap.com/saphelp_nw04/helpdata/en/1d/3d59fdaa5ebb45967ea107d3fa117a/frameset.htm
We are able to create rooms based on pre-defined templates and we are also able to add members to rooms, send/receive the invitation emails. I am able to work with Instant Messaging also.
But the problem is that some of the iViews related to Collaboration Rooms are giving errors.
1. Discussion iView gives an error saying You do not have access permission (even the user has all the necessary roles assigned).
Log for this error is as follows:
Exception ID = 90c3315f-c29d-2910-87ac-806aa372da7f com.sapportals.wdf.WdfError at com.sapportals.wdf.WdfCompositeController.buildComposition(WdfCompositeController.java:678)at com.sapportals.htmlb.AbstractCompositeComponent.preRender(AbstractCompositeComponent.java:33)
 at com.sapportals.htmlb.Container.preRender(Container.java:120)
 at com.sapportals.htmlb.Container.preRender(Container.java:120)
 at com.sapportals.htmlb.Container.preRender(Container.java:120) .
--- Nested WDF Exception -
com.sapportals.wcm.WcmException: The SQL statement "INSERT INTO "KMC_URIMAPPER" ("HASH_KEY","EXTERNAL_KEY","CONST_INTERNAL","VAR_INTERNAL","EK_PREFIX","EKHK00","EKHK01","EKHK02","EKHK03","EKHK04","EKHK05","EKHK06","EKHK07","EKHK08","EKHK09","EKHK10","EKHK11","EKHK12","EKHK13","EKHK14") VALUES (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)" contains the semantics error[s]: column "EK_PREFIX" not in any scope
I tried to change the permissions of the Discussion iView, but it did not work either.
2. Some iViews like Room Information throw a Runtime Error as follows:
Portal Runtime Error
An exception occurred while processing a request for :
iView : pcd:portal_content/com.sap.ip.collaboration/RoomPartContent/Generic/Pages/com.sap.netweaver.coll.RoomDiscussionPage/com.sap.netweaver.coll.RoomInformationExtended
Component Name : com.sap.netweaver.coll.appl.ui.room.RoomInformation
The exception was logged. Inform your system administrator..
Exception id: 02:17_02/02/07_0006_213711350
See the details for the exception ID in the log file
I have figured out that the following error message is common in most or the error messages:
The SQL statement "INSERT INTO "KMC_URIMAPPER" ("HASH_KEY","EXTERNAL_KEY","CONST_INTERNAL","VAR_INTERNAL","EK_PREFIX","EKHK00","EKHK01","EKHK02","EKHK03","EKHK04","EKHK05","EKHK06","EKHK07","EKHK08","EKHK09","EKHK10","EKHK11","EKHK12","EKHK13","EKHK14") VALUES (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)" contains the semantics error[s]: column "EK_PREFIX" not in any scope
Are there any database related configurations required for making the Collaboration Room Discussion functionality work properly?
Are there any KM related configurations necessary other than those mentioned in the document I am referring to?
Are there any database related configurations that are required?
I would really appreciate any help in this matter. Please advise me about any ideas you may have?
Thanks,
Raj Seelam

Hello Lars,
First of all thank you for your reply.
do u use Collaboration first time?
Yes, we just started using Collaboration and this is our first requirement.
Which roles do u have?
I have all the required roles (Super Admin, Content Management, Collaboration, Collaboration Room Creation).
I know that these features are available in NW04 SP 17 without any limitations. I have reviewed SAP Notes 707730, 711093, 709354 and 946470 also.
This problem is with only a few Collaboration iViews.
I am able to create Rooms, Enter Rooms, Receive Invitation e-mails without any problem.
Any suggestions about any possible missing configurations ?
Thanks Again,
Raj

Excise tab in not appearing in GR (new plant configured)

Hi Experts,
Excise tab is not appearing while GR posting.
I have configured a new plant in Sandbox server for testing purpose. Have done all required settings as under:
- New Plant configured
- Complete Excise related configuration done in Logistics General-> Tax on Goods Movement
- PR and PO created successfully. PO showing correct excise duty, cess, hcess, CST component etc.
- Material and vendor excise details maintained properly in J1ID
I guess I have missed excise related config somewhere in SPRO
please help !

Hi,
#Did you have Separate Excise Registration Number for new plant! check & define in following path:
SPRO ->> Logistics general ->> tax on Goods Movements->>India ->>Basic setting ->> Maintain Excise Registrations
##For new plant, Excise Reg. number need to be assigned to new Plant , check Excise Reg. number assigned to new plant
SPRO ->> Logistics general ->> tax on Goods Movements->>India ->>Basic setting ->> Maintain Plant Settings)
###Check Excise Group created & assigned to new plant in following path:
SPRO ->> Logistics general ->> tax on Goods Movements->>India ->>Basic setting ->> Maintain Excise Groups)
For above setting also select check box of EI Capture and select check box of Post EI in MIGO
Regards,
Biju K

CIN Configuration Doccument needed

Hello friends
Can anybody give me the Complete CIN configuration Doccuments (including Screen Shots) for FI step by step for TDS , Excise , CST , VAT ,Export / Import Procedures,etc.I dont know from where to start and how to start.
Pls help me out in my configuration.
Regards
Anup
Points are assured

Hi Anup,
We cant send screen shots for now,but i am sending detailed list of configuration CIN.i think this is very usefull to you
Re: CIN Configuration
Posted: Sep 21, 2007 6:25 AM in response to: vudumula sriniv... E-mail this post
Hi
Refer below link and also search in sdn you have no ogf posts on this issue
http://help.sap.com/saphelp_470/helpdata/en/95/00bb3cfbe1624be10000000a114084/frameset.htm
SAP SD CIN Configuration
What is CIN?
CIN Means Country India Version
In Indian Taxing procedure, Excise Duty plays a vital role in manufacturing cenarios. 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:
- JINFAC (Sales from manufacturing plants)
- JINEXP (Export sales)
- JINDEP (Sales from depots)
- 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.
- 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.
- For each excise registration in your business create a registration ID, and state:
- 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.
- The maximum number of items to be printed on each excise invoice
- 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.
- 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:
- Specify whether it is a manufacturing site or a depot.
- 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.
- Number of goods receipt per excise invoice.
- Multiple GR for one excise invoice, Single credit
- 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.
- GR Per Excise Invoice
- Multiple GR for one excise invoice , Multiple credit
- 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:
- Blocked stock
- Stock transport order
- 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.
- Define excise series groups based on type of outgoing document
- Assign series group to excise registration ID
- If no financial postings are required for an Excise invoice in this seris group then you tick the 'No utilization' indicator.
- 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.
- No account postings for CENVAT in sales cycle
- 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.
- If you use condition-based excise determination, use a copy of the tax procedure TAXINN.
- 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:
- Enter the tax procedure and the pricing conditions that are relevant for excise tax processing.
- Specify the purchasing and sales conditions types used for basic excise duty, additional excise duty, special excise duty, and cess.
- Specify the conditions in the sales order that are used for excise rates.
- 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 General, by choosing Taxes on Goods Movements Account -> Excise Duties Using Condition Technique and -> 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:
- 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).
- 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 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.
- 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.
- Material master data
Each material is assigned a chapter ID.
- 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.
Lets 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.
- Create a new tax code, and set the tax code type to V (input tax). Do not make any other settings for it.
- 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.
- For taxes on purchases, use the condition types contained in the tax procedure.
- 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.
- 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.
- VS1 (basic excise duty)
- VS2 (additional excise duty)
- VS3 (special excise duty)
- VS5 (sales tax setoff)
- MWS (central sales tax)
- MW3 (local sales tax)
- ESA (service tax)
- 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:
- Excise TT DC ind Account name
- GRPO CR CENVAT clearing account
- GRPO CR RG 23 BED account
- 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:
- Excise group
- Company code
- 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:
- Defined the G/L accounts
- Defined the excise groups
- 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.
- 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 Foreign Trade: Import Data. 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 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
Import, Excise related sub screen appears.
Hope this helps to you
Prem

Functionality & configuration of dunning

I need to understand the functionality of dunning and its related configuration steps.
T

hi
let me put it in simple terms:
1) You have a Customer which you had felt, he is doing good business and supplied material on Credit of 45 days.
2) Since this customer is good as you felt, you have not managed Credit Checks as well. So, he had comfortably reached to the fullest credit (or even more) which you can afford for any customer.
3) One fine day you got realised that, there is very bad debt with this customer and need to recover from him and till then, there will be no further supply to the customer.
4) Your company's legal department has laid a policy that, inorder to recover any bad debts, like:
a) We will send a normal payment reminder.
b) In case customer doesnt respond, we will send at least further reminder (dunning notice) may be 9 times
(9 reminders) (Dunning level) and what intervels of time (dunning frequency)
c) Still if the customer doesnt resopond for the reminders, you will file a law suit against the customer for recovering
the Payments.
d) Finally, after getting veridict, you may proceed for auction of his property or as per the order for Law.
Now in SAP, the definition of Dunning procedure is a pre-defined procedure specifying how customers or vendors are dunned.
For each procedure, the user defines
- Number of dunning levels
- Dunning frequency
- Amount limits
- Texts for the dunning notices
In SAP, you will maintain the Dunning Procedure at customer master. Referring to this your SD Team / FI Team (user team) will effect Dunning
hope you find it useful
regards
baalakrushnan.da

Configuration details about FUND- FUND CENTER- Annual Budget

Hi All
1. Link between fund and fundcenter configuration are available in FMDRIVE other than any other transaction code to find out the fund and fundcenter related configuration.
2. Please clarify when ever user trying to post the document posting related documents are automatically update in annual budget table(BPIJ) in SAP for this scenario what is the link between fund->fundcentet->annual Budget
Thanks
KRISHGUNA

Hi,
Fund centres and funds are not correlated. So, indeed, they could be derived one from another only in derivation strategy (FMDERIVE). Every financial/logistic document posted, relevant for FM update, will update your budget.
Regards,
Eli

Payslip related Configurations..

Similar Messages

Maybe you are looking for