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

Similar Messages

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.

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 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: Truncate table command in Stored Procedures

Hi All,
I wrote one procedure in which i used 'Truncate Table command' and while compiling I am getting an error. I searched on google but again many queries has been asked there but no suitable solution is there. So please help me in understanding this matter.I will be really obliged of you.
Gursimran Singh

Hi thanks for your reply. The error I am getting is here
PLS-00103: Encountered the symbol "TABLE" when expecting one of the following:
:= . ( @ % ;
The symbol ":= was inserted before "TABLE" to continue.
I appreciate your step to use 'execute immediate 'truncate table table_name';. but the thing is that the system is not allowing my to use TRUNCATE than how come i use the above expression.
Second thing is that there is no error in syntax, everything is fit and fine.
Gursimran

Reg. TABLE MAINTENANCE GENERATOR

hi ,
can anyone pls detail me on TMG.....
and also how to create a t.code for my table...
thanks,
CAPC

To create Table maintenance genetrator,
Go to Utilities->Table maintenance generator
Then Enter Authorisation group(For eg &NC&)
Function group ( You can create function group in SE37. Here in the menu GOTO->Function group-> Create group)
Then you can select either one step or two step. Assign Screen numbers (To assign Screen numbers click on the button 'Find Scr no' . It will propose screen no:s)
Then Create.Save
Table maintenance is created.
To create Tcode, Go to Se93
Enter A tcode name
Create
Select Transaction with parametrs
Enter some transaction text.
Transaction is SM30
Check Skip initial screen
Check Inherit GUI attribtes
gui SUPPORT - Select all check boxes
Under default values, enter
NAME OF SCREEN FIELD       VALUE
VIEWNAME                           ZTABLE NAME
UPDATE                                 X
save it
and try to use the TCode.

Reg internal table and variants

Hi,
Can any tel me
1. how to create internal table dynamically ( i knew its done thru field symbols but i dont know how) ...pls i need a clear example..pls
2.I have got a requirement where i need to display the fields in ouutput based on the variant i choose/select at selection screen.. that means the fields should be varying based on the variant chosen at selection screen..
pls i need a good example for the above 2 queries..plsss
Thanks in ADVANCE
Jay

hi
http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb387a358411d1829f0000e829fbfe/content.htm
Regards
Anuj

Reg value table and check table

Hi Friends,
I have defined a value table(ZVALTAB) for a domain and defined the relation ship between check table(ZCHKTAB) and dependent table(ZDEPTAB). Here value table and check table both are different. My problem is while I am entering the values into check table, it is not restricting the values to enter into check table even those values are not in value table. And while I am entering values into the dependent table through the menu option Utilities->Create entries then also foreign key is not working. But when I use the SM30 then the foreign key is working. So can any body explain me when this value table restrict the values and why the option Utilities->Create entries is not validating the foreign key relation ship.
Sathish Reddy

Hi,
Value Table will just provide you the possible set of values. It won't restrict u for the wrong entries. Moreover whenever u enter entries thru Create entries no user interface is available. The constraints whatever we give is not at all stored in the Data Dictionary. Only the user interface which takes care all about this. Hence it wont restrict you. For this u have to create table maintenance generator for your table. Then it will restrict the values against check table.
Both Value table and Check table will provide u possible set of values. But only the check table will restrict the values.
Hope this will help u.

Reg:mm tables

Similar Messages

Maybe you are looking for