Enhancement Required for filling Reference No(LFBNR) in MIGO Tx

Hi All,
In Migo Transaction , when i am doing plant to plant goods transfer , i am entering source plant and target plant and doing posting of the material, and one document no .(MBLNR)is generated for a movement type .
Now by taking the same document no. MBLNR , i am doing place in storage location ,in migo .
Now my requirement is in MSEG , i want to fill the refernce document no (LFBNR) as the document no i got , while i do the remove from storage location(i.e, the no with refernce to what i am dng place in storage loc.).
Is there any exit or badi , that will do the need ful.
Hope i am clear...
If i am not clear with my question , for further info , pls ask ....
Regards
Rajendra

Hi Both..
I tried passing X to force change of pai method.
But still this message is cmoing when i run MIGO.
BAdI: Field GOITEM-LFBNR not ready to accept input (Change will not be adopted)
I tried with the exit MB_CF001, but it ios triggring in the MIGO process.
Regards

Similar Messages

Enhancement required for VA02

Hi
The issue is related to my earlier thread :-
[Contract Quantity not updated after assigning Reason for Rejection in Order;
Now to resolve this issue we need to keep the Message V4 096 as "warning", presently we set it as an "error" message. Now as soon as we make it as warning message, user will be able to either increase or decrease the quantity of Sales Order in VA02. But our requirement is that User should be able to reduce the quantity of Sales Order but should NOT INCREASE the quantity of sales Order.
So reduction of quantity should issue a "warning " message due to SAP Standard messge V4 096, whereas increase in quantity must give an "error" meassage, this require some enhancement.
One more thing I would like to understand that, since this process will take place in VA02, so in the table VBAP-KWMENG the existing quantity will be mainatined. While changing the quantity in VA02 the said field will not be updated until we save the document, so how can we compare the chnaged quantity with the already existing quantity before saving the document.
The change in quantity will be done in transaction VA02.
Please guide me how can I achieve my above said requirement. If some exit is required then please let me know the exit and the possible logic.
Thanks and Regards
Amitesh Aannd

Hi,
If you are implementing the logic in include 'MV45AFZZ' then internal table
XVBAP contains the changed value and YVBAP contains the unchanges values.
Regards,
Narayan

Enhancement required for IM52 Transaction validation

Hi all,
How we will hadle screen validation in IM52 like i am entering POSID PRNAM and approval year and after executing i want to validate on the basis of same input.
is there any badi or user exit or enhancement.
appreciate your help!!!
Regards,
Vikas
Edited by: vikas sharma abap on May 24, 2011 2:35 PM

Hi
Kindly check the below enhancements and Badi's.
Enhancement
AAIC0003                                IM Summarization: Definition of User-Defined Characteristics
AAIP0001                                IM Drilldown: Assignmt of Actual Values to Budget Catgories
AAIP0002                                IM Drilldown: Definition of User-Defined Key Figures
AAIP0003                                IM Drilldown: Definition of User-Defined Characteristics
Business Add-in
IM_BEHAVIOUR                            IM: Define Customer-Specific System Behavior

Enhancement LMR1M002 for GR/IR clearing account in MIGO

Hi ,
Did anyone implement the enhancement LMR1M002 to change the GR/IR clearing account while using tcode MIGO.
Please help me how to implement the SAP customer exit , there is a note SAP Note 301477 and 165692 but I was unable to code
Regards
Prasanth Kasturi

Discussion moved. Please use Internationalization and Unicode for CIN related queries.

Reference Document LFBNR in MIGO

Hi all,
Question.
When i enter materials with transaction MIGO the field "Reference Document" is completed with the some number of the material document but it some cases is not working like this.
The thing is that i´m using the same plant, storage location and movement type (101).
Anyone know why ???
Thanks !

Hi Dalmiro,
This is controlled by SPRO settings.
SPRO - MM - Inventory Management & Physical Inventory - Settings for Enjoy Transaction - Settings for Transactions and Reference Documents.
Regards,
Ramesh

Why Enhancement:MBCF0005 for goods receipt is useless in MIGO??

Hi experts,
    When i use enhancement:MBCF0005 , it cann't take effect in goods receipt (MIGO,MB01).
i actived both EXIT_SAPM07DR_001 and CI_AM07M, and debugged or inserted some codes like " Message 'error' type 'E' " in ZXMBCU05. But it cann't take any effect in MIGO or MB01,like the enhancement never changed.My SAP version is 4.7. Can anysome give me some suggestion? Thank you very much!
Regards
Joey

Hi, in our company's subcontracting processes,we have two types of PO, the "Account assignment category" are "P" (project) and "F" (order). When do GR ,the movement types are 101 and 543 O. For the two different PO ,my client wants to record 543 under different G/L Acounts.
In OMWN , the Account Assignment can only configure like this:
543 O     V   WA01       2 GBB     VBR
. For the same Valuation Class   "VBR" can only aim at one G/L Acount. So i try to use enhancement to solve it. Could anyone give me some suggestion?
Regards
Joey

Reference document LFBNR

hi all
I want to activate the field reference document (LFBNR) in MIGO screen.....
In EKBE table in few cases this value is coming for 105 document number and in few cases it is not coming.
Is this field is linked with vendor account group setting???
Regards
SAP MM

u willnot find LFBNR for all movement types.
u will find it fpr movement types like 122 etc.
but if u need in some specific movement types then pls follow:
spro-mm-inventory management and physical inventory--settings for enjoy tranaction-settings for goods movementsfield selection per movement typechoose new entries-give the movement type,field name and choose required/optional entry and save.
regards,
indranil

I received an oline fax, error message "You are not signed up for an appropriate enhanced pdf delivery option required for this request" How do I fix this?

I received an oline fax, error message "You are not signed up for an appropriate enhanced pdf delivery option required for this request" How do I fix this?

Hi howardw93055634,
Please tell me where you are seeing this error message. It's not one that I'm familiar with as being related to Acrobat or Reader. Is it coming from your online fax service, or does it appear when you try to open the PDF file that you received in Acrobat or Reader?
Best,
Sara

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

Can we change the enhancement set for a component

Dear All
I have a situation where in we need to change assign a different enhancement set to all our components which got enhanced.
We can only have 1 enhancement set active for a client.
Now in our case
Say for client 300 we were using Enhancement Set E1.
Our requirement is to create one more enhancment set E2 and assign it to client C1. We can do that.
Do we we have a mechanism to move all development already done using E1 to E2?
Please Help.
Thanks
Gaurav Sahai

Hi Gaurav,
We create enhancement set in SM30, then assign it to client also there.
After that, when we go to BSP_WD_CMPWB - by default we see the enhancement set assigned to the client. Now there are 2 things:
1. to use different enhancement set for different users - you can implement badi component_loading to load different enhancement set depending on business requirement by writing code:
RV_RESULT = <name of ENHANCEMENT_SET. >
there is a default implementation in the system for reference.
2. all enhanced views can be seen in transaction SM34, give name of view cluster as BSPWDVC_CMP_EXT
Select your enhancement set -> go to Enhancement Definitions (here you see components enhanced) -> select any -> go to Controller Subsitutes (here you see all view enhanced).
You can try copying all these entries into another enhancement set. I am not sure if it will allow same entries in two different sets (if it doesn't you will have to delete from the other).
I hope that resolves your query.
Thanks,
Rohit

BADI/Enhancement spot for VL01N (Outbound Delivery)

Hi guys,
while creating outbound deliver it needs to be change the contents of XMKPF (BKTXT), is there any BADI/Enhancement spot for the VL01n.
Kinldy provide some inputs for this one...which is very helpful to me.
Regards,
Vijay

Hi guys,
Thanks for your valuable replies.
special thanks to Kiran Sure because my requirement is full filled by given enhancement spot/badi is LE_SHP_GOODSMOVEMENT
regards,
Vijay

Import error in QA after implementing Enhanced CTS for PI NW 7.1 SP07

Hello Experts,
I had configured the enhanced CTS for transports in PI 7.10 SP07 landscape with reference to guide : How To ... Configure Enhanced CTS for SAP NetWeaver Process Integration 7.1 SP06.
We have created service user dedicated for import in QA box, having the SAP standard roles assigned SAP_XI_CMS_SERV_USER, SAP_XI_DEVELOPER and SAP_XI_CONFIGURATOR to the user.
But still at time of deployment facing the error " class com.sap.aii.util.misc.api.BaseRuntimeException:Parsing generic data instance: begin of unexpec
>>>ted element 'script'! "
Below is the complete tranport request log file...
Please help me on this asap..

Deployment
Transport request   : D15K900284
System              : Q15
tp path             : tp
Version and release: 375.33.79 710
Reading files from directory: /usr/sap/trans_P15/data/D15K900284/
   found file: 6f334b007a0211df9ae500212862bd96
Collected 1 filenames from [/usr/sap/trans_P15/data/D15K900284/]
file deployment: Start copying files to '/sapmnt/Q15/global/xi/repository_server/import/D15K900284'
file '/usr/sap/trans_P15/data/D15K900284/6f334b007a0211df9ae500212862bd96' successfully copied
file deployment: 1 file(s) copied
CTS Deploy Service - Version 0.92 06.03.2007
========================================================================
Deploy Web service destination = CTSDEPLOY
Directory = /usr/sap/trans_P15/data
SDM Deploy URL =
SLD Deploy URL =
XI Deploy URL = http://dbciq15.al.sw.ericsson.se:59700
Double-stack system Q15
Deploy for XIR
Deploy File = 6f334b007a0211df9ae500212862bd96
Start of Web service log
Deploy Service called with following parameters:
CommunicationData-Type:1
CommunicationData-Address:http://dbciq15.al.sw.ericsson.se:59700/rep
CommunicationData-Host:dbciq15.al.sw.ericsson.se
CommunicationData-Port:59700
CommunicationData-User:'filled'
CommunicationData-Password:'filled'
Deployable(0)
Deployable-Type:1
Deployable-Id:/usr/sap/trans_P15/data/D15K900284/6f334b007a0211df9ae500212862bd96
class com.sap.aii.util.misc.api.BaseRuntimeException:Parsing generic data instance: begin of unexpec
>>>ted element 'script'!
com.sap.aii.util.hmi.core.gdi2.GdiCharStreamer$GdiCharReader.startElement (GdiCharStreamer.java:372
>>>)
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement (AbstractSAXParser.java:5
>>>33)
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement (XMLNSDocumentSca
>>>nnerImpl.java:330)
com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElement
>>>Hook (XMLNSDocumentScannerImpl.java:779)
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dis
>>>patch (XMLDocumentFragmentScannerImpl.java:1794)
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument (XMLDocumentFra
>>>gmentScannerImpl.java:368)
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse (XML11Configuration.java:834)
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse (XML11Configuration.java:764)
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse (XMLParser.java:148)
com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse (AbstractSAXParser.java:1242)
com.sap.aii.util.hmi.core.gdi2.GdiCharStreamer.readGdi (GdiCharStreamer.java:54)
com.sap.aii.util.hmi.core.gdi2.GdiCharStreamer.stringToGdi (GdiCharStreamer.java:108)
com.sap.aii.util.hmi.api.HmiHttpClientImpl.sendRequestAndReceiveResponse (HmiHttpClientImpl.java:94
>>>)
com.sap.aii.util.hmi.api.HmiClientAdapter.invokeMethod (HmiClientAdapter.java:95)
com.sap.aii.ibtransportclient.impl.gen.XiHmiClient.invokeHmiTransport (XiHmiClient.java:161)
com.sap.aii.ibtransportclient.impl.XiTransportClientImpl.writeChangelistData (XiTransportClientImpl
>>>.java:234)
com.sap.aii.ibtransportclient.impl.XiTransportClientImpl.writeChangelistData (XiTransportClientImpl
>>>.java:251)
com.sap.aii.ibtransportclient.impl.XiTransportClientImpl.writeChangelistData (XiTransportClientImpl
>>>.java:255)
com.sap.cts.tcs.XICommunicator.importContent (XICommunicator.java:67)
com.sap.cts.deployer.XiDeployer.deploy (XiDeployer.java:63)
com.sap.cts.core.DeployManager.deploy (DeployManager.java:54)
com.sap.cts.ejb.DeployBean.deploy (DeployBean.java:100)
sun.reflect.GeneratedMethodAccessor9371_10000.invoke (null:-1)
sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:25)
java.lang.reflect.Method.invoke (Method.java:585)
com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal (RequestInvocationC
>>>ontext.java:43)
com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed (AbstractInvocationCont
>>>ext.java:166)
com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke (Interceptors_States
>>>Transition.java:19)
com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed (AbstractInvocationCont
>>>ext.java:177)
com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke (Interceptors_Resource.java:
>>>71)
com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed (AbstractInvocationCont
>>>ext.java:177)
com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute (Interceptor
>>>s_Transaction.java:38)
com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke (Interceptors_Transaction
>>>.java:22)
com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed (AbstractInvocationCont
>>>ext.java:177)
com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed (AbstractInvocationCont
>>>ext.java:189)
com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke (Interceptors
>>>_StatelessInstanceGetter.java:16)
com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed (AbstractInvocationCont
>>>ext.java:177)
com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke (Interceptors_SecurityC
>>>heck.java:21)
com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed (AbstractInvocationCont
>>>ext.java:177)
com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke (Interceptors_Excepti
>>>onTracer.java:16)
com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed (AbstractInvocationCont
>>>ext.java:177)
com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain (DefaultInvocat
>>>ionChainsManager.java:133)
com.sap.engine.services.ejb3.webservice.impl.DefaultImplementationContainer.invokeMethod (DefaultIm
>>>plementationContainer.java:203)
com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process0 (R
>>>untimeProcessingEnvironment.java:353)
com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.preProcess
>>>(RuntimeProcessingEnvironment.java:329)
com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process (Ru
>>>ntimeProcessingEnvironment.java:211)
com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWOLogging (ServletD
>>>ispatcherImpl.java:155)
com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWithLogging (Servle
>>>tDispatcherImpl.java:96)
com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost (ServletDispatcher
>>>Impl.java:66)
SoapServlet.doPost (SoapServlet.java:51)
javax.servlet.http.HttpServlet.service (HttpServlet.java:727)
javax.servlet.http.HttpServlet.service (HttpServlet.java:820)
com.sap.engine.services.servlets_jsp.server.Invokable.invoke (Invokable.java:66)
com.sap.engine.services.servlets_jsp.server.Invokable.invoke (Invokable.java:32)
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet (HttpHandlerImpl.java:431)
com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest (HttpHandlerImpl.java:289
>>>)
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet (RequestAnalizer.java:388)
com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet (RequestAnalizer.java:377)
com.sap.engine.services.servlets_jsp.filters.ServletSelector.process (ServletSelector.java:85)
com.sap.engine.services.httpserver.chain.AbstractChain.process (AbstractChain.java:71)
com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process (ApplicationSelector.java:
>>>160)
com.sap.engine.services.httpserver.chain.AbstractChain.process (AbstractChain.java:71)
com.sap.engine.services.httpserver.filters.WebContainerInvoker.process (WebContainerInvoker.java:67
>>>)
com.sap.engine.services.httpserver.chain.HostFilter.process (HostFilter.java:9)
com.sap.engine.services.httpserver.chain.AbstractChain.process (AbstractChain.java:71)
com.sap.engine.services.httpserver.filters.ResponseLogWriter.process (ResponseLogWriter.java:60)
com.sap.engine.services.httpserver.chain.HostFilter.process (HostFilter.java:9)
com.sap.engine.services.httpserver.chain.AbstractChain.process (AbstractChain.java:71)
com.sap.engine.services.httpserver.filters.DefineHostFilter.process (DefineHostFilter.java:27)
com.sap.engine.services.httpserver.chain.ServerFilter.process (ServerFilter.java:12)
com.sap.engine.services.httpserver.chain.AbstractChain.process (AbstractChain.java:71)
com.sap.engine.services.httpserver.filters.MonitoringFilter.process (MonitoringFilter.java:29)
com.sap.engine.services.httpserver.chain.ServerFilter.process (ServerFilter.java:12)
com.sap.engine.services.httpserver.chain.AbstractChain.process (AbstractChain.java:71)
com.sap.engine.services.httpserver.server.Processor.chainedRequest (Processor.java:295)
com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run (Processor.java:222)
com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
java.security.AccessController.doPrivileged (AccessController.java:-2)
com.sap.engine.core.thread.impl3.SingleThread.execute (SingleThread.java:152)
com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
End of Web service log
Return Code = 12
Highest Return Code = 12
Deployment
End date and time : 20100617112451
Ended with return code: ===> 12 <===

On installation of Firefox 4 beta, it tells me that it won't run on my Mac. When I go to system requirements, it takes me to a page for Firefox3.6 requirements. Where can I find the requirements for the beta?

The link to system requirements for Firefox 4 beta takes you to a page that gives you the requirements for Firefox 3.6 instead. I assume that the requirements for the beta are different as I can't seem to install the beta on my Macs. Where can I find the beta system requirements?

I never expected Mozilla to neglect the users of Apple's PowerPC (PPC) computers, while still supporting much older operating environments such as Windows XP. So, I should just throw away a $6,000 system, which is still fast and functional, and contribute masses of heavy metals to land-fills because…?
I'm hurt and confused after supporting Firefox for many years — installing and using it not only on my own computers but on most of my customers' computers. Now I have to tell my customers with PPC Macs they can't have a secure cross-platform browsing experience from Mozilla. They'll have to learn to use some other browser, or buy a new computer.
If one doesn't buy a new computer every year, one doesn't deserve Firefox 4. This is sort of sounding more like a Microsoft™© doctrine. (But wait, I can still have Firefox 4 on a ''SERIOUSLY CRAPPY WINDBLOWS XP pile of rubbish?!'') Please open your eyes Mozilla. This just doesn't make sense.

I am trying to find an example of written technical requirements for iPhone apps

as I am trying to design an app for the Iphone need a frame of reference. Does anyone have access to an example of an effective technical requirement template? Thanks for your help!

the free Xcode from the MacAppStore is needed to develop apps, register for an iOS developer account for technical reference, paid membership is required to publish your apps to the AppStore : http://developer.apple.com/devcenter/ios/index.action

Enhancement request for VAT Report of Customer and Vendor.

Hello SAP Gurus,
Have enhancement request for adding new fields in existing VAT report of Customer and Vendor like user id, GL account etc.
As I am fresher, can you please help me that how I need to approach. Thanks for your support.
Regards,
Saleem

Hello Saleem,
Almost all fields required for VAT reporting are available in standard tax report
S_ALR_87012357 .
You have to configure the layout from the selection screen as below
regards
pb

Enhancement Required for filling Reference No(LFBNR) in MIGO Tx

Similar Messages

Maybe you are looking for