Steps in Fore Cast Based MRP-reg

Hi,
we would like to implement forecast based MRP for spare parts which we supply against sales order from dealers
request you to provide us step by step working with forecast based MRP
1. what are the inputs for forecast based MRP
2. Process of forecast based MRP
3.Out put of forecast based MRP
4. reduction of requirements
etc...
madhu kiran.

Hi Madhu,
Use
Forecast-based planning is also based on material consumption. Like reorder point planning, forecast-based planning operates using historical values and forecast values and future requirements are determined via the integrated forecasting program. However, in contrast to reorder point planning, these values then form the basis of the planning run. The forecast values therefore have a direct effect in MRP as forecast requirements.
Features
The forecast, which calculates future requirements using historical data, is carried out at regular intervals. This offers the advantage that requirements, which are automatically determined, are continually adapted to suit current consumption needs. The forecast requirement is reduced by the material withdrawal so that the forecast requirement quantity that has already been produced is not included in the planning run again.
Reducing Forecast Requirements
*Reducing forecast requirements by consumption
If consumption is higher than the forecast requirements in the current month, then the system also reduces future forecast requirements.
*Reducing current forecast requirements by consumption
If consumption is higher than the forecast requirements in the current month, then the system does not reduce future forecast requirements.
*Average reduction of the forecast requirements
The reduction of the forecast requirements is based on average daily consumption. Actual consumption data is not relevant.
The system calculates the average daily requirement first using the formula forecast requirement/number of workdays in the forecast period.
The forecast requirements are then reduced by the quantity resulting from the following formula: number of workdays worked x average daily requirements.
Period Pattern and Forecast Periods
You can specify the period pattern for the forecast (daily, weekly, monthly or per accounting period) and the number of periods to be included in the forecast individually for each material. It is possible, however, that the forecast period pattern is not specific enough for planning purposes. In this case, you can define per material that the forecast requirements should be divided according to a finer period pattern for planning. You can also define how many forecast periods are to be taken into account during requirements planning. The splitting indicator is defined in Customizing for MRP per plant and per period unit and is assigned to the material in the material master.
For a monthly forecast, the requirements date would be set on the first workday of the month because, for planning, it is assumed that the total requirement must be available at the beginning of the period. You can then divide this monthly requirement into either daily or weekly requirements.
Prerequisites
You have set an MRP type for forecast-based planning in the material master (MRP 1 view).
You define MRP types in Customizing for MRP in the IMG activity Check MRP types.
Process Flow
1.The system copies the requirements quantities that it has forecast in the requirements planning run and calculates net requirements. During this calculation, every period is checked to make sure that the forecast requirements are covered either by available stock, by planned receipts from purchasing or by production. If a material shortage occurs, the system generates a procurement proposal.
2.The system calculates the quantity recorded in the procurement proposal according to the lot-sizing procedure that you specified in the material master. Depending on the lot-sizing procedure, several forecast requirements are grouped together into one lot.
3.For every procurement proposal, the system calculates the date on which it must be converted into a purchase order or a production order.
Hope this helps you.
Regards,
Vinodh

Similar Messages

What r the steps to create task based user interface for interaction center

Hi all,
            Can any one please let me know the steps to create task based user interface for interaction center? It would be great
            if anyone can share document with step by step.
Thanks,
Baasanthi

Hi all,
            Can any one please let me know the steps to create task based user interface for interaction center? It would be great
            if anyone can share document with step by step.
Thanks,
Baasanthi

Need A scenario based step by step process for DTP

Hi BWS,
Can any body give me a scenario based step by step documnet for Data Trasper Process(DTP)..
Cheers
Mak

Hi,
Below is the link for the same. http://help.sap.com/saphelp_nw2004s/helpdata/en/42/f98e07cc483255e10000000a1553f7/frameset.htm
Assign points if this helps.
Regards,
Anil

Export custom step properties for all sequences based upon expression

I want to export only my custom step properties to a database. I realize this can be done one at a time but I'm looking for a more general, quicker solution since I have dozens of custom steps and many instances of each. I can probably do this, but if someone has already developed a method I could use the info. Thanks.
kph

Hi kph,
Unfortunately, there is not a straightforward way to solve this
problem. TestStand does not currently support any database
configuration through programmatic means. The customized database
must be configured ahead of time. I would handle the issue by
setting up this database in configure >> Database Options.
The quickest solution for customization would be to duplicate one of
the default Schemas (for example, Generic Recordset) under the "Schema"
tab. Under the statements tab, you can then cut out all of the
unwanted statements (it sounds like you'll want to cut out most of
them) and add new statments for your custom steps. In this
step, be sure to reference your custom step type for each statement in
the "Types to Log" field.
Under the Columns/Parameters tab, you can then add all of the properties you would like to save for each configured statement.
At this point, you can use TestStand to create a SQL script file to
match the Schema you just created. From the Schema tab, you can
select the Build .sql File dialog box. After saving and running
the script, you will have successfully created the required tables for
the custom schema.
At this point, the custom properties should log to the database.
Hope this helps in your application development!
Andrew W. - Applications Engineer

Project Based MRP run issue

Hi Friends,
There is one issue reg. Project Based MRP Run as below :
We are running MRP through MD51 (Project based MRP run). For this we are assigning FG material code under respective WBS Element which generates Network reservation with movement type 281Q which is base of MRP run in MD51. After MRP run we get planned order generation and then convert it to Production order and execute Production Order to receive Project Stock after GR.
After receiving Project stock and then selling it through Post Goods Issue through SD cycle, project stock is consumed but network reservation is not getting closed which results in again generation of planned order if MRP is run again.
I need your valuable inputs if we are missing any configuration setting which can set Final issue indicator in reservation while Posting Goods Issue (PGI) in SD because FI indicator checking will only ensure reservation doesnu2019t take part in planning again.
Your earliest reply will be highly appreaciated.
Regards,
Tejas

Hi Vivek,
Thanks for your reply. Actually my issue has got resolved the way suggested by Mario Adler.
Hi Mario,
Thanks for your solution. PGI through Project is working fine for me.
Hi Krishna,
Follow the procedure as suggested by Mario which will resolve your issue.
Once again thank you all for spending your precious time to respond my query.
Regards,
Tejas

Steps required for cin configuration

hi,
can anybody give me the steps required for cin configuration.

Hi,
CIN Setting:
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

Workflow for Mail to MRP Controller

Hello Experts
I am configuring to activate workflow for mail to MRP controller, I am not able to activate event linking. Does any one know how to activate linking? Any help is appreciated.
Here is configuration path
SPRO - Materials Management - Consumption Based Planning - Evalution - Activate workflow for mail to MRP controller
Thanks
Ankit

Hi,
If you follow the steps and click on 'Assign Agents' it list the workflow template that is triggered e.g. WS03100020. If you open the builder (transaction SWDD) and view workflow WS03100020 you can see that there is no triggering event specified so you cannot activate the event linkage.
Also the object used in this workflow is BUS1001and not BUS3020. If you want to trigger this workflow then you should check what event should triggered it and add it to the workflow via SWDD => Basic Data => Triggering events.
What transaction should trigger this workflow? Switch on your event trace and recreate thje scenario. See what events are raised and see if one can be used to trigger the workflow. If no events exist then try to find user Exit or BAdi and trigger your event using function module SAP_WAPI_CREATE_EVENT or use SAP_WAPI_START_WORKFLOW to trigger event directly without events.
Regard,
Eddie

Lot Sizes Used for Fore cast planning

Dear all,
For fore cast planing and Automatic reorder point planning what are the lot sizes are use full and what are the advantages and effects for each lot size procedure.
I am expecting answer for this question from all of you.
Regards,
Krishna

Hi
These fore cast planing and Automatic reorder point types are consumption based planning.
Hence for these MRP types normally, lot for lot ( EX ) will be used.
You can go through the following link for further info on lot sizing procedures.
http://help.sap.com/erp2005_ehp_01/helpdata/en/f4/7d3f9344af11d182b40000e829fbfe/frameset.htm
Regards
YMREDDY

Fore casting result

Dear all,
This is regarding forecasting results of all materials which are maintained under forecast view in a material master.
Basically i need a single report of all materials fore cast results based on MRP controller
Any body can you help on this point.
Thanks&Regds
Partha sarathi ray

Hi
I do not think such standard report is available .
you ahve to devcelope customized report.
Regards
YMREDDY

Excise Invoice for Order Based Billing Scenerion

Dear Friends,
We have a scenarion, wherein we are working with Sales Order Based Billing.
We are in the process of Implementing CIN with TAXINN.
Is it possible to create excise invoice for the scenarion of Sales Order based billing, instead of delivery based billing.
If yes, what are the steps we need to follow to configure the same.
Regards,
Harsh

hi
If u want the create Excise Invoice for Order Based Billing Scenerion, u must be set in billing document in General control in fields is.
 SD document categ. M Invoice
Transaction group 7 Billing documents
Billing category
Document type
Negative posting No negative posting
Branch/Head office Customer=Payer/Branch=sold-to party
 No
Invoice list type LR Invoice List
Rebate settlement
Standard text 
Best copy of F2 Invice. and this billing type in outgoing invoices in Tax on goods movement in Logistics general.
Rewards point it helps

MRP FOR CBP MATERIALS- MRP TYPE 'VB', IN MD01

Dear PP Gurus,
My client wants to run MRP for consumption based planning materials (MRP type: VB), for there individual plants. For this I have suggested MD01 for planning in the perticuler plant by using the user exit available in the screen. But then also, after MRP run system is plannig all the materials which have MRP type PD as well as VB.
The user exit parameters are
User Exit Key: 002 (Consider MRP Controller for CBP)
User Exit Parameters : CBP
"CBP" is my MRP controller for materials which have MRP type 'VB'.
Pl suggest me what & where is the problem?
Thanks,
Regards,
Sachin Patil.

Dear,
It is possible through
User Exit: M61X000.
You need to maintain MRP group assign it to the VB type material then go ahead.
For details please refer this thread,
Re: mass MRP run
Regards,
R.Brahmankar

N-Step workflow for invoice

1. Is there a way to implement n-step (more than 2 )approvals for invoices? Can I use the same BADI for n-step approval for shoupping cart?
2. If a vendor is not on supplier portal is there a way send a offline RFQ and get the bid somehow in the system without having vendor being created in the system?

Hi
Please go through this ->
It is possible to copy the standard workflow and make you custom workflow acordingly.You just have to copy standards workflow and all subworkflow under this as well.You have to take care of attributes of workflow in same way as standard workflow.
Implementing a BADI - BBP_WFL_APPROV_BADI using SE18 Transaction is also feasible solution.
Invoice rejected in the invoice workflow.
Re: Invoice Workflow : Dialog work item created
Re: Sample Code needed for N-step approval SC BADI
Re: Invoice BUS2205 Workflow
Approval workflow is ambiguious- for Invoice WF
Please refer to these links as well.
N-step Approval workflow
http://help.sap.com/saphelp_srm40/helpdata/en/17/40a86c773d6c41801d78af1a34b90f/content.htm
N-step Dynamic approval
http://help.sap.com/saphelp_srm50/helpdata/en/17/40a86c773d6c41801d78af1a34b90f/frameset.htm
SRM Business Workflow
http://help.sap.com/saphelp_srm50/helpdata/en/8b/4fa9585db211d2b404006094b92d37/frameset.htm
Dynamic Modification - Workflow
http://help.sap.com/saphelp_srm50/helpdata/en/84/dda441e79ead5fe10000000a1550b0/frameset.htm
Item-based Approval for Shopping carts
http://help.sap.com/saphelp_srm50/helpdata/en/a3/a6a34098022a54e10000000a1550b0/frameset.htm
Business Add-Ins
http://help.sap.com/saphelp_srm50/helpdata/en/bc/6129383d5ec70ce10000009b38f8cf/frameset.htm
Do let me know incase you face any issues in Design / coding of this N-level Approval workflow.
For the 2 point, it is not sure. I don't think there is any way to send offline RFQ.
Hope this will help.
Regards
- Atul

BADI or User Exit for scheduling in MRP

Hello,
I am searching a possibility to influence the scheduling of planned orders, when they are created in the MRP run. There exists a BADI which is called when creating planned orders manually, but not in MRP. Its name is MD_PLDORD_SCHEDULING
Does anybody know about such an alternative for scheduling in MRP?
Thanks in advance
Roland Böhm

Hi,
Check these Enhancements
LMDR2001 User exits restr. profiles of opt. pur.ord.-based load bldg
LMDZU001 User exits in additional planning
Regards,
Satish

Consider the pending PO and Purchase requisition fore cast base planning (vv)

Dear friends,
Our client at presently they are using Forecast based planning for RAW material , in that requirement will not consider Pending Pur req and PO, Is that any option for consider pending PO for Forecast based planning , kindly do the needful.
Regards,
Sabhapathy R

Hello Sabhapathy,
I am not sure why you would need to consider pending PurReqs and POs. These pending documents are considered during the MRP run, but not to generate the forecast.
Forecast-based planning is based on material consumption.
The MRP will generate PurReq or Planner Orders considering the open documents. For example:
+ Current stock = 1000 CS
+ Open PRs and POs to arrive = 400 CS
- Forecast Requirement =1500 CS
- Safety Stock policies = 100 CS (safety stok)
- New replenishment orders = 200 CS
Thanks and Regards,
Mariano

Consumption Based MRP

Hi,
We are running consumption based MRP using MRP Type as VB. We run consumption based MRP daily. In this, when ever there is change in stock level due to consumption, the system reschedules the old schedules also. We don't want to disturb the old schedules generated by MRP as we confirm the vendors as a Firm Schedule.
Can you please guide me on how i can run consumption based MRP daily and not tamper old schedules.
Regards
Shankar

Hi Shankar,
SAP online help:
http://help.sap.com/erp2005_ehp_04/helpdata/EN/1a/8b4bbecdd74536acd4e970faaf6e2d/frameset.htm
SAP recommends working with scheduling agreements with release documentation.
Use a document type for scheduling agreements with release documentation. In the standard system, document type LPA is supplied for this purpose. (In the standard system, the Release docu. indicator is selected for document type LPA in Customizing for Purchasing under Scheduling Agreement à Define Document Types.)
It is sensible to carry out the planning run daily and generate releases (delivery schedules) automatically once a week, for example. You can set up the system in such a way that releases are generated for changed scheduling agreement items (materials) only.
http://help.sap.com/erp2005_ehp_04/helpdata/EN/3b/66596bda7b11d1b6330000e8a738dc/frameset.htm
Scheduling agreement releases provide information to vendors regarding the quantities of a material that are to be delivered and the desired delivery dates. A scheduling agreement release enables you to record the current status of the lines of a delivery schedule stored in the system for a scheduling agreement item and then transmit this status to the vendor.
Are you using release SA release?
It seems this is the solution for your problem
Regards,
Csaba
Edited by: Csaba Szommer on Mar 1, 2010 1:47 PM
Edited by: Csaba Szommer on Mar 1, 2010 1:48 PM

Steps in Fore Cast Based MRP-reg

Similar Messages

Maybe you are looking for