FICA Rebate calculation and posting

Dear All,
When a bill is raised, the respective rebate amount is calculated and respective discount percentage(SKTPZ) field is updated.
So, when a payment is taken against the consumer the respective rebate is calculated and accordingly the amount is taken considering the amount without rebate amount before the due date.
But, we have configuration of FIFO method and clearing will be done based on due date. But if a consumer pay the partially before the due date, he is ant able to get the rebate(which he should defintely get).
I am just wondering if there will be anywhere the calcualtion is made which we can check at the time of amount posting.
Thanks,
Jay

Hi Jay,
Check event 0020 which enables additional action to be initiated where a document is posted in Contract Accounts Receivable, and open items are cleared at the same time (either fully or in part)
Thanks,
Amlan

Similar Messages

Calculation and posting of discount on Payment and on net amount

Hello,
My client would like to configure posting of discount on payment. The discount should be calculated on the net amount and should also adjust the VAT input tax amount. Example:
PO: 100 EUR, VAT 10 EUR, Gross amt = 110 EUR, Invoice recieved: 110 (-110 on vendor,100 is posted on GR/IR and 10 on input tax). When payment is done, discount amounts to 2.2 EUR ( 110 is posted on vendor account, -107.8 on bank account, -2 on discount account, -0.2 in input tax).
Have anyone of you ever did this on SAP. Can you pleas explain me the steps if yes? Thank you for your help.

Hi,
I have already did a test with base discount on net amount and base vat on net amount check. When those are check, during good receipt the purchase account is debit with the net amount (gross -discount) and during invoice the difference is then transferred to the purchase account. The tax is calculated on the net amount. This is not what we are looking for. For us we want to know if it is possible that during good receipt and invoice received everything is calculated without taking into consideration the discount received. It is only when we are doing the payment of the invoice that discount is calculated and the VAT amount is adjusted for with the discount received. Thank you for your help.

Depreciation not calculated and posted

Dear All
I have a problem. Actually we had a legacy data transfer last year in the month of March.
All the assets were posted to new company code fronm the old company code by using an initial clearing account.
the entries were done through f-02.
My problem lies in the fact that 4 assets which were posted at that time are not functioning well.
The balances got transfered as opening balances in Aw01n but there is no planned depreciation for them for the year 09-10.The amounts are coming as " zero" in the planned depreciation tab.
As a result of which my asset acquisition reports are not coming correct.
I have figured out the diiferences..
The differences are regarding these 4 assets only.
Could any of you please help me in finding the reason why the depreciation is not calculated on these assets since April 2009 and how they are appearing "ZERO" in the acquistion report when there is a actual balance in the asset
Thanking you
regards
Ruby

Hi
I have checked the asset in the previous company code also.. All the parameters are same..plus in that company code the sysytem has shown the planneed depreciation too for all the assets.
now I think the problem lies in the depreciation key or in some linking between depreciation key and the asset..
have you any clue about the areas that needs to be checked for this sort of linkage?
Plus there is no over charging of depreciation.... The system didnot calculate anything in the present company code.........
Regards
Ruby jamwal

EXCISE CAPTURE AND POSTING

Dear all,
what are the steps are involved to activate excise capture and posting at T Code : MIGO.
Rgs
mrs

Hi,
Before going to capture excise invoice ,you need to configure all the cin configurations .
here is the cin configuration..
Check Calculation Procedure
In this activity, you can check and, if necessary, change existing procedures for tax calculation.
Standard settings
Calculation procedures containing the necessary specifications for the calculation and posting of taxes on sales/purchases have already been defined in the standard SAP system for certain countries. Every calculation procedure groups several tax types together into a condition type (for example, output tax or input tax) in the calculation procedure, and determines calculation rules for it.
The calculation procedure determines for which amount the individual condition types are to be calculated. This can be the base amount (total of the expense items and the revenue items) or a subtotal. The entry in column FrmLvl, determines for which amount tax is calculated.
Note
In this activity, the condition types for the check and the possible change provided in the standard system are also displayed. Here, for example, the condition calculation rule, or for which base amount the tax is calculated is determined (= condition type).
Recommendation
If possible, do not change the condition types and calculation procedures provided in the standard system. Only check the standard condition types and calculation procedures regarding whether you can use them for your requirements. If necessary, make changes.
Activities
If you cannot use the standard settings, change the condition types and calculation procedures delivered to meet your requirements.
Procedure (pricing, output control, acct. det., costing,...)
Specifies the conditions that are allowed for a document and defines the sequence in which they are used.
Example
Procedures are used, for example, in the following applications:
· Pricing in sales and distribution
· Applying overhead in Product Costing (costing sheets) and for CO internal orders
· Calculating accrued costs in Profitability Analysis
· Output control (printed confirmations, EDI messages, electronic mail)
· Account determination
· Calculating taxes on sales/purchases
· Calculating accruals in Cost Center Accounting
· Pricing for resource planning
Definition: condition type
Controlling (CO)
A distinction, in overhead calculation, is made between:
· Base condition types, which determine the object for which the overhead is to be calculated
· Overhead condition types, which define the percentage overhead to be applied
In resource planning, a condition type determines the types of resource prices that are stored in the SAP System. These can be absolute or percentage values, for example.
Real Estate Management (RE)
An exact definition of a condition that specifies the amount paid for a specific service.
Condition types include:
· Basic rent
· Advance payment for operating costs
· Pest control
Sales and Distribution (SD)
A characteristic of a condition.
For example, in pricing, different condition types are used to distinguish between a discount that refers to a net price and a discount that refers to a gross price.
Treasury (TR)
A characteristic of a condition used to classify financial transactions.
Typical examples of condition types are interest, dividends, or full repayment upon maturity. The various parameters specified for the individual condition types determine how the flows are calculated in the cash flow.
Return ->
Definition: condition_type
Condition type
The condition type is used for different functions. In pricing, for example, the condition type lets you differentiate between different kinds of discount; in output determination, between different output types such as order confirmation or delivery note; in batch determination, between different strategy types.
Access sequence
With the access sequence you define
· the condition tables used to access the condition records
· the sequence of the condition tables
· which field contents are the criteria for reading the tables
Assign Country to Calculation Procedure
In this activity, you enter the key for the calculation procedure which determines the conditions which are allowed per document and which defines the sequence of the conditions in the document for each country.
Requirements
Each calculation procedure which you enter must contain the necessary specifications for calculating and posting the taxes on sales/purchases. For more information on this, read the chapter "Create calculation procedure".
Activities
1. Assign a procedure for tax calculation to every country with which your company has business dealings.
2. Make sure that the corresponding data for calculating taxes is stored for each calculation procedure which you enter here.
Check and Change Settings for Tax Processing
In this activity you make the necessary specifications for posting taxes. In doing this you specify under a process key the following indicators:
· Tax type
Output tax, input tax, additional taxes, or "not tax-relevant" can be specified as the tax type.
· Nondeductibility of tax amounts
For this, tax amounts are marked as not deductible.
· Posting indicator
Here you specify whether the tax amount is posted separately or distributed to expense or revenue items.
· Tax not relevant to cash discount (Not discount relevant)
This indicator is set only for Canada. If you select it, the system does not take into account the corresponding tax amount when determining the tax base.
Standard settings
Process keys with the most important characteristics for tax amounts have already been set in the standard SAP system.
Recommendation
Do not change the standard settings. Check whether you can use these process keys for your company, making changes only if necessary.
Activities
If you cannot use the standard settings, use new process keys and enter them in your calculation procedure. Do not change the standard SAP process keys.
Note
You must make enhancements to the standard settings if you want to specify a new account key in the "Create calculation procedure" activity. You must create and maintain this key beforehand in the "Settings for tax processing" activity.
Internal processing key
The internal processing keys are used by the system to determine accounts or posting keys for line items which are created automatically.
The processing keys are defined in the system and cannot be changed by the user.
Definition: posting key
Financial Accounting (FI)
A two-digit numerical key that determines the way line items are posted.
This key determines several factors including the:
· Account type
· Type of posting (debit or credit)
· Layout of entry screens
Return ->
Definition: posting_key
Maintain Excise Registrations
Use
In this IMG activity, you maintain the data relating to your excise registrations.
Activities
Enter each of your excise registrations, specifying a four-character code for each.
Definition: excise registration
Financial Accounting (FI)
An entity in India that is entitled by law to produce any goods liable to excise.
Each entity is assigned its own excise registration number.
Every factory that manufactures excisable goods is required to register separately, so that a business with seven factories requires seven registrations.
Return ->
Definition: excise registration
Maintain Company Code Settings
Use
In this IMG activity, you maintain the data relating to your company codes.
Maintain Plant Settings
Use
In this IMG activity, you maintain excise information relating to your plants.
Maintain Excise Groups
Use
In this IMG activity, you define your excise groups. For each excise group, you can also control how various excise invoice transactions will work.
Definition: excise group
Financial Accounting (FI)
A unit within an excise registration, in India, which keeps its own set of excise records.
Whereas the excise registration reports to the excise authorities, the excise group is a purely internal organizational unit. Each excise group keeps records of all transactions that have to be reported to the excise authorities. When the time comes to present these records to the authorities, the excise registration compiles the information from all of its excise groups.
Return ->
Definition: excise group
Maintain Series Groups
Use
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.
Activities
· 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' indicator.
Example
You could define two series groups, group 001 for excise invoices, and group 002 for 57 F4 documents.
Maintain Excise Duty Indicators
Use
In this IMG activity, you maintain the excise duty indicators.
Maintain Postal Addresses
Use
In this IMG activity, you maintain the addresses of various customs and excise organizations that your company deals with.
You use these addresses in the ARE Documents functions. When you create an ARE-1 or ARE-3, you enter the address of the excise department and the customs department involved in the export process. The system then prints their names and addresses on the AREs.
You can then define a default local excise department for each excise group and a default customs department for each series group.
Definition: ARE-1 document
Logistics - General (LO)
A form, in India, that companies have to fill out when they remove excisable goods from their manufacturing plants for export.
The form exempts them from paying excise duty when they remove the goods from their premises.
Return ->
Definition: ARE-1 document
Definition: ARE-3 document
Logistics - General (LO)
A form, in India, that allows companies to sell otherwise excisable goods from their premises without paying basic excise duty. The buyer of the goods must be in possession of a deemed export license.
The ARE-3 states what goods are being removed and which deemed excise license covers it.
Return ->
Definition: ARE-3 document
Maintain Subtransaction Type with Text
Sub Transaction Type
Sub transaction type is used for multiple purposes
Subcontracting:
It determines the subcontracting attributes and determines the accounts for the posting while doing a sub contracting transaction.
Excise removals
Sub transaction type is also used for determining the accounts while doing excise removals.
With in CIN the account determination is based on the transaction type. So normally you can have a single set of accounts for Excise utilization. In case you need alternate account determination for handling various scenarios you can define sub transaction types. The sub transaction types and corresponding account assignments needs to be maintained in CIN customization
Select Tax Calculation Procedure
Use
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.
Definition: condition-based excise determination
Logistics - General (LO
A method that the system uses of determining excise duty in India.
This method requires you to create condition records for each combination of vendor or customer and material (and possibly other conditions).
When you create a purchasing document, the system calls the tax procedure assigned to India. The tax procedure finds all of the condition records that you have created for that combination of vendor and material.
When you create a sales document, the excise duties and sales taxes are determined by the pricing procedure (not the tax procedure).
Return ->
Definition: condition-based excise determination
Definition: formula-based excise determination
Logistics - General (LO)
A method that the system uses of determining excise duty in India.
This method was used in the Country Version India Add-On and requires you to maintain additional data in the Excise Rate Maintenance transaction, J1ID.
When you create a purchasing document, the system calls the tax procedure assigned to India. Each of the excise duties in the tax procedure has its own condition types, and each condition type is assigned to a formula. This formula instructs the system to calculate the excise duty using the data that you have maintained in the Excise Rate Maintenance transaction.
When you create a sales document, the system determines the excise duties and sales taxes using the pricing procedure (not the tax procedure).
Return ->
Definition: formula-based excise determination
Maintain Excise Defaults
Use
In this IMG activity, you define which tax procedure and pricing condition types are used in calculating excise taxes using formula-based excise determination.
Activities
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.
Definition: basic excise duty
Financial Accounting (FI)
The main type of excise duty in India.
It is levied on a wide range of products, for example, foodstuffs, metals, jewellery, leather goods, and machinery.
Return ->
Definition: basic excise duty
Definition: additional excise duty
Financial Accounting (FI)
A form of excise duty, in India, levied on a select range of products, for the most part, textiles.
Return ->
Definition: additional excise duty
Definition: special excise duty
Financial Accounting (FI)
A form of excise duty in India on a limited number of goods, mostly luxury goods, including pan masala, sparkling waters, furs, and yachts.
Return ->
Definition: special excise duty
Definition: cess
Financial Accounting (FI)
In India, a tax on the manufacture of certain products, mostly foodstuffs.
Return ->
Definition: cess
Definition: countervailing duty
Financial Accounting (FI)
A form of excise duty imposed on imports that are subsidized by the country in which they were manufactured.
Countervailing duty (also known as CVD) is intended to make the imports more expensive, thereby redressing any competitive advantage they might have over goods produced locally.
Return ->
Definition: countervailing duty
Define Tax Code for Purchasing Documents
Use
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.
Activities
Create a new tax code, and set the tax code type to V (input tax). Do not make any other settings for it.
See also
SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> Condition-Based Excise Deter
Sales Tax Code
The tax code represents a tax category which must be taken into consideration when making a tax return to the tax authorities.
Tax codes are unique per country. The tax rate calculation rules and further features are stored in a table for each tax code.
Procedure
For tax-exempt or non-taxable transactions, you should use tax codes with a 0 percentage rate if the corresponding transactions are to be displayed in the tax returns.
Note
You must define new tax codes if tax rates are changed by the state. The old codes with the old tax rates must remain in the system until no more open items which use this tax code exist.
Definition: tax code
Financial Accounting (FI)
A two-digit code that represents the specifications used for calculating and displaying tax.
Examples of the specifications defined under the tax code are:
· Tax rate
· Type of tax (input tax or output tax)
· Calculation method (percentage included or percentage separate)
Return ->
Definition: tax_code
Definition: tax rate
Financial Accounting (FI)
The percentage rate used to calculate the tax amount.
Return ->
Definition: tax_rate
Assign Tax Code to Company Codes
Use
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.
See also
SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> Condition-Based Excise Determination
Classify Condition Types
Use
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.
Standard settings
The standard system comes with sample settings for the tax calculation procedures and pricing procedures.
Use these settings as a basis for your own.
Maintain Chapter IDs
Use
In this IMG activity, you maintain the chapter IDs and the corresponding descriptions as per the schedules published by the Central Board of Excise and Customs.
Definition: chapter ID
Logistics - General (LO)
The number given to a material in the schedules of materials published by the government of India.
The schedule lists all materials involved in manufacturing, input materials and output materials alike. It shows how much excise duty is levied on each material.
Each material in the schedule is assigned its own identification code, called "chapter ID."
Example
The schedule contains an entry for ceramic roofing tiles, which are liable to basic excise duty at 16%. The chapter ID associated with these tiles is 6903.10.
Return ->
Definition: chapter ID
Assign Users to Material Master Screen Sequence for Excise D
Use
In this IMG activity, you customize the material master data so that it shows the information relating to excise duty.
Standard settings
Country Version India comes with a screen sequence (IN) that shows the excise duty fields. You have to assign it to each of your users.
Activities
1. Double-click User Screen Reference.
2. Assign all users who need to see the excise duty information to the screen reference IN.
Example
Name Screen Reference
MISHRA IN
Screen Sequence Number
Alphanumeric key identifying the screen sequence. The screen sequence defines the sequence of information units in the material master dialog. A screen sequence is made up of data screens. For information on the screen sequences defined in the standard R/3 system, see the IMG documentation Configuring the Material Master.
Note
When creating a screen sequence, use an alphanumeric key beginning with the letter Y or Z (customer name range). This key cannot subsequently be changed.
Dependencies
You can assign screen sequences to users in the IMG activity Assign Screen Sequences to Users/Material Types/Transactions/Industry Sectors.
Screen reference depending on the user
Grouping of users that determines what screens are displayed in accordance with the user master record when you maintain material master records. It also determines the order in which the screens appear.
Definition: user master record
User and Authorization Management (BC-SEC-USR)
Record that contains important master data for a user in the SAP System.
The user master record contains the assignment of one or more roles to the user. This is how a user menu and the corresponding authorizations for the activities contained in the user menu are assigned to the user. Only users who have a user master record can log on to the system.
Return ->
Definition: user_master_record
Define Form Types
Use
In this IMG activity, you define which form types you want to record in the system. You can only use form tracking for the form types that you enter here.
Example
· Form type: CT3
· Form description: Concessional tax form
· Status: Receive
Define G/L Accounts for Taxes
Use
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.
Activities
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
Use
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 subtransaction types, enter the accounts for each subtransaction type as well.
Activities
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 hold account
Specify G/L Accounts per Excise Transaction
Use
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 alltransactions.
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.
Define Processing Modes Per Transaction
Use
In this IMG activity, you specify which processing modes the user can use in the various Incoming Excise Invoice transactions.
This way, you can tailor the transaction to what your users have to do.
Standard settings
The system comes with three standard transactions relating to the Incoming Excise Invoices function (those that are included in the role SAP_CIN). The processing modes available in these transactions are as follows:
· J1IEX_C
This transaction is for excise clerks: users of this transaction can only capture and display excise invoices.
· J1IEX_P
This transaction is for excise supervisors: they can change, display, cancel, and post excise invoices.
· J1IEX
In this transaction, users can capture and post excise invoices, as well as displaying, changing, and canceling them.
Activities
If the standard settings meet your requirements, do not do anything.
Otherwise, you can adjust the standard settings or you can create your own transactions. To do so:
1. In Maintain Transaction, create a new transaction by making a copy of one of the standard transactions. Give the new transaction a transaction code of your choice.
2. In this activity, enter data as follows:
o Tcode: The transaction code that you have just created.
o Proc. mode: Specify what the users of the transaction will do with the excise invoices.
o Active: Select this indicator to activate the setting.
Example
You might want to create a transaction that only allows users to display excise invoices.
Define Reference Documents Per Transaction
Use
In this IMG activity, you specify for each combination of transaction and processing mode which reference documents you want the users to be able to use.
Activities
If the standard settings meet your requirements, you do not have to do anything.
Otherwise, add the entries that you need to the table: For each transaction, make one entry per combination of processing mode and reference document. Activate each entry for it to work.
Definition: excise invoice reference document
Logistics - General (LO)
A document, in India, that you refer to when you enter an incoming excise invoice.
If you have already posted the goods receipt, you can use the goods receipt document as the reference document. Otherwise, you can use the purchase order (or another purchasing document, such as a be a contract or a scheduling agreement).
Example
In the SAP System, you create a purchase order for 100 bags of sand and send the order to your vendor. Two weeks later, the vendor delivers the sand, accompanied by an excise invoice.
When you enter the excise invoice in the system, you specify the number of the original purchase order: this is the reference document.
Return ->
Definition: excise invoice reference document
Maintain Rejection Codes
Use
In this IMG activity, you define the rejection codes that are used in the Incoming Excise Invoices transaction.
Activities
For each rejection code, enter a code and a description. You can also specify whether the excise duty in the invoice is to be posted to the CENVAT on hold account, instead of the CENVAT clearing account.
Specify Which Movement Types Involve Excise InvoicesUse
In this IMG activity, you specify which movement types relating to goods receipts involve excise invoices.
The system uses this information during the goods receipt procedure. When you post a goods receipt using one of the moevement types that you have specified here, the system prompts you to enter the excise invoice number.
Note
This option cannot be used for processing goods receipts without purchase orders.
Maintain Default Excise Groups and Series Groups
Use
In this IMG activity, you specify which excise group and series group you want to appear in these fields by default. You can make separate settings for different combinations of sales organization, distribution channel, division, and shipping point.
Activities
This activity is optional, unless you want the system to automatically create outgoing excise invoices when you create a customer invoice.
In this case, you must also make the appropriate setting in Customizing for Excise Duty, by choosing Basic Subcontracting Attributes
Use
The subcontracting attributes help determine conditions for a combination of an excise group, a transaction type, and a subtransaction type.
The conditions such as the number of excise items per subcontracting challan, if the nonexciseable materials have to be filtered or not when the subcontracting challan is created, the movement type groups for issues and receipts and the hierarchy of determining the excise base value are mentioned here.
Requirements
Before you continue with this activity, work through the following activities:
· Materials Management -> Inventory Management and Physical Inventory -> Goods Issue / Transfer Postings -> Define Screen Layout.
For the movement type 541, maintain the field Purchase Order as an optional entry or as a required entry.
· Materials Management -> Inventory Management and Physical Inventory -> Output Determination ->Maintain OutputTypes.
Maintain the output type. On the Default Values tab, maintain the dispatch time and the transmission medium. Maintain the print parameter on the Print tab. This output type has to be maintained in this activity here.
· Materials Management -> Inventory Management and Physical Inventory -> Output Determination ->Assign Forms andPrograms.
Maintain the Program, FORM routine, and the form for the output type.
· Materials Management -> Inventory Management and Physical Inventory -> Output Determination ->Printer Determination -> Printer Determination by Plant / Storage Location.
Enter the output device that you use.
Settings -> Maintain Excise Groups, and selecting Create EI (Create Excise Invoice Automatically).
Maintain Movement Type Groups
Use
In this IMG activity, you group movement types together to form movement type groups.
Definition: movement type
Inventory Management (MM-IM)
A classification key indicating the type of material movement (for example, goods receipt, goods issue, physical stock transfer).
The movement type enables the system to find predefined posting rules determining how the accounts of the financial accounting system (stock and consumption accounts) are to be posted and how the stock fields in the material master record are to be updated.
Return ->
Definition: movement type
Utilization Determination
Use
In this IMG activity, you specify which CENVAT accounts are to be debited by the Fortnight Utilization of CENVAT report: When the report calculates how much excise duty you must remit, it automatically proposes which CENVAT accounts the duty should be debited to. Here, you specify those defaults.
You can either:
· Debit all the excise duty to one account
· Debit the excise duty to more than one account, in which case you specify which percentage is to be debited to each account
Example
If you want 50% of basic excise duty (BED) to be debited to the RG 23A account and the remaining 50% to the RG 23C account, you would make the following settings:
Acct name BED perc.
RG 23A BED account 50
RG 23C BED account 50
Alternatively, to debit all of the BED to the RG 23A account, and then RG 23C account, if there is not enough in the RG 23A account, you would make the following settings:
Acct name BED perc. +
RG 23A BED account X
RG 23C BED account X
When you come to run the report, the system takes the RG 23A account because it is the first one you have entered. If this account does not cover the BED, the system takes the RG 23C account instead.
Maintain Minimum Balances for Excise Accounts
Use
In this IMG activity, you can maintain minimum balances in your excise accounts. When the balance in these accounts during utilization falls below this level, the system automatically utilizes funds in the PLA account.
Activities
Maintain the minimum balance amount for the excise accounts. If you have more than one excise group, you can maintain different minimum balances.
Specify SAPscript Forms
Use
In this IMG activity, for each of your company codes, you specify which SAPscript forms the system prints the excise registers with.
Standard settings
Country Version India includes a number of sample SAPscript forms and printing programs, which you can use as follows:
Reg. name Lay. no. Form Tcode/Prog
RG 23A Part I 1 J_2IRG23A_PART1 J_2IRAP1
RG 23C Part I 1 J_2IRG23C_PART1 J_2IRCP1
RG 23A Part II 1 J_2IRG23A_PART2 J_2IRAP2
RG 23C Part II 1 J_2IRG23C_PART2 J_2IRCP2
PLA 1 J_2I_PLA J_2IPLA
RG 23 D 1 J_2I_RG23D J_2IRG23
RG 1 1 J_2I_RG1 J_2IRRG1
RT 12 1 J_2I_RT12_ABSTRA J_2IRT12
RT 12 1 J_2I_RT12_ABSTRA J_2IRT12
RT 12 1 J_2I_RT12_3 J_2IRT12
The layout description can be left blank or an appropriate description maybe filled in. You may not change the register name. You can have your own layouts and maintain the name here. If the output device and number of copies are maintained it is automatically picked up for printing.
Number Ranges
You can maintain the number ranges for all CIN Number range objects using this transaction
Activities
Please maintain the number ranges for the folllowing objects The no nr has to be '01' for all
1. j_1iintnum
At an Excise group
1. j_1irg23a1
2. j_1irg23a2
3. j_1iRG1
4. j_1irg23c1
5. j_1irg23c2
6. j_1ipla2
7. j_1iintpr2
8. j_1irg23d
9. j_1irg1_t ( material level)
10. j_1iconpla ( if Consolidated PLA is used )
At Series group
1. j_1iexcloc
2. j_1iexcexp
3. j_1idepinv
4. j_1i57Fc ( 57F Challans
After configuring cinraise the po aganst the material which is lliable to excise.
in migo enter the po number...select the ok indicator and click check button
now can observe excise tab in the header
enter excise invoice no and date.
now post the goods reciept.
according to configuration settings in excise tab it gives whether excise inoice is saving when you posting migo .if invoice is only saving
go to j1iex_p tc and post the excise invoice.
hope your dubt is clearded.
regards
venkat

Rebate rate and accrual rate

What is the difference between rebate rate and accrual rate in rebate agreements. One example wil be very helpful

Accrual Rate:
You can enter an accrual rate manually in each condition record. The accrual rate should reflect, as accurately as possible, the rate at which the rebate will be calculated at final settlement.
Every time you process a rebate-relevant billing document (an invoice, a credit or debit memo), the system automatically posts an accrual to financial accounting (FI). Within FI, the rebate accrual is posted to two accounts: a sales deduction account and an accrual account. The accrual account is cleared when the rebate agreement is settled with a credit memo.
Rebate Rate:
A price discount that a vendor grants a customer at a later time.
The amount of rebate depends on the invoiced sales that the customer achieves in a specified period and is defined using condition records.
Regards
AK

How do I create a 1d array that takes a single calculation and insert the result into the first row and then the next calculation the next time the loop passes that point and puts the results in thsecond row and so on until the loop is exited.

The attached file is work inprogress, with some dummy data sp that I can test it out without having to connect to equipment.
The second tab is the one that I am having the problem with. the output array from the replace element appears to be starting at the index position of 1 rather than 0 but that is ok it is still show that the new data is placed in incrementing element locations. However the main array that I am trying to build that is suppose to take each new calculation and place it in the next index(row) does not ap
pear to be working or at least I am not getting any indication on the inidcator.
Basically what I am attempting to do is is gather some pulses from adevice for a minute, place the results for a calculation, so that it displays then do the same again the next minute, but put these result in the next row and so on until the specifiied time has expired and the loop exits. I need to have all results displayed and keep building the array(display until, the end of the test)Eventually I will have to include a min max section that displays the min and max values calculated, but that should be easy with the min max function.Actually I thought this should have been easy but, I gues I can not see the forest through the trees. Can any one help to slear this up for me.
Attachments:
regulation_tester_7_loops.vi ‏244 KB

I didn't really have time to dig in and understand your program in depth,
but I have a few tips for you that might things a bit easier:
- You use local variables excessively which really complicates things. Try
not to use them and it will make your life easier.
- If you flowchart the design (very similar to a dataflow diagram, keep in
mind!) you want to gather data, calculate a value from that data, store the
calculation in an array, and loop while the time is in a certain range. So
theres really not much need for a sequence as long as you get rid of the
local variables (sequences also complicate things)
- You loop again if timepassed+1 is still less than some constant. Rather
than messing with locals it seems so much easier to use a shiftregister (if
absolutely necessary) or in this case base it upon the number of iterations
of the loop. In this case it looks like "time passed" is the same thing as
the number of loop iterations, but I didn't check closely. There's an i
terminal in your whileloop to read for the number of iterations.
- After having simplified your design by eliminating unnecessary sequence
and local variables, you should be able to draw out the labview diagram.
Don't try to use the "insert into array" vis since theres no need. Each
iteration of your loop calculates a number which goes into the next position
of the array right? Pass your result outside the loop, and enable indexing
on the terminal so Labview automatically generates the array for you. If
your calculation is a function of previous data, then use a shift register
to keep previous values around.
I wish you luck. Post again if you have any questions. Without a more
detailed understanding of your task at hand it's kind of hard to post actual
code suggestions for you.
-joey
"nelsons" wrote in message
news:[email protected]...
> how do I create a 1d array that takes a single calculation and insert
> the result into the first row and then the next calculation the next
> time the loop passes that point and puts the results in thsecond row
> and so on until the loop is exited.
>
> The attached file is work inprogress, with some dummy data sp that I
> can test it out without having to connect to equipment.
> The second tab is the one that I am having the problem with. the
> output array from the replace element appears to be starting at the
> index position of 1 rather than 0 but that is ok it is still show that
> the new data is placed in incrementing element locations. However the
> main array that I am trying to build that is suppose to take each new
> calculation and place it in the next index(row) does not appear to be
> working or at least I am not getting any indication on the inidcator.
>
> Basically what I am attempting to do is is gather some pulses from
> adevice for a minute, place the results for a calculation, so that it
> displays then do the same again the next minute, but put these result
> in the next row and so on until the specifiied time has expired and
> the loop exits. I need to have all results displayed and keep building
> the array(display until, the end of the test)Eventually I will have to
> include a min max section that displays the min and max values
> calculated, but that should be easy with the min max function.Actually
> I thought this should have been easy but, I gues I can not see the
> forest through the trees. Can any one help to slear this up for me.

FA-retirement-Asset value date and posting date are not in same fisc year

Hello,
I would like to post retirement in the new fiscal year but with asset value date in the previous year so that NBV is calculated correctly. It is not possible neither in ABAON nor in ABAVN with any transaction type.
I always get message 'Asset value date and posting date are not in same fiscal year'.
Is there any way how to handle this?
Thank you,
Jan

Hi,
I have tried this but the settings of our Depr keys works in the way. That if you use asset value date in the new month it will calculate depreciation for the whole month.
This means if I retire with asset value date 31.12.2008 - NBV will be calculated as at 31.12.2008.
If I retire with asset value date 1.1.2008 - NBV will be calculated as at 31.1.2009.
Thank you anyway!

Rebate settlement and VAT

Hi Gurus,
I am implementing retrospective rebates in SD.
I have produced a rebate settlement document (in Poland (where I am working) that document is a corrective invoice request). With the billing document that I will produce from that request I need to post VAT in addition to the usual postings that SAP performs in rebate agreement settlements (that is: accruals reverse, client account profit correction and posting of rebate ammount).
That means that I need somehow to include MWST like price conditions in the settlement documents.
Unfortunatelly it seems that SAP does not allow including any new conditions in the pricing of those settlement documents. No new conditions can be added to the corrective invoice request.
Is there any way to add price conditions to a rebate settlement document ?
Or is it a SAP constraint that nothing else can be changed there in order to not to mess with the normal rebate settlement ?
I have a program that calculates the right VAT ammounts I have to post. If only I could include it somehow in the settlement doc. that would solve the problem...
Thank you in advance for any advice

Hello,
Can you tell which Rebate Type are you using and which Sales Document type this rebate type generates?
Thanks
Fátima

Rebate calculation from Basic Price PR00

Hi,
This query is related to rebate conditions. At present the rebate base is calculated from the subtotal, that is Basic price - discount(The subtotal 7 is assigend to the step 300).
As per the requirement from the business, the rebate should be calculated from the 'Basic Price'. They don't want the discount value should be considered in the rebate calculation. I explained them regarding the burden which company has to bear, but the business still want to go with the changes.
My plan is to create another step in the pricicng procedure right after the basic price and assign subtotal 7 to it and delete the exting reabte subtotal step, and assign the new step number to rebate conditions, so the reabte will be calculated based on this.
My questions are:-
1. Can I edit the existing pricing procedure to make these changes?
2) Will there be any impact on the existing rebate agreements (open) and its settlements on a later date?
3) Will there be any impact on the process of billing of open sales orders/deliveries (not billed) after the change in pricing procedure?
Please guide me.
Regards,
SAM

Hi Ivano,
Thnak you very much for your suggestion.
As the note says, the best way is to copy the existing pricing procedure and create another and assign it in OVKK.
Will there be any effect for partially billed delivery items? (at the time of creation of billing document for the unbilled items in the delivery)
OR
when we create a billing document from the delivery (in the case of sales order and delivery created with old pricing procedure and the billing document is getting created after the assignment of new pricing procedure)
Your valuable suggestions will be highly appreciated.
Regards,
SAM

Difference between "Rebate Recipient" and "Customer" in Rebate Setting

While setting "Rebate Agreement" (TCode VBO1), for "Customer Rebate" (0003) Agreement Type, there is one "Rebate Recipient" and then when we go on to create the conditions, there is "Customer" for different rate etc.
My question- What is difference between the "Rebate Recipient" & the "Customer" (the one we enter while entering the conditions)?
Is it like "Payer" & "Sold to Party" partner function in Sales Order Processing eg for different "Sold to Party" there could be one "Payer", similarly for Rebate, for these different "Sold to Party", which would be like "Customer" in Rebate setting and the "Payer" in Sales Order will be like "Rebate Recipient" in Rebate Setting.?
Thx

Dear SR
Rebate Recipient is the payer
As you know ,in rebate configuration , the payer's master record is to be activated which is first major setting in rebates
Customer is sold to party
As you know ,the rebate process starts from sales order (your sales order pricing procedure will have rebate condition types but they are reflected in billing) and in a sales document the pricing conditions is taken from sold to party and the pricing condition records are taken from sold to party
If in case payer and sold to party are different
That means the input is taken from sold to party that is Customer (rebate calculations in pricing procedure ) and the out put is passed on to the payer that is Rebate Recipient (passing on rebate claim as credit notes)
That is two different identities which the system needs to know
Hence SAP has defined so
Even if the payer and sold to paty are same even then we need to give the same no(customer no ) in both the places
Regards
Raja

SAP HR /PY Accrual and posting Period

Hello SAP Experts,
The posting date of our Payroll is always 'Plus 2'. For example, if the fortnightly pay period ends on 29/5/2011, the posting date and the EFT release date will be 31/5/2011 - this pay period should therefore be included in May accounting.
However, our software vendor is telling us that where the posting date (i.e. pay period end plus 2) falls on the end of month date, that the system cannot recognize this pay period in May accounting. Rather this period will now be included in June accounting, and therefore, the system will calculate and post accruals in the previous pay period of 15/5/2011 i.e. 10 day accrual.
Is there a way that SAP can be configured to allow period 29/5/2011 to be included in May accounting and for No accruals to be calculated in the previous pay period?
Rgds
Muthu

Hi Li,
We have alrweady Implemented the Month end Accruals trying to Enhance a new functionality with in the posting period but the standard config as below
Menu Path IMG -> Payroll Australia-> Reporting for Posting Payroll Results to Accounting -> Activities in the HR System -> Maintain Posting Date for Payroll Periods
Send ur email I can send u the spread sheet of how i did the Config for my Client
rgds
Muthu

Modify existing rebate condition and exclusion

Hi
We are rebate agreements for customers. Currently I want to modify rebate condition in one of rebate agreement.
Scenario: let us June 10th 2010 onwards, the rebate % is 3% for Profit center 'xxxx' & customer 'yyyy' instead of 1%. And 3% needs to accrued on billing docs going forward. How to set up this.
I tried to modify existing rebate condition using VBo2 as follows: went into rebate agreement using VBo2, changed rebate % for condition record with effective from 06/11/2010 and Saved. problem when I ran VBOF program, system posted reversal accrual for old rebate condition 1%. Old condition record validity from 01/01/2009 Valid to 12/31/2011.
I have one more question. We want to set up rebate condition for all materials exclude some of them. we have thousands of materials for which we need to calculate rebates. but we want to exclude some materials in the rebate agreement. How to set up such exclus
any ideas really appreciated
thnx

The key of your condition table (the one supporting your condition record in the agreement) is evidently Profit Center / Customer. So for any combination of profit center and customer, you can maintain a rate and validity period.
You are attempting to maintain two separate records having the same key. As you have experienced, the system does not allow it.
The simple solution is to expire that rebate agreement and start a new one with the updated validity period and conditions.
As for excluding certain materials, you need a more detailed key in your condition table. Something else from the material master seems appropriateu2014Commission Group for example. Maintain commissionable materials in group 01 and non-commissionable ones in group 02. Then a key combination of Commission Group / Profit Center / Customer would work well for you.
Regards,
Ken

Minority Interest calculation and consolidation

Hi people. i am new to HFM. I am kind of stuck with Minority Interest calculation and the consolidation of it. Now after looking at different posts on the minority interest calculation here , i am still confused if we could use the calculation expression for Minority Interest calculation within Sub Consolidate() or should we include it in Sub Calculate(). Please find below the script that i am working on.
SCRIPT :
Sub Consolidate()
Method=HS.Node.Method("")
PCon=HS.Node.PCon("")
POwn=HS.Node.POwn("")
vMIN=1-HS.Node.POwn("")
PMin=PCon-POwn
Dim strAccount,i
Set DataUnit=HS.OpenDataUnit("")
NumItems=DataUnit.GetNumItems
For i=0 to NumItems-1
Call DataUnit.GetItem(i,strAccount,ICP,Custom1,Custom2,Custom3,Custom4,Data)
If Method="Holding" Then
Call HS.Con("",PCon,"")
End If
If Method="Global" Then
If StrAccount = "281100" Then
Call HS.Con("A#281100",PMin,"PMin")
'Call HS.Con("A#281000",vMIN,"")
Else
Call HS.Con("",POwn,"")
End If
End If
'If HS.Account.IsConsolidated(strAccount) and Data0 Then
'If Data0 Then
'HS.Con "A#"&strAccount,POwn,""
'If StrAccount = "281100" Then
'HS.Con "",PMin,""
'End If
'End If
'End If
Next
End sub
Sub Calculate()
HS.EXP "A#281100 = A#CapitalStock - A#Investments"
End Sub
My Doubts :
1. Is the expression correct for Minority Interest calculation ?
2. If so can we use it in Sub Consolidate() ?
3. Should the Minority Interest consolidate to its parent using PMin ? If so kindly provide the appropriate expression.
Looking forward to some help. Thanks in advance.

Hi,
If I got it correctly, you don't want the A#281100 calculation to happen for your holding company. There is a preferable way to do your consolidation that avoids involving the Calculate() altogether. So scrap your Calculate and write this Consolidate() instead:
Sub Consolidate()
Method=HS.Node.Method("")
PCon=HS.Node.PCon("")
POwn=HS.Node.POwn("")
vMIN=1-HS.Node.POwn("")
PMin=PCon-POwn
Dim strAccount,i
Set DataUnit=HS.OpenDataUnit("")
NumItems=DataUnit.GetNumItems
For i=0 to NumItems-1
Call DataUnit.GetItem(i,strAccount,ICP,Custom1,Custom2,Custom3,Custom4,Data)
If Method="Holding" Then
Call HS.Con("",PCon,"")End If
If Method="Global" Then
If StrAccount = "CapitalStock" Then
Call HS.Con("",POwn,"")
Call HS.Con("A#281100",PMin,"")ElseIf StrAccount = "Investments" Then
Call HS.Con("",POwn,"")
Call HS.Con("A#281100", (-1) * PMin,"")Else
Call HS.Con("",POwn,"")End IfEnd IfNextEnd subWith this code, the minority interest will calculate only for entities using the Global method.
I did not drive you to this solution immediately in order to avoid to confuse you, as well as because this does not address the issue of Calculation() running at many Value levels.
Regards,
--Kostas

Store printed wrong rebate envelope -- and two days left to gain the rebate!

To the Verizon support team,
I need some help.
After my recent upgrades at a Verizon store (somewhat pricey), the service agent helped me out a lot with the mail-in rebates. He printed envelopes, and the store provided metered stamps for mail.
However, after I mailed them in early- to mid-September, the US Post Service must have let the letters circulate in the mail for weeks.
Both my $120 mail-in rebate offer and my $50 mail-in rebate offer came back to me today (Sept. 21), stamped "Return to Sender: Insufficient Address. Unable to Forward."
The addresses were
"Mail In Rebate Offer
Promotion Code 10-172
PO Box 540047
El Paso, TX 79904-0047"
The deadline for these rebates is September 24 -- just 2 days!
I'm a professional, and my demands at work don't leave me time to baby Verizon through correcting this mistake. (Hence, I'm writing this forum post at 11:29 p.m. after finding out at 11:02 p.m. that customer service closes at 11:00 p.m.) However, nor do I have the money to let a $170 mistake go.
I need help:
The correct address and a brief, one-time-only grace period would be acceptable.
A store that I could take these rebate envelopes to and have them pass the rebate within the Verizon company would be better.
A correct address alone or a grace period alone would be unacceptable as they don't give me the ability to do much else.
What course of action does anyone suggest?
(Verizon service reps: e-mail me or call me if you have an immediate fix that we can arrange. My boss hates to see me on the phone, but I'll tell him the mistake and he might let it pass. He's an AT&T/iPhone guy. I had the last laugh on our business trip to Durango, Colo., but now he might have the last laugh.)

Well, this may make it better -- or it may just be confusion.
After posting on this forum, I visited the Rebate Center. I started the "Pre-submit rebate order", this is the matching result I found for my promotion code:
Search Results You searched for: 10-172 << Previous | Next >> Product: LG Ally
Promotion: Verizon Wireless Mail-In Rebate Offer with Purchases Made Between July 18, 2010 through September 6, 2010 Valid Purchase Dates: 07-18-2010 through 09-06-2010
Postmarked By: 10-12-2010
Rebate Reward: $100.00 Rebate Card
Product: Samsung Intensity II - Blue
Promotion: Verizon Wireless Mail-In Rebate Offer with Purchases Made Between July 18, 2010 through September 6, 2010 Valid Purchase Dates: 07-18-2010 through 09-06-2010
Postmarked By: 10-12-2010
Rebate Reward: $50.00 Rebate Card
This search result makes it sound like I don't have to worry about a "Month-from-purchase-date" deadline for my rebate. Instead, my rebate's real deadline is October 12.
Can anyone (with Verizon-level authority) confirm this, please?
If confirmed, the situation has now changed.
All I need is a correct address to mail the rebate materials.

Interest calculation and Invoicing

Hello
I'm looking for a way to generate an invoice follow the calculation of the interest.
Is there some one does alreday this or not ?
For information, we are using ECC 6 without CRM module.
Thanks for your help
Philippe

Hello Philippe,
Firstly you will need to create a documenyt typ ein OAB7 for this interest calculation button. Also create a number range in FBN1.
Then You can change the document type for the Interest calculation using the
following customizing setting:
    IMG path:
Financial Accounting -> Accounts Receivable and Accounts Payable
        -> Business Transactions -> Interest Calculation -> Interest
        Posting -> A/R: Calculation of Interest on Arrears
    Here you can select Goto -> Document type and you select the
    required document type.
hope this helps
Ray

FICA Rebate calculation and posting

Similar Messages

Maybe you are looking for