Information related SMMAIN table in sap

Hi Experts,
Can anyone brife me about the table SMMAIN, its functionality in sap.
I tried to findout many forums but didnt received any.
Please guide....
Thanks,
Functional Consultant

Good Afternoon,
Is this table a module specific? how it works? application of this table?
Can you please brief me out.
Thanks in advance.....
Regards,
Functional Consultant

Similar Messages

RELATIONAL DATABASE TABLES IN SAP BW

hi
friends please give me the information regarding the RELATIONAL DATABASE TABLES IN SAP BW?

Hi,
See the tables.
InfoObjects Table:
RSDIOBJ Directory of all InfoObjects
RSDIOBJT Texts of InfoObjects
InfoCube Tables:
RSDCUBE Directory of InfoCubes
RSDCUBET Texts on InfoCubes
DSO Tables:
RSDODSO Directory of all ODS Objects
RSDODSOT Texts of all ODS Objects
PSA Table:
RSTSODS Directory of all PSA Tables
For reports:
RSRREPDIR
Thanks & Regards,
Sathish

Information related to Public Sector -SAP

Hi All,
Please can some one help me to give General information on SAP - Public Sector like
1) Over view
2)The main modules and some brief about them and so on.
I would be thankful for your help.
Even if some links are given it will be helpful to me..
Thanks,
Vengal Rao.
Edited by: vengalrao jalgam on Nov 14, 2011 8:21 PM
help.sap.com

HI Ritesh
Which version of XI do you have
XI 3.0 last SPS was SPS22
PI 7.0 last was SPS 14
On Netweaver 7.1 platoform it is going through SPS 4
Thanks
Gaurav Bhargava

Passing information from an iView to SAP - ESS Related

Hi,
How do you pass information from an iView to SAP?
For example, in my task the User will log into ESS.
Then they will click on the iView link and be prompted with a dialog for their service number (how is that done)?
Now, on SAP's side (backend), I need to take that service number and their user id and pass it to the transaction.
For the service number, I will have to add leading zero's.
How is this done?
What is the ESS cookbook and does anyone have it?
Thanks,
John

Thank you for the response - it gives me a better idea of how this system works.
But how would you modify the information that is being passed? Would it be passed to a structure, which can be accessed from within SAP? For example, the medical service number would be entered as 15. It would be stored and then my program would extract that number, add leading zero's and call the relevant transaction.
Please help.

Who can give me all the name of system table or organization table in sap?

Who can give me all the name of system table or organization table in sap? such as the table stores the client,company code ,plant,transaction code ,sap menu,purchase organization along with the relation between organizations such as
the relation between company code and plant, the relation between company and purchase organization and so on.Pls supply the list of table name or the url where I can see these information.
Thank you in advance.

Hi YuLin
refer this link you will get all tables in SAP with description and relation.
http://www.erpgenie.com/abap/tables.htm
regards
Yogesh

CAN YOU PLEASE GIVE INFORMATION RELATED TO CIN INFORMATION

hi gurus,
Can any body provide information about the Setoff excise duties in the country india version.
can any provide detial information about Excise Transaction type
Thanks in advance
Regards,
ch.srinivas

Hi,
Excise Invoice:--
J1ID for configuration and J1IIN, J2I7, J1I5, J1I5, J2I6, J1IP for creating, extracting and printing excise invoice
Basically Cin is divided in to two types:
1. TAXINJ - Is a Routine Based that is used in the condition types. it will work on the logic what ever is there in the Routine.
2. TAXINN: - Is a condition Record based. Means we have to create condition records for each and every condition type that you are going to use in the Pricing Procedure.
Since Version 4.7 this TAXINN came into picture and start using this.
And one of the important points is since 4.6 c CIN comes a separate package. But after introduction of 4.7 Version, CIN is coming the SAP Package itself and even in the Customer Master Record also we will find the CIN Icon.
Basically 4 types of Pricing Procedures are used in CIN and are as follows:
1.JDEPOT - Depot Sales
2.JEXPOR - Export Sales
3.JFACT - Factory Sales
4.JSTKTR - Stock Transfer
Country Version India comes with four pricing procedures as follows:
JINFAC (Sales from manufacturing plants)
JINEXP (Export sales)
JINDEP (Sales from depots)
JINSTK (Stock transfers
CIN:
IMG > Logistics - General > Tax on Goods Movement > India > Basic Settings >
Maintain Excise Registrations
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
Excise Registration IDs
In this activity, you maintain excise registration IDs. You create one ID for each of your business's excise registrations.
Activities
For each excise registration in your business create a registration ID, and state:
Which taxes the registration covers (additional excise duty, special excise duty, and cess)
Fields for any taxes that are not covered will be hidden in transactions involving excise duty.
The maximum number of items to be printed on each excise invoice
Whether you are allowed partial CENVAT credits
Maintain Registration ID NUMBER, Excise code number, excise registration number
Excise Registration Number
A number assigned to each premises or location that has registered as a manufacturer with the excise authorities.
Every entity with an excise registration number is required to keep its own excise books.
ECC Number
Specifies the organization's ECC number.
Excise Registration Number
A number assigned to each premises or location that has registered as a manufacturer with the excise authorities.
Every entity with an excise registration number is required to keep its own excise books.
Excise range: Specifies the excise range in whose area the excise registration is located.
Excise Division
Specifies the excise division in whose area the excise registration is located.
Excise Collectorate
The code of the excise collectorate in whose area the excise registration is located.
Indicator for confirming AED usage
Additional Excise duty Percentage. These are leviable under the additional duties of excise act. These duties are in addition to basic excise duty and special excise duty.
Example
Additional Excise duty is leviable in case of textile products, tobacco and sugar.
Similarly for SED CESS
Number of Items in Excise Invoice
Shows the maximum number of line items that the authorities allow per excise invoice.
Dependencies
This information is used when you create an excise invoice in Sales and Distribution (SD) for factory sales and for other movements.
This information is used to split the transfer postings' items into multiple subcontracting challans.
Excise register set description
Description of the excise registers set.
Partial CENVAT Credit
Indicates that the excise registration ID is allowed to credit only a portion of its input excise duty to its CENVAT account.
Dependencies
When you post a goods receipt, the system splits the input excise duty on the material into its deductible and nondeductible amounts. It posts the deductible duty to the appropriate CENVAT account, and adds the nondeductible duty to the material value.
This information is also shown when you post the vendor's excise invoice.
Maintain Company Code Settings
Use
In this IMG activity, you maintain the data relating to your company codes.
Document Type for CENVAT Postings
It controls, which document type the system uses when making CENVAT postings in Financial Accounting (FI). Here ED is document type for cenvat posting.
Indicator for providing debit account overwriting
Debit Account Overwrite Indicator. X - Indicates debit accounts can be overwritten. Use In excise journal voucher transaction. It provides the flexibility to the user to enter the debit account of his choice depending on the nature of transaction.
Automatic balance Indicator
Excise year start month
The calendar month marking the beginning of the excise year
Use
this start month represents the month for the start of the excise invoice number range. The month 04 is entered here indicating April of the calendar year as the start month for excise invoices. Any change by the Excise authorities regarding start month should be taken care of by an entry in this field and initialization.
Excise invoice selection procedure
Excise invoice selection type. To indicate the method opted by the company for selecting the excise invoice. It can be either earliest or latest invoices that were received.
Number of excise invoices to be selected
indicates the number of excise invoices that needs to be selected in the excise invoice selection.
Days to be considered for excise invoice selection
Number of days from document date for excise invoice selection.
Example
If the value of this field is 20 and today is 28-03-97. The excise
invoice selection will show the related invoices only for the
period 08-03-97 to 28-03-97.
Document type for TDS FI posting
Financial accounting document type for TDS posting.
Document type for FI posting on Utilization
Financial accounting document type for TDS posting.
Indicator for item level excise duty round off
This indicator is to be used for deciding whether Item level excise duty amount rounding off is required during procurement cycle. If marked 'X' then the excise duty amount will be rounded off to the nearest rupee at the Purchase order level. This will not round off the CENVAT credit to be taken. If the duty amount is less than one rupee then no rounding is done
Rounding off of Excise duty for outgoing excise invoice
You can round off the Excise amount to be paid during an outgoing Excise invoice by marking this indicator as 'X'. The rounding is done at the item level for each item where the amount is greater than 1 Rupee.
Immediate Credit on Capital Goods
Instructs the system, when you verify a goods receipt for capital goods, to immediately post half of the input excise duty to the appropriate CENVAT accounts.
The rest is posted the CENVAT on hold account, for use in the following year.
CVD Clearing Account
Specifies which G/L account the system credits when you take a CENVAT credit on countervailing duty in the Incoming Excise Invoices transaction.
Exchange rate type
Key representing a type of exchange rate in the system.
Use
You enter the exchange rate type to store different exchange rates.
Example
You can use the exchange rate type to define a buying rate, selling rate, or average rate for translating foreign currency amounts. You can use the average rate for the currency translation, and the bank buying and selling rates for valuation of foreign currency amounts.
Exchange rate type to be used for Export excise duty converts
When you are creating an Excise invoice for export sales then the exchange rate for duty calculation will be picked up using this Exchange rate type.
Maintain Plant Settings
Use
In this IMG activity, you maintain excise information relating to your plants.
Plant Settings
In this activity, you maintain excise information relating to your plants.
Activities
For each plant:
Specify whether it is a manufacturing site or a depot.
Assign it an excise registration ID.
You can assign the same ID to more than one plant, if required.
Depot
indicates that the plant in question is a depot.
Dependencies
Depots are required to prepare register RG 23D, and follow different procedures for goods receipt and invoice generation.
Number of goods receipt per excise invoice.
Multiple GR for one excise invoice, Single credit
Multiple GR for one excise invoice, multiple credits
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.
Excise Groups
In this activity, you define excise groups. An excise group allows you to maintain a separate set of excise registers and excise accounts. The RG 23A, RG 23C and PLA serial numbers are created for an excise group.
Recommendation
Under normal circumstances, excise authorities require every business to maintain only one set of excise registers and one set of accounts. But through exemption from the authorities, multiple books can be maintained.
If your company has only one set of excise registers, then you need to maintain only one excise group.
Activities
1. Create one excise group for each set of registers that you need to keep.
1. Assign the excise groups to plants.
2. Maintain whether this Excise group is for a depot or not.
3. If you receive only one consignment for an Excise challan then you can leave GR's per EI as blank. If you receive multiple GR's for a given Excise challan and would like to avail multiple credit mark the GRs per EI as 'Multiple GR's for one excise invoice, multiple credit'. Alternatively if you want to avail the credit only after all the goods receipts have been made mark it as ' Multiple GR for one excise invoice, single credit'.
4. If you want to automatically create Excise invoice during Sales cycle at the time of billing the tick the indicator 'Create EI'
5. During depot sales if you do not want to do RG23D selection and posting separately and would like to complete RG23D selection in one step mark the indicator 'RG23D Auto post'. This will post the selected records into RG23D automatically. You cannot cancel the selection later.
6. If the indicator 'Default GR qty' is marked system will default the Excise challan quantity on to the Goods receipt if the Excise invoice number is given in the pop-up.
7. If the indicator 'Folio no creates' is marked system will generate Folio numbers for RG23D during receipt of excise invoice into depot.
8. 'Automatic posting' when ticked will post the Excise invoice other movements automatically along with creation in single step.
9. 'Create Part1 for Block Stock' when marked will create a Part1 during the receipt of material into Blocked stock.
10. 'Create Part1 for STO' when marked will create a Part1 during the receipt of material through inter plant transfers.
11. 'Create Part1 for consumption stock' when marked will create a Part1 during the receipt of material into consumption stock.
Excise Group
Governs which set of excise registers a business transaction will be included in.
Following is the relation between excise group, plant and registration.
Dependencies
In define excise groups in Customizing.
Then, in transactions involving excise duty, for example, when you post a vendor's excise invoice, you specify which excise group you are using. This information tells the system which G/L accounts to post the excise to.
At the end of the period, when you come to prepare your excise registers, you create different sets for each excise group.
Indicates that the plant in question is a depot.
Dependencies
Depots are required to prepare register RG 23D, and follow different procedures for goods receipt and invoice generation.
GR Per Excise Invoice
Multiple GR for one excise invoice , Multiple credit
Multiple GR for one excise invoice , Single Credit
Create Excise Invoice Automatically
Instructs the system to automatically create a Sales and Distribution (SD) excise invoice immediately you create a commercial invoice or a pro forma invoice.
The excise invoice is created in the background.
Dependencies
If you want to make use of this function, you must also define the default plant, excise group, and series groups in Customizing for Sales and Distribution (SD), by choosing Excise Group - Series Group Determination.
RG23D Sales Creation and posting option
RG23D Automatic Option if selected will create Depot excise invoice by posting the selection of excise invoices in single step.
If this is not selected then you need to separately do RG23D selection followed by PGI and then RG23D verification and posting.
If you need automatic posting of RG23D selection then the Post Goods Issue should have been completed before running RG23D selection.
Default excise qty in GR
If this indicator is ticked then while doing Goods Receipt using 'MB01' system will default the excise invoice quantity on to the Goods receipt document.
Folio number for depo
Posting
If this indicator is marked then while creating Excise invoice for other movements system automatically does the Verify and Post. You need not separately Post the excise invoice
Also we can set indicator for creation of part 1 for:
Blocked stock
Stock transport order
Consignment stock
Maintain Series 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.
No account postings for CENVAT in sales cycle
No utilization Flag
If you do not need any CENVAT utilization for an excise invoice but would like to just generate an excise invoice then you need to mark this indicator.
IF the flag is checked then system will create an Excise invoice in the given Series group but there will not be any account postings or Part2 postings.
Immediate Utilization of CENVAT
Specifies that when you create an excise invoice, the system immediately pays the amount from CENVAT and creates the Part II entry. Such invoices will not be listed for fortnightly utilization.
If you have both fortnightly and immediate utilization for the same excise group, the account determination within CIN IMG should point to the ED interim account.
Account determination for immediate payment will be done exactly the same as being done for fortnightly utilization program.
Maintain Excise Duty Indicators
Use
In this IMG activity; you maintain the excise duty indicators.
IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination of Excise Duty >
Select Tax Calculation Procedure
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.
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.
IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination of Excise Duty >
Condition-Based Excise Determination
Use
When you enter a purchasing document, for example, a purchase order, the R/3 System automatically calculates the applicable excise duties using the condition technique.
Features
The standard system comes with two tax calculation procedures. TAXINN is only supports condition-based excise determination, whereas TAXINJ supports condition-based excise determination and formula-based excise determination. Both tax procedures contain condition types that cover all of the excise duties and sales taxes applicable.
Since the exact rates of excise duty can vary on a large number of factors, such as which vendor you purchase a material from, or which chapter ID the vendor stocks the material under, you create condition records for every sort of excise duty.
When you come to enter a purchasing document, the system applies the excise duty at the rates you have entered in the condition records.
Activities
Customizing
IndiaMake for Logistics General, by choosing Taxes on Goodsthe settings in Customizing Basic Excise Duties Using Condition Technique and Movements Account Settings Determination.
These activities include one activity where you define a tax code for condition-based excise determination.
Master Data
Create condition records for all excise duties that apply, and enter the tax code for condition-based excise determination in each.
Day-to-Day Activities
When you enter a purchase order or other purchasing document, enter the tax code for condition-based excise determination in each line item. The system then calculates the excise duties using the condition records you have created.
When the ordered materials arrive, you post the goods receipt and the excise invoice. The system posts the excise duty to the appropriate accounts for deductible input taxes when you enter the excise invoice.
Creating Condition Records for Excise Duty
1. In the command field, enter FV11 and choose .
2. Enter the condition type that you want to create a condition record for and choose .
The Key Combination dialog box appears.
3. Select the combination of objects that you want to create the condition record for.
On the dialog box, Control Code means "chapter ID."
So, for example, to create a condition record for a tax that applies to a combination of country, plant, and chapter ID, select Country/Plant/Control Code.
4. Choose.
5. Enter data as required.
In the Tax Code field, enter the dummy tax code that you have defined.
6. Save the condition record.
Formula-Based Excise Determination
Use
When you execute a business transaction involving materials that are subject to excise duty, the system automatically calculates the duty for you.
Prerequisites
In order for the system to be able to determine which rate of excise duty to apply, you must have maintained all the data on the Maintenance screen, which you can MasterExcise Rate access from the SAP Easy Access screen by choosing Indirect Taxes Excise Rate Maintenance.Data
You maintain the following types of data:
Plant master data
You assign each of your plants an excise duty indicator. You can use the same indicator for all the plants with the same excise status from a legal point of view, such as all those that are in an exempt zone.
See also the information about manufacturers that are only entitled to deduct a certain portion of the duty (see Partial CENVAT Credit).
Vendor master data
For each of your vendors with the same excise status from a legal perspective, you define an excise duty indicator. You must also specify the vendor type for example, whether the vendor is a manufacturer, a depot, or a first-stage dealer. You must also stipulate if the vendor qualifies as a small-scale industry.
For each permutation of plant indicator and vendor indicator, you then create a final excise duty indicator.
Customer master data
similarly, you assign the same excise duty indicator to each of your customers that share the same legal excise status.
Again, for each permutation of plant indicator and customer indicator, you then create a final excise duty indicator.
Material master data
each material is assigned a chapter ID.
Excise tax rate
For every chapter ID and final excise duty indicator, you maintain the rate of excise duty.
If your business only qualifies for partial CENVAT credit, you must customize your system accordingly.
Activities
Let us consider an example to illustrate how the system determines which rate of excise duty to apply to a material. Assume you are posting a sale of ball bearings to a customer. The system automatically determines the rate of excise duty as follows:
1. Looks up the customer master data to see what status you have assigned the customer.
Let's assume you've assigned the customer status 3.
2. Looks up the plant master data to see what status you have assigned the plant.
Similarly, your plant has status 2.
3. The system looks up the table under Excise Indicator for Plant and Customer to see what the final excise duty indictor is for customer status 3 and plant status 2: It is 7.
4. The system determines the chapter ID of the ball bearing for the plant.
Lets assume the chapter ID at plant for the ball bearings is 1000.01.
5. Finally, the system looks up the table under Excise Tax Rate to see what rate of duty applies to chapter ID 1000.01 under status 7.
Define Tax Code for Purchasing Documents
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.
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.
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.
IMG > Logistics - General > Tax on Goods Movement > India > Account Determination
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 sub transaction types, enter the accounts for each sub transaction 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 hld 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 all transactions.
Note
You need not remit the CENVAT to the excise department immediately, so maintain the credit account for transaction type DLFC as an excise duty interim account. This will be set off when you remit the duty.
Config setting needed to be done in order to get the Excise Details Screen in Material Master.
Even though this functionality is available in enterprise version, a small config step has to be made in Screen Sequences for Material Master.
Following document helps you to do this configuration.
Logistics General 1. Go to IMG Define Structure of Data ScreenMaterial Master Configuring the Material master Screen Sequence. for each
2. Select your screen sequence. Usually it would be 21. Select the same and click on Data Screen in the left frame.
3. Once the data screens are exhibited, select data screen no. 15, ie. SSq. 21and Scrn 15, which is Foreign Trade: Import Data. Select the same and click on Subscreens in the left frame.
4. Go to the last sub screen i.e. 21-15-6 - SAPLMGD1- 0001 and select the same. Click on tab view subscreen and ensure that the subscreen is blank.
5. Now in the last sub screen i.e. no.6 you delete SAPLMGD1 0001 and instead add SAPLJ1I_MATERIAL_MASTER and in the screen no. 2205.
6. Save the setting.
7. Create a Material Master and check whether in Screen Foreign Trade Import, Excise related subscreen appears.
Transaction
Action
J1I2
Prepare a sales tax register
J1I3
Create outgoing excise invoices in batches
J1I5
Update the RG 1 and Part I registers
J1IEX
Incoming Excise Invoices (central transaction)
J1IEX_C
Capture an incoming excise invoice (excise clerk)
J1IEX_P
Post an incoming excise invoice (excise supervisor)
J1IF01
Create a subcontracting challan
J1IF11
Change a subcontracting challan
J1IF12
Display a subcontracting challan
J1IF13
Complete, reverse, or recredit a subcontracting challan
J1IFQ
Reconcile quantities for subcontracting challans
J1IFR
List subcontracting challans
J1IH
Make a CENVAT adjustment posting
J1IIN
Create an outgoing excise invoice
J1IJ
Assign excise invoices to a delivery for sales from depots
J1INJV
Adjust withholding tax Item
J1INREP
Reprint a withholding tax certificate for a vendor
J1IQ
Year-End Income Tax Depreciation Report
J1IR
Download register data
J1IS
Process an excise invoice (outgoing) for other movements
J1IU
Process exemption forms
J1IW
Verify and post an incoming excise invoice
J1IX
Create an incoming excise invoice (without reference to purchase order)
J2I8
Transfer excise duty to CENVAT account
J2IU
Remit excise duty fortnightly
J2I9
Monthly CENVAT return
J1IG
Excise invoice entry at depot
J1IGA
Create additional excise entry at depot
J2I5
Extract data for excise registers
J2I6
Print excise registers
Reward points if it useful
Cheers,
Govind.

Internal table in sap script

Hello All ,
I have got a internal table with tracking numbers and I want to print all the numbers in that internal table on sap script.
Please advise.
Thanks
Moderator message: please search for available information before asking.
locked by: Thomas Zloch on Sep 13, 2010 1:09 PM

Hi,
You can create a sub-routine and pass all the table entries in variables and then you can print them.

Payment Program Creation Date and User (is this in any table in SAP R/3)?

Dear Experts!
The treasury guy asked me whether there would be a way to recover the "Payment Program" Creation Date and Created by (User) from Payment Program Executions (F110 transaction).
I searched on the REGU* tables and I didn't find out this information.
Does anybody know whether there is any table where this is recorded?
NOTE: We cannot use the information from "Proposal Log" because the log is removed from the Productive System and only the last 3 (three) days are remaining.
Thanks and Kind Regards,
Daniel Carvalho.

Hello "The Wirtschaftsmann",
Thanks for the reply. However, I need the Creation Date and Creation by of the Proposal / Payment Run steps.
Not sure if this information is available nowadays at SAP. I opened an incident with SAP, let's see what they reply to us.
Regards,
Daniel

How to Access table in SAP

Hi Gurus,
Actually I am new to SAP and was wondering if somebody could tell me how to access a table in SAP where the relavant data is being stored.
e.g. If I want to check table VBAK, what wouldbe the menupath/t-code?
Thank you.
Juhi Singhania

Hi Juhi,
Since you are new to SAP you might want to have this link handy.. it has several useful information including the tables list
http://www.erpgenie.com/abap/tables.htm
http://www.erpgenie.com/saptech/transactions.htm
http://www.sap-img.com/general/find-the-list-of-sap-transaction-codes.htm
http://www.sap-img.com/basis/useful-sap-system-administration-transactions.htm
Thanks
Janani
award points if helpful

Object Status table in SAP R/3

All,
Doe any one know what table in SAP R/3 shows the current value assigned to an
Object ID stored in Table JSTO.
JSTO shows the object ID .
But I am trying to retrive the current user status value assigned to the objectID (for example in VA02)
Thanks,
Mark

Hello "The Wirtschaftsmann",
Thanks for the reply. However, I need the Creation Date and Creation by of the Proposal / Payment Run steps.
Not sure if this information is available nowadays at SAP. I opened an incident with SAP, let's see what they reply to us.
Regards,
Daniel

Protection of Key SAP HR tables in SAP R/3 Upgrade

Hello,
We are upgrading SAP R/3 to ECC 6.0. We have SAP HR, that also needs to be upgraded. Based on this, I have 4 queries, seen below.
1- What are the Pre-reqs and protection of data related activities prior to doing the above upgrade?
2- What are the key tables (in SAP R/3 and SAP HR) to be protected prior to "OR" during a upgrade?
3- What are the key tables (in SAP BW) to be protected prior to "OR" during a upgrade?
4- What is the length of a typical upgrade? (Is there a tool to analyze the expected time duration?)
Thanks for help in advance

Hi Abdul
Please find answers to your questions below .
One should be very careful with the upgrades with HR or BW unlike normal upgrades. Though upgrade do not delete any data but some exceptional tables may be skipped by upgrade and which will not have any data after system is converted to target
1.
Befoe prepare
Check SAP_HR 46C SP level
during Prepare
Add ST-A/PI in upgarde as well so that error will not be in JOB_RDDNTPUR
include all support package of the SAP_HR comp in BIND _PATCH phase
Before upgarde phase :
Backup table T512W(wage types in HR )
Before downtime
backup ST03 data
2. Key table in HR upgrade is T512W
3. check the upgrade guide for BW
4. The best prractice for this kind of project is to have upgrade system (sandbox which is copy of development ) . Try to have similar hardware configuration as PRD
This system will give the timeline for entire upgrade
Upgrade depends on hardware ,database ,size of database ,no of support packs binded in
So matra is " Read Read and Read "
Success !!
Ganesh

Query with information from SD tables

Dears,
I have two questions concerning the creation of a Query which reports information of sales orders and information related to these (tables VBAK, VBAP, KNA1, VBKD).
1. I want to include for example the ship-to-party, but I only find the field in structures, so it would not be able to include... or is there another way to acces this field?
2. I want to include the field KONWA (rate unit). It should appear showing the rate unit depending on the condition type PR00 on item level... Is this possible?
If anybody could help me out on this topics, I would appreciate it a lot!
Thanks in advance,
Dominik Ley
Chile

Hi,
The answer for the first question is If you want to include ship to party at
a)Header level:Simply pass the order number in to VBPA table and fetch for PARVW="WE" having POSNR=000000.By default header details will appear in this table.Take "ADRNR" field contents and pass to ADRC table to fetch the address.
b)Item level:If you want ship to party address at the item level Simply pass the order number in to VBPA table and fetch for PARVW="WE" having POSNR=000010 or 000020 like that what ever is your line item number.If it recognises any change in change at the line item then only the entry will appear in the table.otherwise you cannot find any entry in the table.Take "ADRNR" field contents for the corresponding line item and pass to ADRC table to fetch the address.
Regards,
Mohan.

Need information about Internal Tables

Hi Every one!
I Need some information about Internal tables. Pls help be above the same.
Thanks & with Regards,
Chandra.

Hi..,

Internal tables 
Internal tables provide a means of taking data from a fixed structure and storing it in working memory in ABAP. The data is stored line by line in memory, and each line has the same structure. In ABAP, internal tables fulfill the function of arrays. Since they are dynamic data objects, they save the programmer the task of dynamic memory management in his or her programs. You should use internal tables whenever you want to process a dataset with a fixed structure within a program. A particularly important use for internal tables is for storing and formatting data from a database table within a program. They are also a good way of including very complicated data structures in an ABAP program.
Like all elements in the ABAP type concept, internal tables can exist both as data types and as data objects A data type is the abstract description of an internal table, either in a program or centrally in the ABAP Dictionary, that you use to create a concrete data object. The data type is also an attribute of an existing data object.
Internal Tables as Data Types
Internal tables and structures are the two structured data types in ABAP. The data type of an internal table is fully specified by its line type, key, and table type.
Line type
The line type of an internal table can be any data type. The data type of an internal table is normally a structure. Each component of the structure is a column in the internal table. However, the line type may also be elementary or another internal table.
Key
The key identifies table rows. There are two kinds of key for internal tables - the standard key and a user-defined key. You can specify whether the key should be UNIQUE or NON-UNIQUE. Internal tables with a unique key cannot contain duplicate entries. The uniqueness depends on the table access method.
If a table has a structured line type, its default key consists of all of its non-numerical columns that are not references or themselves internal tables. If a table has an elementary line type, the default key is the entire line. The default key of an internal table whose line type is an internal table, the default key is empty.
The user-defined key can contain any columns of the internal table that are not references or themselves internal tables. Internal tables with a user-defined key are called key tables. When you define the key, the sequence of the key fields is significant. You should remember this, for example, if you intend to sort the table according to the key.

Table type
The table type determines how ABAP will access individual table entries. Internal tables can be divided into three types:
Standard tables have an internal linear index. From a particular size upwards, the indexes of internal tables are administered as trees. In this case, the index administration overhead increases in logarithmic and not linear relation to the number of lines. The system can access records either by using the table index or the key. The response time for key access is proportional to the number of entries in the table. The key of a standard table is always non-unique. You cannot specify a unique key. This means that standard tables can always be filled very quickly, since the system does not have to check whether there are already existing entries.

Sorted tables are always saved sorted by the key. They also have an internal index. The system can access records either by using the table index or the key. The response time for key access is logarithmically proportional to the number of table entries, since the system uses a binary search. The key of a sorted table can be either unique or non-unique. When you define the table, you must specify whether the key is to be unique or not. Standard tables and sorted tables are known generically as index tables.

Hashed tables have no linear index. You can only access a hashed table using its key. The response time is independent of the number of table entries, and is constant, since the system access the table entries using a hash algorithm. The key of a hashed table must be unique. When you define the table, you must specify the key as UNIQUE.

Generic Internal Tables
Unlike other local data types in programs, you do not have to specify the data type of an internal table fully. Instead, you can specify a generic construction, that is, the key or key and line type of an internal table data type may remain unspecified. You can use generic internal tables to specify the types of field symbols and the interface parameters of procedures . You cannot use them to declare data objects.
Internal Tables as Dynamic Data Objects
Data objects that are defined either with the data type of an internal table, or directly as an internal table, are always fully defined in respect of their line type, key and access method. However, the number of lines is not fixed. Thus internal tables are dynamic data objects, since they can contain any number of lines of a particular type. The only restriction on the number of lines an internal table may contain are the limits of your system installation. The maximum memory that can be occupied by an internal table (including its internal administration) is 2 gigabytes. A more realistic figure is up to 500 megabytes. An additional restriction for hashed tables is that they may not contain more than 2 million entries. The line types of internal tables can be any ABAP data types - elementary, structured, or internal tables. The individual lines of an internal table are called table lines or table entries. Each component of a structured line is called a column in the internal table.

Choosing a Table Type
The table type (and particularly the access method) that you will use depends on how the typical internal table operations will be most frequently executed.

Standard tables
This is the most appropriate type if you are going to address the individual table entries using the index. Index access is the quickest possible access. You should fill a standard table by appending lines (ABAP APPEND statement), and read, modify and delete entries by specifying the index (INDEX option with the relevant ABAP command). The access time for a standard table increases in a linear relationship with the number of table entries. If you need key access, standard tables are particularly useful if you can fill and process the table in separate steps. For example, you could fill the table by appending entries, and then sort it. If you use the binary search option with key access, the response time is logarithmically proportional to the number of table entries.
Sorted tables
This is the most appropriate type if you need a table which is sorted as you fill it. You fill sorted tables using the INSERT statement. Entries are inserted according to the sort sequence defined through the table key. Any illegal entries are recognized as soon as you try to add them to the table. The response time for key access is logarithmically proportional to the number of table entries, since the system always uses a binary search. Sorted tables are particularly useful for partially sequential processing in a LOOP if you specify the beginning of the table key in the WHERE condition.

Hashed tables
This is the most appropriate type for any table where the main operation is key access. You cannot access a hashed table using its index. The response time for key access remains constant, regardless of the number of table entries. Like database tables, hashed tables always have a unique key. Hashed tables are useful if you want to construct and use an internal table which resembles a database table or for processing large amounts of data.
regards,
sai ramesh

Cluster tables in SAP

Hi all,
what are the cluster tables in SAP.
and shall we use inner join statment on cluster tables.
regards,
Suresh

HI,
CLUSTER Tables :-Table clusters (clusters) are special table types in the ABAP Dictionary
The data from several tables is stored together in a table pool or table cluster. Tables assigned to a table pool or table cluster are referred to as pooled tables or cluster tables.
Table pool or table cluster should be used exclusively for storing internal control information (screen sequences, program parameters, temporary data, continuous texts such as documentation). Data of commercial relevance is usually stored in transparent tables.
Can check this link for more clarity
http://help.sap.com/saphelp_47x200/helpdata/en/81/415d363640933fe10000009b38f839/frameset.htm
We can't use inner join on clustor table.
To Join cluster table with other table its better use
several select statements.
This one sample code to join cluster table with other transperant table.
In this bseg is a cluster table.
Check it out.
TABLES : bkpf,
 bseg.
 INTERNAL TABLE AND WORK AREA FOR THE FIELDS IN BKPF TABLE *
DATA : BEGIN OF itab_bkpf OCCURS 0,
 bukrs LIKE bkpf-bukrs, "Company Code.
 gjahr LIKE bkpf-gjahr, "Fiscal Year.
 budat LIKE bkpf-budat, "Posting Date in the Document.
 belnr LIKE bkpf-belnr, "Accounting document number.
 blart LIKE bkpf-blart, "Document Type.
 END OF itab_bkpf.
DATA : wa_bkpf LIKE LINE OF itab_bkpf.
 INTERNAL TABLE AND WORK AREA FOR THE FIEDLS IN BSEG TABLE *
DATA : BEGIN OF itab_bseg_debit OCCURS 0,
 bukrs LIKE bseg-bukrs, "Company Code.
 gjahr LIKE bseg-gjahr, "Fiscal Year.
 belnr LIKE bseg-belnr, "Accounting Document Number.
 buzei LIKE bseg-buzei, "Line Item.
 hkont LIKE bseg-hkont, "General Leadger Account.
 shkzg LIKE bseg-shkzg, "Credit/Debit Indicator.
 wrbtr LIKE bseg-wrbtr, "Amount in Document Currency.
 pswsl LIKE bseg-pswsl, "Update Currency for Gen.Ledger
 dmbtr LIKE bseg-dmbtr, "Amount in local currency.
 sgtxt LIKE bseg-sgtxt, "Item Text.
 zuonr LIKE bseg-zuonr, "Assignment Number.
 END OF itab_bseg_debit.
DATA : itab_bseg_credit LIKE STANDARD TABLE OF itab_bseg_debit WITH
 HEADER LINE.
 FINAL OUTPUT INTERNAL TABLE *
DATA : BEGIN OF itab_output OCCURS 0,
 belnr(08),
 bukrs(04),
 budat LIKE bkpf-budat,
 buzei(03),
 hkont(07),
 blart(02),
 shkzg(01),
 wrbtr(08),
 pswsl(05),
 dmbtr(10),
 sgtxt(19),
 zuonr(10),
END OF itab_output.
CONSTANTS : c_debit TYPE c VALUE 'S',
 c_credit TYPE c VALUE 'H'.
 SELECT-OPTIONS *
SELECTION-SCREEN BEGIN OF BLOCK input WITH FRAME TITLE text-t01.
SELECT-OPTIONS : s_bukrs FOR bkpf-bukrs.
PARAMETERS : p_year LIKE bkpf-gjahr.
SELECT-OPTIONS : s_budat FOR bkpf-budat,
 s_dbacct FOR bseg-hkont,
 s_cracct FOR bseg-hkont,
 s_amt FOR bseg-dmbtr.
SELECTION-SCREEN END OF BLOCK input.
 SELECTING RECORDS FROM BKPF TABLE BASED ON THE CONDITION *
SELECT bukrs gjahr budat belnr blart
 FROM bkpf INTO TABLE itab_bkpf
 WHERE bukrs IN s_bukrs AND
 gjahr EQ p_year AND
 budat IN s_budat.
 SELECTING DEBIT LINE ITEMITEMS FROM BSEG FOR THE DOCUMENT *
 NUMBER SELECTED FROM BKPF *
IF NOT itab_bkpf[] IS INITIAL.
SELECT bukrs gjahr belnr buzei
 hkont shkzg wrbtr pswsl
 dmbtr sgtxt zuonr
 FROM bseg INTO TABLE itab_bseg_debit
 FOR ALL ENTRIES IN itab_bkpf
 WHERE bukrs EQ itab_bkpf-bukrs AND
 belnr EQ itab_bkpf-belnr AND
 gjahr EQ itab_bkpf-gjahr AND
 hkont IN s_dbacct AND
 shkzg EQ c_debit AND
 dmbtr IN s_amt.
 SELECTING CREDIT LINE ITEMITEMS FROM BSEG FOR THE DOCUMENT *
 NUMBER SELECTED FROM BKPF *
SELECT bukrs gjahr belnr buzei
 hkont shkzg wrbtr pswsl
 dmbtr sgtxt zuonr
 FROM bseg INTO TABLE itab_bseg_credit
 FOR ALL ENTRIES IN itab_bkpf
 WHERE bukrs EQ itab_bkpf-bukrs AND
 belnr EQ itab_bkpf-belnr AND
 gjahr EQ itab_bkpf-gjahr AND
 hkont IN s_cracct AND
 shkzg EQ c_credit AND
 dmbtr IN s_amt.
ENDIF.
SORT itab_bkpf BY bukrs gjahr belnr.
SORT itab_bseg_credit BY bukrs gjahr belnr.
 LOOPING THE DEBIT ENTRIES
LOOP AT itab_bseg_debit.
READING THE CREDIT ENTRIES WHICH MATCHES WITH HE CURRENT DOC. NUMBER
READ TABLE itab_bseg_credit WITH KEY
 bukrs = itab_bseg_debit-bukrs
 gjahr = itab_bseg_debit-gjahr
 belnr = itab_bseg_debit-belnr BINARY SEARCH.
IF sy-subrc EQ 0.
*READING THE POSTING DATE AND DOCUMENT TYPE FOR THE CURRENT DOUCMENT
 AND APPENDING THE DEBIT AND CREDIT ENTRIES
 READ TABLE itab_bkpf INTO wa_bkpf WITH KEY
 bukrs = itab_bseg_debit-bukrs
 gjahr = itab_bseg_debit-gjahr
 belnr = itab_bseg_debit-belnr BINARY SEARCH.
 itab_output-belnr = itab_bseg_debit-belnr.
 itab_output-bukrs = itab_bseg_debit-bukrs.
 itab_output-budat = wa_bkpf-budat.
 itab_output-buzei = itab_bseg_debit-buzei.
 itab_output-hkont = itab_bseg_debit-hkont.
 itab_output-blart = wa_bkpf-blart.
 itab_output-shkzg = itab_bseg_debit-shkzg.
 itab_output-wrbtr = itab_bseg_debit-wrbtr.
 itab_output-pswsl = itab_bseg_debit-pswsl.
 itab_output-dmbtr = itab_bseg_debit-dmbtr.
 itab_output-sgtxt = itab_bseg_debit-sgtxt.
 itab_output-zuonr = itab_bseg_debit-zuonr.
 APPEND itab_output.
 itab_output-belnr = itab_bseg_credit-belnr.
 itab_output-bukrs = itab_bseg_credit-bukrs.
 itab_output-budat = wa_bkpf-budat.
 itab_output-buzei = itab_bseg_credit-buzei.
 itab_output-hkont = itab_bseg_credit-hkont.
 itab_output-blart = wa_bkpf-blart.
 itab_output-shkzg = itab_bseg_credit-shkzg.
 itab_output-wrbtr = itab_bseg_credit-wrbtr.
 itab_output-pswsl = itab_bseg_credit-pswsl.
 itab_output-dmbtr = itab_bseg_credit-dmbtr.
 itab_output-sgtxt = itab_bseg_credit-sgtxt.
 itab_output-zuonr = itab_bseg_credit-zuonr.
 APPEND itab_output.
ENDIF.
ENDLOOP.
Reward if it helps you.
Thanks.

RSRV - Database Information about InfoProvider Tables

Hello Experts,
I have a question regarding the RSRV. I have run the check "Database Information about InfoProvider Tables " to see number of entries of the dimension tables for a cube. Afterwards I checked directly the dimension table /BIC/D* with the TC SE16. And the number of entries differs. In the RSRV I get around 26 MIO entries, but in the dimension table I get around 25 MIO entries.
Can anybody explain me this ? For my understanding the RSRV result for the dimension table and the number of entries (SE16) should match.
Thx in advance.
AK

hi,
Please refer
SAP Note Number: 941933 - RSRV: Incorrect values for database info on InfoProvider
RSRV - Database information about Infoprovider
Dim tables
Hope this helps.
Regards
Raj

Information related SMMAIN table in sap

Similar Messages

Maybe you are looking for