Reg : CIN Tables

Gurus,
I want to get the list of Tables used in CIN. where can i get ths list?please through some lights into this.
Thanks and Regards,
Senthil.T

Hi,
the easy method ,to get all the CIN tabes in go to T code
SE16-- Click F4 (Function key)
a window appear--Click on the information system
then another screen apeears.
IN that in the Standard selections tab...in the package feild enter the Below value
J1I*
and click OK.
it gives the complete list of Excise tables
hope so it helps
Regads
Anjanna.
Edited by: Shiva Rajanala on May 11, 2009 12:53 PM
Edited by: Shiva Rajanala on May 11, 2009 12:53 PM

Similar Messages

CIN tables mismatch

Hi ,
I have a strange problem. In my CIN table J_1IPART2 , for only GRPO Excise transaction type refence document is missing which is MIGO doc number. But for tables J_1IEXCHDR and J_1IEXCDTL refence document(MIGO) is coming. I am capturing excise in MIGO and posting in J1IEX. Is there any Configuration issue.
Please help me solve the issue.

HI,
I checked at my end in table table J_1IPART2 and found that for GRPO for some document reference is coming as MIGO document number and for some document reference is not coming
but why this so don't know ,have to analyze
Regards
Kailas Ugale

Hi reg CIN

hi to all,
any body help me regarding the CIN.

Dear Brahma,
This is complete details about CIN.This infirmation wll give idea about CIN
Country Version India
A Country Version is designed specifically to cater the business operations of that country over and above the generic SAP system functionalities. It comprises of functionalities degined for the laws and business practices pertaining to the country.
Most of the country-specific functions for India relate to Financials and Logistics.
The main areas are as follows:
Excise duty and the central value-added tax system (CENVAT)
Withholding tax (also known as tax deducted at source)
Sales tax
Maintenance and printing of statutory excise registers
The official help documentation for Country Version India is here.
Links
Operations Home
ERP SD
ERP MM
ERP PP
ERP QM
ERP WM
ERP TM
Forums
ERP General Forum
ERP-MM Forum
ERP-SD Forum
ERP-PP Forum
ERP-MM Forum
In Indian Taxing procedure, Excise Duty plays a vital role in manufacturing scenario's. Excise related configuration is known as CIN configuration. CIN Configuration is a topic in itself.
Here is some information on CIN Configuration. While it may not appear understandable as given below, it will be understood better when you check on screen.
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 Utilisation
Financial accounting document type for TDS posting.
Indicator for item level excise duty round off
This indicator is to be used for deciding whether Item level excise duty amount rounding off is required during procurement cycle. If marked 'X' then the excise duty amount will be rounded off to the nearest rupee at the Purchase order level. This will not round off the CENVAT credit to be taken. If the duty amount is less than one rupee then no rounding is done
Rounding off of Excise duty for outgoing excise invoice
You can round off the Excise amount to be paid during an outgoing Excise invoice by marking this indicator as 'X'. The rounding is done at the item level for each item where the amount is greater than 1 Rupee.
Immediate Credit on Capital Goods
Instructs the system, when you verify a goods receipt for capital goods, to immediately post half of the input excise duty to the appropriate CENVAT accounts.
The rest is posted the CENVAT on hold account, for use in the following year.
CVD Clearing Account
Specifies which G/L account the system credits when you take a CENVAT credit on countervailing duty in the Incoming Excise Invoices transaction.
Exchange rate type
Key representing a type of exchange rate in the system.
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 credit
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 availa the credit only after all the goods receipts have been made mark it as ' Multiple GR for one excise invoice, single credit'.
4. If you want to automatically create Excise invoice during Sales cycle at the time of billing the tick the indicator 'Create EI'
5. During depot sales if you do not want to do RG23D selection and posting separately and would like to complete RG23D selection in one step mark the indicator 'RG23D Auto post'. This will post the selected records into RG23D automatically. You cannot cancel the selection later.
6. If the indicator 'Default GR qty' is marked system will default the Excise challan quantity on to the Goods receipt if the Excise invoice number is given in the pop-up.
7. If the indicator 'Folio no create' is marked system will generate Folio numbers for RG23D during receipt of excise invoice into depot.
8. 'Automatic posting' when ticked will post the Excise invoice other movements automatically along with creation in single step.
9. 'Create Part1 for Block Stock' when marked will create a Part1 during the receipt of material into Blocked stock .
10. 'Create Part1 for STO' when marked will create a Part1 during the receipt of material through inter plant transfers.
11. 'Create Part1 for consumption stock' when marked will create a Part1 during the receipt of material into consumption stock.
Excise Group
Governs which set of excise registers a business transaction will be included in.
Following is the relation between excise group, plant and registration.
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
Make the settings in Customizing Basic? India?for Logistics - General, by choosing Taxes on Goods Movements Account? Excise Duties Using Condition Technique and ...?Settings Determination.
These activities include one activity where you define a tax code for condition-based excise determination.
Master Data
Create condition records for all excise duties that apply, and enter the tax code for condition-based excise determination in each.
Day-to-Day Activities
When you enter a purchase order or other purchasing document, enter the tax code for condition-based excise determination in each line item. The system then calculates the excise duties using the condition records you have created.
When the ordered materials arrive, you post the goods receipt and the excise invoice. The system posts the excise duty to the appropriate accounts for deductible input taxes when you enter the excise invoice.
Creating Condition Records for Excise Duty
1. In the command field, enter FV11 and choose .
2. Enter the condition type that you want to create a condition record for and choose .
The Key Combination dialog box appears.
3. Select the combination of objects that you want to create the condition record for.
On the dialog box, Control Code means "chapter ID."
So, for example, to create a condition record for a tax that applies to a combination of country, plant, and chapter ID, select Country/Plant/Control Code.
4. Choose .
5. Enter data as required.
In the Tax Code field, enter the dummy tax code that you have defined.
6. Save the condition record.
Formula-Based Excise Determination
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 Excise Rate Maintenance screen, which you can Master Data?access from the SAP Easy Access screen by choosing Indirect Taxes Excise Rate Maintenance.?
You maintain the following types of data:
? Plant master data
You assign each of your plants an excise duty indicator. You can use the same indicator for all the plants with the same excise status from a legal point of view, such as all those that are in an exempt zone.
See also the information about manufacturers that are only entitled to deduct a certain portion of the duty (see Partial CENVAT Credit).
? Vendor master data
For each of your vendors with the same excise status from a legal perspective, you define an excise duty indicator. You must also specify the vendor type - for example, whether the vendor is a manufacturer, a depot, or a first-stage dealer. You must also stipulate if the vendor qualifies as a small-scale industry.
For each permutation of plant indicator and vendor indicator, you then create a final excise duty indicator.
? Customer master data
Similarly, you assign the same excise duty indicator to each of your customers that share the same legal excise status.
Again, for each permutation of plant indicator and customer indicator, you then create a final excise duty indicator.
? Material master data
Each material is assigned a chapter ID.
? Excise tax rate
For every chapter ID and final excise duty indicator, you maintain the rate of excise duty.
If your business only qualifies for partial CENVAT credit, you must customize your system accordingly.
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.
Let's 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 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 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 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.
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.
? Material Master ? Logistics General ?1. Go to IMG Define Structure of Data Screen for each?Configuring the Material master Screen Sequence.
2. Select your screen sequence. Usually it would be 21. Select the same and click on Data Screen in the left frame.
3. Once the data screens are exhibited, select data screen no. 15, ie. SSq. 21and Scrn 15, which is "Foreign Trade: Import Data". Select the same and click on 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.
Back to ERP Operation Home.Transaction Codes for India
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
Hope this infirmation helps you
Prem.

Reg : MSEG Table

Hi Friends,
               i've a dobut dobut regarding MSEG table....
               In Mseg table we have Movment Types field (BWART), Now I've two movement types Namingly
               101 - (GR goods receipt)   and 261 (GI for order). Now My Qusetion is .....
               1. How can we link any two MBLNRs with movemnt types 101 &   261 in the MSEG table?
   Regards,
   Kalyan.
Moderator Message: What happened to this one: Reg : Movement Types MSEG Table?.
Edited by: kishan P on Sep 16, 2010 5:52 PM

Hi,
Check MSEG-SMBLN, u will get first material do in SMBLN of 102 material doc.
Regards,
Prashant

Reg : FM tables parametrs

Hi All,
I heard that tables parameters is going to be outdated in the function modules as we can achieve the same functionlaity using the import and export parametrs.
Can anyone give me the some more details reg this?
Thanks in advance.
Regards
Abhilash.

Hi Abhilash,
To some extent what u said is correct.
We are gradually moving from conventional ABAP to Object oriented ABAP. In OOPs concepts we have EXPORTING, IMPORTING and CHANGING parameters(TABLES parameter will be replaced with CHANGING) but not IMPORT and EXPORT).
All new technologies in ABAP like WebDynpro, Netweaver are mostly based on OOPs and linked with JAVA concepts.
Hope i gave u some idea.
Thanks,
Vinod.

Re: CIN Table

Hi Guru,
please Provid the CIN Related Table.
Thanks
Siva

Hello,
Check these:
J_1IEXCHDR Excise invoice header detail
J_1IADDEXC   Additional Excise rate table
J_1IADDRES   Excise Related Address Management
J_1IADDRESS Excise Related Address Management
J_1IARE_ATTRB Excise Bonding: Attributes
J_1IASSVAL   Assessable value table for excise calculat
J_1IBILDET   Billing Type Determination - India
J_1IBOND   Excise Bonding: Bonds/UT-/Running Bond mas
J_1ICALOC   Allocation of materials to assets
J_1ICERTIF   TDS certificate information
J_1ICHIDTX   Text Table for Chapter ID
J_1ICHPTER   Chapter ID Master
J_1ICOMP   Additional company data
J_1ICONDTAX Tax Codes for Excise Duties Using Conditio
J_1ICUS_BILL_TYP Assign Customer Category to Bill Type
J_1IDCLSDET Document class Determination - India
J_1IEICOCU   Excise indicator determination for company
J_1IEICOVE   Excise indicator determination for company
J_1IEWTCALID Calendar for Payment Due date-EWT India
J_1IEWTCALID_N Calendar for Payment Due date-EWT India: S
J_1IEWTCHLN Table for Internal and external Challan no
J_1IEWTDOCKEY Document Types for Extended Withholding Ta
J_1IEWTDTCHLN Document Type for Remittance Challan - Cla
J_1IEWTDTPRV Document Types for TDS Provisions -EWT In
J_1IEWTDUEDATE Tax Due Dates
J_1IEWTECESS Education Cess Codes
J_1IEWTHKONT Table for for TDS provisions Accounts / L
J_1IEWTJV   Document Types for Journal Vouchers
J_1IEWTNO   No range for certificate Printing-EWT Indi
J_1IEWTNUM   INTERNAL NO RANGE FOR CHALLANS- EWT INDIA
J_1IEWTNUMGR Number Groups For Internal Challan Numbers
J_1IEWTNUMGR_1 Number Groups For Internal Challan Numbers
J_1IEWTNUMGR_N Number Groups For Internal Challan Numbers
J_1IEWTPROV Table for TDS provisions
J_1IEWTPROVISACC Maintain entries for accts to be considere
J_1IEWTSURC Surcharge Tax Codes
J_1IEWT_CERT SAPscript Forms/section indicators for E
J_1IEWT_CERTIF Certificate Issued Details-EWT India
J_1IEWT_CERTIF_N Certificate Issued Details-EWT India:SECCO
J_1IEWT_CERTNO Number Ranges for Withholding Tax Certific
J_1IEWT_CERT_N SAPscript Forms/section indicators for EWT
J_1IEWT_COMP Surcharge Calculation Methods
J_1IEWT_CUST Customer certificates ,Challan customizin
J_1IEWT_CUSTV View for Document type for Challan Update-
J_1IEWT_ECESS1 Education Cess Rates
J_1IEWT_ECFLAG Separate Tax code for Ecess
J_1IEWT_HC   Health check for migration to EWT status.
J_1IEWT_MAPEXM Assign Exemption Reasons to Withholding Ta
J_1IEWT_MAPEXMPT Table for Vendor type/exemption indicators
J_1IEWT_MIGRATE Map Classic tax code to EWT Tax type - Tax
J_1IEWT_SURC Maintain Surcharge Calculation Methods
J_1IEWT_SURC1 Surcharge Rates
J_1IEWT_VENTYP Assign Types of Company to Withholding Tax
J_1IEXCACC   Excise Account Assignment table
J_1IEXCDEF   Tax default informations
J_1IEXCDEFN Default Condition Types
J_1IEXCDEP   Excise information of vendor at detail lev
J_1IEXCDTL   Excise invoice line item details
J_1IEXCHDR   Excise invoice header detail
J_1IEXCREF   Delivery document to excise invoice refren
J_1IEXCTAX   Tax calc. - Excise tax rates
J_1IEXESTA   Excise indicator determination for co / cu
J_1IEXGRPS   Excise Groups
J_1IEXMPTCODE VAT Exempted Tax code
J_1IEXSRDET Excise / Series group determination
J_1IEX_CUST_ACT Define Processing Modes Per Transaction
J_1IEX_CUST_FLDS J1IEX: Incoming Invoices field selections
J_1IEX_CUST_REF Define Reference Documents Per Transaction
J_1IFRDTOT   Transaction Table for Forms Tracking-Non S
J_1IFRDTPO   tranasction Table for Forms Tracking for P
J_1IFRDTSO   Transaction table for Forms Tracking for S
J_1IFRMTYP   Form Types
J_1IGRXREF   Goods Receipt to Excise Invoice Coss Refer
J_1IGRXSUB   GR reference to subcontracting challans
J_1IINDCUS   Company Code Settings
J_1IITMDTL   Item Details - for Capital goods and subco
J_1IKONV   Excise recalculated conditions
J_1ILICDTL   Excise Bonding: License detail
J_1ILICHDR   Excise Bonding: License Header
J_1ILICTYPE   Excise Bonding: License type master
J_1IMATEXP   Exceptional materials excise rates
J_1IMESG   Message Control
J_1IMINBAL   Minimum account balances
J_1IMOCOMP   Company and Plant - Excise Additional Data
J_1IMOCUST   Customer Master Excise Additional Data
J_1IMOCUSTEWT Maintain PAN no for Customers -EWT India
J_1IMODDET   Modvat Determination Table (Input Material
J_1IMOVEND   Vendor Master Excise Additional Data
J_1IMOVENDEWT Maintain PAN no for Certificates-EWT India
J_1IMTCHID   Combination of Material Number and Chapter
J_1IMVMT   Movement types versus register relevance
J_1IMVTGRP   Movement type Group for Subcontrcting
J_1INEWJCODE VAT Transition Dummy Jurisdiction Code
J_1INEXCGRP excise group for no range
J_1IPART1   Excise part I detials
J_1IPART2   Excise Part II details
J_1IQEXCISE   Quantity based AED, NCCD and SED
J_1IREGSET   Excise Registrations
J_1IREJMAS   Rejection Codes
J_1IRG1   Excise RG1 details
J_1IRG1RNG   Group table for RG1 - Number Range Object
J_1IRG23D   RG23D register for the depot
J_1IRGSUM   RG23 Summary of receipts and issues
J_1IRSNCODEM Exemption Reason Code; e-Filing India Loca
J_1ISERVC   Service tax details
J_1ISRGRPS   Excise Document Series
J_1ISSIRAT   ssi concessional rates
J_1ISTAPPL   Tax applicability
J_1ISTATECD   State Codes; e-Filing, Localization India
J_1ISTATECDM State Code Mapping; e-Filing India Locali
J_1ISTATECDT State Code Texts; e-Filing India Localiza
J_1ISTRATE   Sales tax set off percentages
J_1ISUBATT   Subcontracting Scenario Attributes
J_1ISUBBYP   Subcontracting Scrap/ Byproduct
J_1ISUBTYP   Subtransaction type text
J_1IT030K   India Tax account determination ( T030K +
J_1IT030K_V   India Tax Account Determination
J_1IT059A   Indicator to mention tax exemption
J_1ITAXDEP   Depreciation computation as per Income Ta
J_1ITAXIND   Excise Tax Indicator
J_1ITCJCMAP   Tax code and Jurisdiction code mapping
J_1ITCJCUPDATE Updatation table for open documents
J_1ITDS   Classic TDS - reference table
J_1ITDSDUE   TDS Payment due date customization
J_1ITDSSEC   TDS Sections
J_1ITDSTXC   TDS - Withholding taxcode and section rel
J_1ITRAN   Transaction code
J_1ITRNACC   Transaction code vs accounts
J_1IUTILIZE   Utilization Determination
J_1IV2ARE_ATTRB Make Settings for ARE-1 Procedure
J_1IVARE_ATTRB Make Settings for ARE-3 Procedure
J_1IVATDATE   Maintain Valid from date of VAT legislatio
J_1IVATDATE_V Maintain Valid from date of VAT legislatio
J_1IVATINVOICE Billing type determination for VAT
J_1IVATREGIO States Under VAT regime
J_1IVCHID   View of Chapter ID and text
J_1IVEXGRP   Help view for Excise groups
J_1IVEXGRPS Excise Group Maintenance
J_1IVFRMTY   Help view for Form type
J_1IVFRTYP   Maintenance view for Form Types
J_1IVREGID   Help View for the register id
J_1IVSRGRP   Help view for serial group
J_1IVT001   Document types for TDS JV
J_1IVTDSDU   Payment due date in TDS
J_1IVTRAN   Help view for the transaction type
J_1IVTTXID   Text maintenance
J_1IVTTXOB   Text object maintenance
J_1IVTXNOR   Excise tax rates - normal
J_1IVTXRAT   Tax rate maintenance
J_1IVTXSPL   Excise tax rates
J_1IV_INVC   Help view for Vendor Excise invoice
J_1IWRKCUS   Plant Settings
J_1I_BCKEXCSUS Customizing table for background capture
J_1I_CUST_CERT Data table for clearing doc on customer ta
J_1I_EWT_RETURN Annual returns - Documemnt View
J_1I_INBDELV INBOUND DELIVERY DETAILS FROM sus
J_1I_SECCODE Section Codes for Extended Withholding Tax
Regards,
Prase

Reg:Tax Table In Purchase Order

Hi All,
     In the Purchase Order Line Item Level We will Give Tax I.e In the Invoice tab We have our required tax codes the the taxes button will enable when we click taxes all the taxes will come my question is coils anybody say in which table all the tax details for a Purchase Order is Stored? i have checked the table KONV
only the Header Conditions is Stored in that table.could you please help me?

Hi Vijetasap,
   i have tried that function module it doesn't return the values thats y i asked the table name, i have attached the code for my reference just correct me where am wrong?
LOOP AT I_EKPO.
    clear taxcom.
    CLEAR : I_KOMV.
    REFRESH : I_KOMV.
    SELECT SINGLE *
       INTO t001
       FROM t001
      WHERE bukrs = ekko-bukrs .
    taxcom-bukrs = i_ekpo-bukrs.
    taxcom-budat = ekko-bedat.
    taxcom-waers = ekko-waers.
    taxcom-kposn = i_ekpo-ebelp.
    taxcom-mwskz = i_ekpo-mwskz.
    taxcom-txjcd = i_ekpo-txjcd.
    taxcom-shkzg = 'H'.
    taxcom-xmwst = 'X'.
      IF I_EKPO-MTART = 'HAWA'.
        taxcom-wrbtr = i_ekpo-kzwi6.
      ELSEIF I_EKPO-MTART = 'ROH'.
        taxcom-wrbtr = i_ekpo-kzwi4.
      ENDIF.
    ELSE.
      taxcom-wrbtr = i_ekpo-zwert.
    ENDIF.
    taxcom-lifnr = ekko-lifnr.
    taxcom-land1 = ekko-lands.
    taxcom-ekorg = ekko-ekorg.
    taxcom-hwaer = t001-waers.
    taxcom-llief = ekko-llief.
    taxcom-bldat = ekko-bedat.
    taxcom-matnr = i_ekpo-ematn.
    taxcom-werks = i_ekpo-werks.
    taxcom-bwtar = i_ekpo-bwtar.
    taxcom-matkl = i_ekpo-matkl.
    taxcom-meins = i_ekpo-meins.
    taxcom-ebeln = i_ekpo-ebeln.
    taxcom-ebelp = i_ekpo-ebelp.
    IF ekko-bstyp EQ bstyp-best.
      taxcom-mglme = i_ekpo-menge.
    ELSE.
      IF ekko-bstyp EQ bstyp-kont AND i_ekpo-abmng GT 0.
        taxcom-mglme = i_ekpo-abmng.
      ELSE.
        taxcom-mglme = i_ekpo-ktmng.
      ENDIF.
    ENDIF.
    IF taxcom-mglme EQ 0.
      taxcom-mglme = 1000.
    ENDIF.
    taxcom-mtart = i_ekpo-mtart.
    IF NOT TAXCOM-mwskz IS INITIAL.
      CALL FUNCTION 'CALCULATE_TAX_ITEM'
      EXPORTING
ANZAHLUNG                 = ' '
   DIALOG                    = ' '
   DISPLAY_ONLY              = ' '
   INKLUSIVE                 = ' '
   I_ANWTYP                  = ' '
   I_DMBTR                   = '0'
   I_MWSTS                   = '0'
          I_TAXCOM                  = taxcom
   PRUEFEN                   = ' '
   RESET                     = ' '
      IMPORTING
   E_NAVFW                   =
          E_TAXCOM                   = taxcom
   E_XSTVR                   =
   NAV_ANTEIL                =
      TABLES
          T_XKOMV                    = i_komv
      EXCEPTIONS
             MWSKZ_NOT_DEFINED          = 1
            MWSKZ_NOT_FOUND             = 2
            MWSKZ_NOT_VALID             = 3
              STEUERBETRAG_FALSCH       = 4
              COUNTRY_NOT_FOUND         = 5
             OTHERS                     = 6
.Note: Am not given Full Code but this is the part where am getting the tax values.

Reg: Fact table and Dimension table in Data Warehousing -

Hi Experts,
I'm not exactly getting the difference between the criteria which decide how to create a Fact table and Dimension table.
This link http://stackoverflow.com/questions/9362854/database-fact-table-and-dimension-table states :
Fact table contains data that can be aggregate.
Measures are aggregated data expressions (e. Sum of costs, Count of calls, ...)
Dimension contains data that is use to generate groups and filters.
This's fine but how does one decide which columns to consider for Fact table and which columns for Dimension table?
Any help is much appreciated.
Pardon me if this's not the correct place for this question. My first question in the new forum.
Thanks and Regards,
Ranit Biswas

ranitB wrote:
But my main doubt was - what is the criteria to differentiate between columns for Fact tables and Dimension tables? How can one decide upon the design?
Columns of a fact table will often be 'scalar' attributes of the 'fact' data item. A dimension table will often be 'compound' attributes of a 'fact'.
Consider employee information. The EMPLOYEE table can be a fact table. It might have scalar attribute columns such as: DATE_HIRED, STATUS, EMPLOYEE_ID, and so on.
Other related information that can't be specified as a single attribute value would often be stored in a 'dimension' table: ADDRESS, PHONE_NUMBER.
Each address requires several columns to define it: ADDRESS1, ADDRESS2, CITY, STATE, ZIP, COUNTRY. And an employee might have several addresses: WORK_ADDRESS, HOME_ADDRESS. That address info would be stored in a 'dimension' table and only the primary key value of the address record would be stored in the EMPLOYEE 'fact' table.
Same with PHONE_NUMBER. Several columns are required to define a phone number and each employee might have several of them. The dimension tables are used to help 'normalize' the data in the employee 'fact' table.
And that EMPLOYEE table might also be a DIMENSION table for other FACT tables. A DEVELOPER table might have an EMPLOYEE_ID column with a value that points to a 'dimension' row in the EMPLOYEE dimension table.

REG: base table/view error

Hi,
I am trying the execute my interface last week and it was running fine but when i try to execute i am getting the following error. can any one tell me what is the cause.
0 : : org.netezza.util.PSQLException: ERROR: Base table/view 'xxxxx' attr 'MILES_DRIVEN' has changed (precision); rebuild view 'xxxx'
Thanks,
GA

Hi Srinivas...
I restricted the view with following selection condition.
JEST INACT NE 'X'.
After that i get like that 2 records.
Example:
EQUNR ESTAT AEDAT STSMA
000000001000000798 E0005 25.03.2004 ZE_00002
000000001000000798 E0007 30.06.2007 ZE_00002
But for that Equip number if i select the OBJNR and check the STATUS in JEST i have only one active record
050 IE000000001000000798 E0005 001
Actually then in the output u should get only record as said by you since u are getting one status value for objnr .....
Actually in our case for a particular objnr we got 6 status values out of these two status values are inactive... so we are left with 4 active status values we took thee four values and checked in text table and we got four values and in this there is one no display so we finally got three values....for a order...
we need to loop over the particular order and store all the status values into a single field ...
this cant be achieved directly through a view i gueesss we need to go for function module...
i has to implement this and i will gett back to you once it is done.....
regards
vamsi

Reg: internal table?

hello friends?
i have one basic doubts,
please clear this things,
what are all the ways we can create the internal table?
how we create internal table using data statement?
how we create internal table using types statement?
what is the difference between these two methods?

FYI..
DATA - Defining an Internal Table
Variants:
1. DATA itab TYPE itabtype [WITH HEADER LINE].
2. DATA itab {TYPE tabkind OF linetype|
              LIKE tabkind OF lineobj}
          WITH [UNIQUE|NON-UNIQUE] keydef
          [INITIAL SIZE n] [WITH HEADER LINE].
3. DATA itab {TYPE TABLE OF linetype|LIKE TABLE OF lineobj}.
4. DATA itab TYPE RANGE OF type.
DATA itab LIKE RANGE OF f.
5. DATA itab [TYPE linetype|LIKE lineobj] OCCURS n
          [WITH HEADER LINE].
6. DATA: BEGIN OF itab OCCURS n,
      END   OF itab [VALID BETWEEN f1 AND f2].
In an ABAP Objects context, a more severe syntax check is performed that in other ABAP areas. See New naming conventions and LIKE references to Dictionary Types not allowed.
Effect
Defines an internal table.
To fill and process internal tables, use the statements INSERT, APPEND, READ TABLE, LOOP, SORT, and so on.
The OCCURS or INITIAL SIZE parameter (OCCURS value) determines the number of lines that are created when the table itself is created. However, the table is extended dynamically on demand. For details, refer to Performance Notes for Internal Tables. The OCCURS value, has no other semantic meaning (apart from one exception in the APPEND SORTED BY statement). If you do not specify an INIT IAL SIZE , the system uses the default value 0.
If you specify WITH HEADER LINE, the table is created with a header line, that is, a field with the same name. It has the same type as the line type of the table.
This addition is not allowed in an ABAP Objects context. See Tables with header line not allowed.
Variant 1
DATA itab TYPE itabtype [WITH HEADER LINE].
Effect
itabtype must be an internal table type that you have already defined using TYPES. The statement creates an internal table in the program with this type.
In general, the type specification for the table object must be complete. The exception to this is a standard table, in which the key definition may be missing. In this case, the system automatically uses a default key.
Example
Creating a hashed table by referring to an existing table type:
TYPES: BEGIN OF STRUC, NAME(10), AGE TYPE I, END OF STRUC,
       HTAB TYPE HASHED TABLE OF STRUC WITH UNIQUE KEY NAME.
DATA : PERSONS TYPE HTAB.
Variant 2
DATA itab {TYPE tabkind OF linetype|LIKE tabkind OF lineobj}           WITH [UNIQUE|NON-UNIQUE] keydef
          [INITIAL SIZE n] [WITH HEADER LINE].
Effect
Creates an internal table in the program with the type tabkind. Since there are no generic field definitions, you cannot use the table types ANY TABLE or INDEX TABLE.
The structure of the table lines is defined by the type linetype if you use a TYPE reference) or by the type of the referred object lineobj (when you use a LIKE reference).
The same rules apply to the UNIQUE and NON-UNIQUE additions in the DATA statement as in a TYPES definition. You may only omit the definition when defining a standard table.
If you do not specify the INITIAL SIZE the system uses a default initial size of 0.
Variant 3
DATA itab {TYPE TABLE OF linetype|LIKE TABLE OF lineobj}.
Effect
This is a shortened form of the definition of a standard table. It corresponds to
   DATA itab {TYPE STANDARD TABLE OF linetype|
              LIKE STANDARD TABLE OF lineobj} WITH DEFAULT KEY.
or the old definition (compare variant 4)
   DATA itab {TYPE linetype|LIKE lineobj} OCCURS 0.
Variant 4
DATA itab TYPE RANGE OF type. DATA itab LIKE RANGE OF f.
Additions:
1. ... INITIAL SIZE n
2. ... WITH HEADER LINE
Effect
Creates an internal table itab with table type STANDARD. The line type is a structure with the following components:
SIGN(1)   TYPE C
OPTION(2) TYPE C
LOW       TYPE type bzw. LIKE f
HIGH      TYPE type bzw. LIKE f
Addition 1
...INITIAL SIZE n
Effect
The INITIAL SIZE specification determines how many table lines are created when the table itself is created. The table is also dynamically expanded as required. For further information, refer to Performance Notes for Internal Tables. The INITIAL SIZE value has no semantic meaning (apart from one exception in the ei APPEND SORTED BY statement). If you do not specify the INITIAL SIZE, the system uses the default value 0.
Addition 2
... WITH HEADER LINE
This addition is not allowed in an ABAP Objects context. See Tables with Header Lines Not Allowed.
Effect
Creates an internal table and a header line for it, that is, a field with the same name as the internal table and the same type as the line type of the internal table.
Variant 5
DATA itab [TYPE linetype|LIKE lineobj] OCCURS n                                        [WITH HEADER LINE].
This variant is not allowed in an ABAP Objects context. See Declaration with OCCURS not allowed.
Effect
This variant exists to ensure compatibility with Release 3.x. If you do not specify a line type, the system uses type C with length 1. Otherwise, the variant is the same as
   DATA itab {TYPE STANDARD TABLE OF linetype|
              LIKE STANDARD TABLE OF lineobj}
             INITIAL SIZE n [WITH HEADER LINE].
Example
TYPES: BEGIN OF LINE_TYPE,
         NAME(20) TYPE C,
         AGE      TYPE I,
       END   OF LINE_TYPE.
DATA: PERSONS    TYPE LINE_TYPE OCCURS 20,
       PERSONS_WA TYPE LINE_TYPE.
PERSONS_WA-NAME = 'Michael'. PERSONS_WA-AGE = 25.
APPEND PERSONS_WA TO PERSONS.
PERSONS_WA-NAME = 'Gabriela'. PERSONS_WA-AGE = 22.
APPEND PERSONS_WA TO PERSONS.
The internal table PERSONS now contains two entries.
Variant 6
DATA: BEGIN OF itab OCCURS n,         ...
      END   OF itab [VALID BETWEEN f1 AND f2].
This variant is not allowed in an ABAP Objects context. See Declaration with OCCURS not allowed.
Effect
Creates an internal table itab with type STANDARD and a header line. The line type consists of the fields between "BEGIN OF itab OCCURS n" and " END OF itab".
Use the VALID BETWEEN f1 AND f2 addition to specify that the components f1 and f2 of the internal table itab contain a line-based validity interval. You can only use this addition in conjunction with the PROVIDE statement.
Example
DATA: BEGIN OF PERSONS OCCURS 20,
        NAME(20),
        AGE TYPE I,
      END   OF PERSONS.
PERSONS-NAME = 'Michael'.
PERSONS-AGE = 25.
APPEND PERSONS.
PERSONS-NAME = 'Gabriela'.
PERSONS-AGE = 22.
APPEND PERSONS.
The internal table consists of two entries. PERSONS also has a header line (work area), which is an interface between the program and the actual table contents.
Additional help
Internal Table Objects
Ramesh

Reg : internal table & Perform statement

hi all
     i have 3 internal tables ,
*     in first internal table i have mark-1 ,*
*     in 2nd internal table i have mark-2 ,*
*     using "PERFORM" i have to add mark 1 & mark 2*
*     and i need to display the total in 3rd internal table.*
*     how to do by using "PERFORM" .*
                Kindly clarify.
with kind regards
vel

Raghupathy is right you just have to write:
porgram code......
perform sum_of_tables tables itab1
                                           itab2
                                           itab3.
program code....
definition of form:
form_sum_of_tables tables itab1
                                      itab2
                                      itab3.
definiton type of witab1, witab2, witab3.
loop itab1 into witab1.
loop itab2 into witab2.
witab3-total = witab1-mark1 plus witab2-mark2.
append witab3 to itab3.
endloop.
endloop.
endform.
It will return itab3 which is sum of itab1 and itab2.

Reg. internal table logic

Hi,
I have an internal table with 5 fields (Vbeln, A, B, C, D ) and records like this:
Record1:
Field vbeln (value is 6000000001), Field A (value is 2006), Field B (value is 1130), Field C (value is initial), Field D (value is initial)
Record1:
Field vbeln (value is 6000000001), Field A (value is initial), Field B (value is initial), Field C (value is 2005), Field D (value is 1134)
Now whenever, Field A and Field B has values, field C and field D are initial and vice versa.
I Want to get all of the field values in just one record like below when the key vbeln is same.:
Field vbeln (value is 6000000001), Field A (value is 2006), Field B (value is 1130), Field C (value is 2005), Field D (value is 1134)
I know I can create another internal table, copy the contents, use the looping logic and achieve the same but wondering if there is any better way of doing the same?
Appreciate your input.
Thanks!

Hi,
You need another internal tables. Please try this.
SORT ITAB1.
ITAB2[] = ITAB1[].
LOOP AT ITAB1.
LOOP AT ITAB2 WHERE ITAB2-VBELN EQ ITAB1-VBELN
                  AND ITAB2-DATE1 NE ITAB1-DATE1
                  AND ITAB2-TIME1 NE ITAB1-TIME1.
    ITAB3-VBELN = ITAB1-VBELN.
    ITAB3-DATE1 = ITAB1-DATE1.
    ITAB3-TIME1 = ITAB1-TIME1.
    ITAB3-DATE2 = ITAB2-DATE2.
    ITAB3-TIME2 = ITAB2-TIME2.
    APPEND ITAB3.
ENDLOOP.
ENDLOOP.
Regards,
Ferry Lianto

REG : KONP Table -A003 Table

hai ,
i have one problem in Purchase Order
In ED, CESS, LST/CST,Surcharge using that respective conditions how can i get that values
in A003 i can pass KAPPL KSCHL. MWSKZ (differs for each line item)
in konv i don't have this conditions..
any body know the any function modules ...or exact tables ...
thanks in advance,
sn

yes,knumh ok but how can i get that KNUMH
B'case KAPPL ok
       KSCHL OK
       MWSKZ differs from item by item
       with out MWSKZ how can i get the KNUMH ..
thanks,
SN

Reg:mm tables

Hi friends,
if u know table name for request for quotation date kindly tell me.
thank u.
regards
Suchithra

They are stored in EKKO and EKPO such that
for RFQ EKKO-BSTYP = 'A'.
reward if answered

Reg PLD Table Export

Hi All,
I have designed the PLD for one company. So i need to use same format for most of the reports like Purchase Order, Sales Invoice etc.. . For that, i woluld like to export RDOC, RITM tables to the New company DB. I am exporting with overwrite option.
Is it ok, or it will cause any other problem?
Pl suggest me to proceed
Regards
Suresh R

Hi,
i think the official way is to use the ReportLayoutsService Object.
have a look at it - you can create xml files from your report and use this to load the xml file in another company.
regards
David

Reg : CIN Tables

Similar Messages

Maybe you are looking for