Relation between Mara, CAWN and CABN table.

Can anyone tell how to find Character value and Characteristic Name from Material master record.
I need to generate a report, in the input I will give Material Name and output should be Character_Name and Character value.
How material master(MARA) is linked to CAWN and CABN table?
Thanks,

The first field in AUSP is Object. In this case, the Object is the material number from mara. You have to have the leading zeroes. So if your material number is 12345678, then you have to use 000000000012345678 as the Object in AUSP. From their you should be able to figure out the links to the other tables.
CABN is just the characteristics available in your system. CAWN is just the values for each characteristic in CABN. You can't link to these tables from the material master.
Hope it helps,
Brian

Similar Messages

Creating a master-detail relation between a view and a table

Hi all,
I have a problem with creating a master-detail relation between a database-view with lots of customer data and a small table with per customer a list of entities of our companies who may work for that customer.
Somehow I seem to be unable to create a relation between these two. I can't find where I can make a foreign key using Toplink to implement the relationship. And neither can I get a Viewlink object doing the job using ADF Business Components.
Somebody any suggestions on this problems?
Regards,
Birgit

There is a key relationship between two fields which form the primary key in the main table of the view and two fields in the second table.
I created a viewlink manually, but I still couldn't get the data correct i.e. a form with one record of a customer from the main view and a small table with all entities of our company who can make performances for that customer.
I tried to find a manual or a how-to on this topic but I didn't find anything helpfull yet.
Regards,
Birgit
After a couple more tries, I got the master-detail working. With all the fiddling I am not sure what caused the problem but I think the finally action was checking which fields of the view were marked as primary keys.
Now everthing is up and running.
Birgit
Message was edited by:
user492355

How to get the link between mara, ausp, cawn and cawnt tables

hello ABAPERS
i have got a requiremet in that i have to get the relation .
how to get the link between mara, ausp, cawn and cawnt tables and also type how can we get link between char value and char description in cawn and cawnt tables through ausp and mara tables.
I would be very thankful for ur help in advance.
Thanks & Regards.
soni

Hi,
Sample report using the linkage between tables;
report batch_char no standard page heading
 line-size 132
 line-count 58(1)
 message-id mm.
 Report by Batch Characteristic *
Description : Report by Batch Characteristic *
Declaration for Tables
tables: mara, " Material Master
 mard, " Storage Location Data for Material
 t001w, " Plants/Branches
 t001l, " Storage Locations
 cabn, " Characteristics
 inob. " Link between Internal Number and Object
Declaration for Constants
constants : c_klart like ausp-klart value '023', " Class Type
 c_obtab like inob-obtab value 'MCH1', " Database Table
 c_flag type c value 'X', " Flag
 c_c23 type i value '23', " Ratio
Constants for Ratio Categories
 c_13 type p decimals 2 value '13.00', " For Ratio 13
 c_1499 type p decimals 2 value '14.99', " For Ratio 14.99
 c_15 type p decimals 2 value '15.00', " For Ratio 15
 c_1699 type p decimals 2 value '16.99', " For Ratio 16.99
 c_17 type p decimals 2 value '17.00', " For Ratio 17
 c_1899 type p decimals 2 value '18.99', " For Ratio 18.99
 c_19 type p decimals 2 value '19.00', " For Ratio 19
 c_2099 type p decimals 2 value '20.99', " For Ratio 20.99
 c_21 type p decimals 2 value '21.00', " For Ratio 21
 c_2299 type p decimals 2 value '22.99', " For Ratio 22.99
 c_23 type p decimals 2 value '23.00', " For Ratio 23
 c_g23(4) type c value '>=23', " For Ratio >=23
 c_ratio(5) value 'RATIO', " For Ratio
Constants for Storing Selected item field information
 c_cursor1(15) value 'I_OUTPUT1-MEINS', " For Selected Base
 " Unit of Measure
 c_cursor2(15) value 'I_OUTPUT1-MATNR', " For Selected Base
 " Material Number
 c_cursor3(15) value 'I_OUTPUT1-MAKTX', " For Selected Base
 " Material Des.
 c_cursor4(15) value 'I_OUTPUT1-CLABS', "For Selected Base
 " Stock Value
 c_cursor5(15) value 'I_OUTPUT1-ATFLV', " For Selected Base
 " Char.Value (Ratio)
 c_cursor6(5) value 'C_G23'.
Declaration for Global Variables
data : g_exit type c, " Flag
 g_clabs1(16) type c, " Quantity
 g_clabs(18) type c, " Quantity
 g_cursor(15) type c, " Cursor field name
 g_matnr type mara-matnr, " Material Number
 g_werks type mchb-werks, " Plant
 g_atinn(30) type c. " Character.
Declaration for Internal tables
Internal table to hold Batch Stock data
data : begin of i_mchb occurs 0,
 matnr like mchb-matnr, " Material Number
 werks like mchb-werks, " Plant
 lgort like mchb-lgort, " Storage Location
 charg like mchb-charg, " Batch Number
 clabs like mchb-clabs, " Stock Value
 meins like mara-meins, " Unit of measure
 atflo like ausp-atflv, " Char.Value (Ratio)
 atflv like ausp-atflv, " Char.Value (Ratio)
 end of i_mchb.
Internal table to hold Secondary List data
data : begin of i_mchb1 occurs 0,
 werks like mchb-werks, " Plant
 matnr like mchb-matnr, " Material Number
 lgort like mchb-lgort, " Storage Location
 charg like mchb-charg, " Batch Number
 atinn like ausp-atinn, " Char.Value
 clabs like mchb-clabs, " Stock Value
 atflo like ausp-atflv, " Char.Value (Ratio)
 atflv like ausp-atflv, " Char.Value (Ratio)
 end of i_mchb1.
Internal table to get the Plant Name
data : begin of i_plant occurs 0,
 werks like t001w-werks, " Plant
 name1 like t001w-name1, " Name
 end of i_plant.
Internal table to get the Material Description
data : begin of i_makt occurs 0,
 matnr like makt-matnr, " Material
 maktx like makt-maktx, " Description
 end of i_makt.
Internal table to hold AUSP data
data : begin of i_ausp occurs 0,
 objek like ausp-objek, " Object No
 atinn like cabn-atinn, " Characteric value
 atflv like ausp-atflv, " Characteristic Value
 end of i_ausp.
Internal table to hold output data
data : begin of i_output occurs 0,
 atinn like cabn-atinn, " Characteric value
 werks like mchb-werks, " Plant
 matnr like mchb-matnr, " Material Number
 atnam like cabn-atnam, " Characteristic
 atflv like ausp-atflv, " Char.Value (Ratio)
 name1 like t001w-name1, " Plant Description
 maktx like makt-maktx, " Material Description
 clabs like mchb-clabs, " Stock Value
 meins like mara-meins, " Base Unit of Measure
 end of i_output.
Internal table to hold final Output data
data : begin of i_output1 occurs 0,
 atinn like cabn-atinn, " Characteric value
 werks like mchb-werks, " Plant
 matnr like mchb-matnr, " Material Number
 atnam like cabn-atnam, " Characteristic
 atflv(32) type c, " Char.Value (Ratio)
 name1 like t001w-name1, " Plant Description
 maktx like makt-maktx, " Material Description
 clabs like mchb-clabs, " Stock Value
 meins like mara-meins, " Base Unit of Measure
 end of i_output1.
 Selection screen
selection-screen begin of block b1 with frame title text-001.
select-options: s_werks for t001w-werks obligatory, " Plant
 s_lgort for t001l-lgort, " Stor.Location
 s_matnr for mara-matnr obligatory, " Material No
 s_atinn for cabn-atinn. " Character.
selection-screen end of block b1.
At selection screen
at selection-screen.
Validation of Selection Screen Fields
perform validate_screen.
Start of selection
start-of-selection.
Get the Material and Batch Stock data from MARA and MCHB Tables
perform get_mat_stock_data.
Get the Material Group Text and Plant Name from T023T and T001W Tables
perform get_plant_grp_data.
Append the data into final Output Internal Table after getting the
Characteristic Values data from INOB and AUSP Tables
perform append_final_data.
Processing if the Characteristics contain 'RATIO'
perform collect_ratio.
End-of-Page
end-of-page.
write /1(125) sy-uline.
End of selection
end-of-selection.
if g_exit <> c_flag.
Display the Report Output data
 perform display_report.
endif.
Top-of-Page
top-of-page.
Write the Report and Column Headings
perform get_headings.
at line-selection
at line-selection.
if sy-lsind = 1.
 perform display_batch.
endif.
Top of page during line-selection
top-of-page during line-selection.
perform heading_seclist.
 Form validate_screen
Validation of Selection Screen fields
form validate_screen.
Validation of Plant
clear t001w.
if not s_werks[] is initial.
 select werks
 into t001w-werks
 from t001w
 up to 1 rows
 where werks in s_werks.
 endselect.
 if sy-subrc <> 0.
 message e899 with 'Enter Valid Plant'(002).
 endif.
endif.
Validation of Material Number
clear mara.
if not s_matnr[] is initial.
 select matnr
 into mara-matnr
 from mara
 up to 1 rows
 where matnr in s_matnr.
 endselect.
 if sy-subrc <> 0.
 message e899 with 'Enter Valid Material'(003).
 endif.
endif.
Validation of Storage Location
clear t001l.
if not s_lgort[] is initial.
 select lgort
 into t001l-lgort
 from t001l
 up to 1 rows
 where lgort in s_lgort.
 endselect.
 if sy-subrc <> 0.
 message e899 with 'Enter Valid Storage Location'(004).
 endif.
endif.
Validation of Characteristic Value
clear cabn.
if not s_atinn[] is initial.
 select atinn
 into cabn-atinn
 from cabn
 up to 1 rows
 where atinn in s_atinn.
 endselect.
 if sy-subrc <> 0.
 message e899 with 'Enter Valid Characteristic Value'(005).
 endif.
endif.
Validation of Plant, Material and Storage Location
clear mard.
select matnr werks lgort
 into (mard-matnr, mard-werks, mard-lgort)
 from mard
 up to 1 rows
 where matnr in s_matnr and
 werks in s_werks and
 lgort in s_lgort.
endselect.
if sy-subrc <> 0.
 message e899 with 'No Data found for the Selection Criteria'(006).
endif.
endform. "validate_screen
*& Form get_headings
Write the Report and Column Headings
form get_headings.
data: l_repid type sy-repid.
l_repid = sy-repid.
call function 'Y_STANDARD_HEADING'
 exporting
 repid = l_repid
 heading1 = sy-title.
write:/1(125) sy-uline.
format color col_heading on.
write : /1 sy-vline, 2(18) 'Material Number'(008) centered,
 20 sy-vline, 21(40) 'Material Description'(011) centered,
 61 sy-vline, 62(22) 'Ratio'(009) centered,
 84 sy-vline, 85(18) 'Quantity'(010) centered,
 103 sy-vline, 104(20) 'Base Unit of Measure'(015) centered,
 125 sy-vline.
write:/1(125) sy-uline.
format color off.
endform. "get_headings
*& Form get_mat_stock_data
Get the Material and Batch Stock data from MARA and MCHB Tables
form get_mat_stock_data.
clear: i_mchb,i_output, i_output1.
refresh: i_mchb,i_output, i_output1.
select a~matnr " Material Number
 b~werks " Plant
 b~lgort " Storage Location
 b~charg " Batch Number
 b~clabs " Stock Value
 a~meins " Base Unit of Measure
 into table i_mchb
 from mara as a inner join mchb as b
 on amatnr eq bmatnr
 where b~matnr in s_matnr and
 b~werks in s_werks and
 b~lgort in s_lgort.
if sy-subrc <> 0.
 g_exit = c_flag.
 message s899 with 'No Data found for the Selection Criteria'(006).
 stop.
endif.
sort i_mchb by matnr werks lgort charg.
endform. " get_mat_stock_data
*& Form get_plant_grp_data
Get the Material Group Text and Plant Name from T023T and T001W
form get_plant_grp_data.
if not i_mchb[] is initial.
Get the Plant Description from t001w Table
 clear i_plant.
 refresh i_plant.
 select werks " Plant
 name1 " Name
 into table i_plant
 from t001w
 for all entries in i_mchb
 where werks = i_mchb-werks.
Get the Material Description from MAKT Table
 clear i_makt.
 refresh i_makt.
 select matnr " Material number
 maktx " Material Description
 into table i_makt
 from makt
 for all entries in i_mchb
 where matnr = i_mchb-matnr and
 spras = sy-langu.
 sort i_plant by werks.
 delete adjacent duplicates from i_plant comparing werks.
 sort i_makt by matnr.
 delete adjacent duplicates from i_makt comparing matnr.
endif.
endform. "form get_plant_grp_data.
*& Form append_final_data
Append the data into final Internal Table
form append_final_data.
data : l_matbatch(28),
 l_tabix like sy-tabix.
if not i_mchb[] is initial.
 loop at i_mchb.
 l_tabix = sy-tabix.
 clear l_matbatch.
 concatenate i_mchb-matnr i_mchb-charg into l_matbatch.
 move-corresponding i_mchb to i_output.
Get the Plant Description from i_plant Table
 read table i_plant with key werks = i_mchb-werks binary search.
 if sy-subrc = 0.
 i_output-name1 = i_plant-name1.
 endif.
Get the Material Description from i_makt Table
 read table i_makt with key matnr = i_mchb-matnr binary search.
 if sy-subrc = 0.
 i_output-maktx = i_makt-maktx.
 endif.
Get the Characteristic Values data from INOB and AUSP Tables
 clear inob.
 select single cuobj from inob
 into inob-cuobj
 where klart = c_klart and
 obtab = c_obtab and
 objek = l_matbatch.
 if sy-subrc = 0.
 select objek
 atinn
 atflv
 from ausp
 into table i_ausp
 where objek = inob-cuobj and
 atinn in s_atinn and
 klart = c_klart.
 sort i_ausp by objek atinn.
 loop at i_ausp.
 clear cabn.
 select single atinn atnam from cabn
 into (cabn-atinn,cabn-atnam)
 where atinn = i_ausp-atinn.
 if sy-subrc = 0.
If the ratio value is between 13-14.99, display 13
 if cabn-atnam cs c_ratio.
 if i_ausp-atflv between c_13 and c_1499.
 i_mchb-atflo = i_ausp-atflv.
 i_mchb-atflv = c_13.
If the ratio value is between 15-16.99, display 15
 elseif i_ausp-atflv between c_15 and c_1699.
 i_mchb-atflo = i_ausp-atflv.
 i_mchb-atflv = c_15.
If the ratio value is between 17-18.99, display 17
 elseif i_ausp-atflv between c_17 and c_1899.
 i_mchb-atflo = i_ausp-atflv.
 i_mchb-atflv = c_17.
If the ratio value is between 19-20.99, display 19
 elseif i_ausp-atflv between c_19 and c_2099.
 i_mchb-atflo = i_ausp-atflv.
 i_mchb-atflv = c_19.
If the ratio value is between 21-22.99, display 21
 elseif i_ausp-atflv between c_21 and c_2299.
 i_mchb-atflo = i_ausp-atflv.
 i_mchb-atflv = c_21.
If the ratio value is greater than or equal to 23, display 23
 elseif i_ausp-atflv >= c_23.
 i_mchb-atflo = i_ausp-atflv.
 i_mchb-atflv = c_23.
 endif. " Condition for RATIO values
 else. " If characteristic does contain RATIO
 i_mchb-atflv = i_ausp-atflv.
 endif.
 i_output-atinn = cabn-atinn.
 i_output-atnam = cabn-atnam.
 i_output-atflv = i_ausp-atflv.
 i_mchb1-matnr = i_mchb-matnr.
 i_mchb1-werks = i_mchb-werks.
 i_mchb1-lgort = i_mchb-lgort.
 i_mchb1-charg = i_mchb-charg.
 i_mchb1-clabs = i_mchb-clabs.
 i_mchb1-atinn = i_ausp-atinn.
 i_mchb1-atflo = i_mchb-atflv.
 i_mchb1-atflv = i_ausp-atflv.
 append : i_output, i_mchb1.
 clear i_mchb1.
 modify i_mchb index l_tabix transporting atflo atflv .
 endif.
 endloop.
 endif.
 endloop.
endif.
Checking whether the table is filled or not
if not i_output[] is initial.
 sort i_output by atinn werks matnr atflv.
else.
 g_exit = c_flag.
 message s899 with 'No Data found for the Selection Criteria'(006).
endif.
Delete the records where RATIO is less than 13.
delete i_output where atnam cs c_ratio and atflv lt c_13.
endform. "append_final_data
*& Form display_report
Display the Report Output data
form display_report.
data: l_tabix like sy-tabix.
loop at i_output1.
 l_tabix = sy-tabix.
At new Characteristic
 at new atinn.
 read table i_output1 index l_tabix.
 format color 1 intensified on.
 write: /1 sy-vline, 2(20) 'Characteristic Name:'(007),
 23(40) i_output1-atnam,
 125 sy-vline.
 format color off.
 format color 4 intensified on.
 write: /1 sy-vline, 2(20) 'Plant Name :'(022),
 23(4) i_output1-werks, 29(30) i_output1-name1,
 125 sy-vline.
 format color off.
 write /1(125) sy-uline.
 endat.
 clear: g_clabs, g_clabs1.
 format color col_normal.
 write :/1 sy-vline, 2(18) i_output1-matnr,
 20 sy-vline, 21(40) i_output1-maktx,
 61 sy-vline.
 if i_output1-atflv = c_c23.
 write: 62(22) c_g23 centered.
 else.
 shift i_output1-atflv left deleting leading space.
 write: 62(22) i_output1-atflv centered.
 endif.
 write: 84 sy-vline,
 103 sy-vline,
 110(5) i_output1-meins.
If the quantity value is negative
 if i_output1-clabs ge 0.
 write: 85(18) i_output1-clabs unit i_mchb-meins,
 125 sy-vline.
 else.
 i_output1-clabs = - i_output1-clabs.
 write i_output1-clabs unit i_mchb-meins to g_clabs1.
 condense g_clabs1.
 concatenate '(' g_clabs1 ')' into g_clabs separated by space.
 write: 85(18) g_clabs right-justified,
 125 sy-vline.
 endif.
 format color off.
 hide : i_output1.
 new-line.
At end of material
 at end of matnr.
 sum.
 move : i_output1-matnr to g_matnr.
 format color 3 intensified on.
 write /1(125) sy-uline.
 write :/1 sy-vline, 2(25) 'Total for Material :'(012),
 28(18) g_matnr.
 if i_output1-clabs ge 0.
 write: 85(18) i_output1-clabs unit i_mchb-meins,
 125 sy-vline.
 else.
 i_output1-clabs = - i_output1-clabs.
 write i_output1-clabs unit i_mchb-meins to g_clabs1.
 condense g_clabs1.
 concatenate '(' g_clabs1 ')' into g_clabs separated by space.
 write: 85(18) g_clabs right-justified,
 125 sy-vline.
 endif.
 write: 125 sy-vline.
 format color off.
 write /1(125) sy-uline.
 endat.
At end of plant
 at end of werks.
 sum.
 move : i_output1-werks to g_werks.
 format color 3 intensified off.
 write :/1 sy-vline, 2(25) 'Total for Plant :'(013),
 28(4) g_werks.
 if i_output1-clabs ge 0.
 write: 85(18) i_output1-clabs unit i_mchb-meins,
 125 sy-vline.
 else.
 i_output1-clabs = - i_output1-clabs.
 write i_output1-clabs unit i_mchb-meins to g_clabs1.
 condense g_clabs1.
 concatenate '(' g_clabs1 ')' into g_clabs separated by space.
 write: 85(18) g_clabs right-justified,
 125 sy-vline.
 endif.
 format color off.
 write /1(125) sy-uline.
 endat.
At end of characteristic
 at end of atinn.
 read table i_output1 index l_tabix.
 sum.
 format color 3 intensified on.
 write :/1 sy-vline, 2(25) 'Total for Characteristic:'(014),
 28(25) i_output1-atnam.
 if i_output1-clabs ge 0.
 write: 85(18) i_output1-clabs unit i_mchb-meins,
 125 sy-vline.
 else.
 i_output1-clabs = - i_output1-clabs.
 write i_output1-clabs unit i_mchb-meins to g_clabs1.
 condense g_clabs1.
 concatenate '(' g_clabs1 ')' into g_clabs separated by space.
 write: 85(18) g_clabs right-justified,
 125 sy-vline.
 endif.
 format color off.
 write /1(125) sy-uline.
 endat.
endloop.
endform. " display_report
*& Form DISPLAY_BATCH
 Display the batch details for the seclected material *
form display_batch.
Get the batch details for the selected material
get cursor field g_cursor.
if g_cursor = c_cursor1 or
 g_cursor = c_cursor2 or
 g_cursor = c_cursor3 or
 g_cursor = c_cursor4 or
 g_cursor = c_cursor5 or
 g_cursor = c_cursor6.
 format color 3.
 write: /1 sy-vline,
 2(17) 'Material Number :'(020),
 20(17) i_output1-matnr,
 94 sy-vline.
 format color off.
 write /1(94) sy-uline.
 loop at i_mchb1 where matnr = i_output1-matnr and
 atinn = i_output1-atinn and
 atflo = i_output1-atflv.
 format color col_normal.
 shift i_mchb1-charg left deleting leading '0'.
 write :/1 sy-vline, 2(16) i_mchb1-lgort centered,
 18 sy-vline, 19(17) i_mchb1-charg centered,
 36 sy-vline.
 if i_output1-atnam cs c_ratio.
 write: 37(29) i_mchb1-atflv
 exponent 0 decimals 2 centered.
 else.
 write : 37(29) i_mchb1-atflv
 exponent 0 decimals 0 centered.
 endif.
 write : 66 sy-vline, 67(27) i_mchb1-clabs unit i_mchb-meins,
 94 sy-vline.
 format color off.
 endloop.
 write /1(94) sy-uline.
else.
 message s899 with 'Invalid cursor position'(016).
 exit.
endif.
endform. " DISPLAY_BATCH
*& Form HEADING_SECLIST
 Write the Column Headings for Interactive Report
form heading_seclist.
write /1(94) sy-uline.
format color col_heading on.
write :/1 sy-vline, 2(16) 'Storage Location'(021),
 18 sy-vline, 19(17) 'Batch Number'(017) centered,
 36 sy-vline, 37(29) 'Characteristic Value'(018) centered,
 66 sy-vline, 67(27) 'Quantity'(019) centered,
 94 sy-vline.
write /1(94) sy-uline.
format color off.
endform. " HEADING_SECLIST
*& Form COLLECT_RATIO
 Display the Characteristic ratio data
form collect_ratio.
loop at i_output.
 clear g_atinn.
 i_output1-atinn = i_output-atinn.
 i_output1-atnam = i_output-atnam .
 i_output1-werks = i_output-werks.
 i_output1-name1 = i_output-name1.
 i_output1-matnr = i_output-matnr.
 i_output1-maktx = i_output-maktx.
 i_output1-clabs = i_output-clabs.
 i_output1-meins = i_output-meins.
 call function 'CONVERSION_EXIT_ATINN_OUTPUT'
 exporting
 input = i_output-atinn
 importing
 output = g_atinn.
 if g_atinn cs c_ratio.
If the ratio value is between 13-14.99, display 13
 if i_output-atflv between c_13 and c_1499.
 i_output1-atflv = c_13.
If the ratio value is between 15-16.99, display 15
 elseif i_output-atflv between c_15 and c_1699.
 i_output1-atflv = c_15.
If the ratio value is between 17-18.99, display 17
 elseif i_output-atflv between c_17 and c_1899.
 i_output1-atflv = c_17.
If the ratio value is between 19-20.99, display 19
 elseif i_output-atflv between c_19 and c_2099.
 i_output1-atflv = c_19.
If the ratio value is between 21-22.99, display 21
 elseif i_output-atflv between c_21 and c_2299.
 i_output1-atflv = c_21.
If the ratio value is greater than or equal to 23, display 23
 elseif i_output-atflv >= c_23.
 i_output1-atflv = c_23.
 endif.
 write i_output1-atflv to i_output1-atflv .
 else.
 write i_output-atflv to i_output1-atflv exponent 0 decimals 0.
 endif.
 collect i_output1.
 clear i_output1.
endloop.
sort i_output1 by atinn werks matnr atflv.
endform. " COLLECT_RATIO
Reward if useful..
Regards,
Anji

How to get the link between MCH1, AUSP, CAWN and CAWNT tables

Hi,
Can anyone let me know how to get the link between MCH1, AUSP, CAWN and CAWNT tables as I want to get the description (CAWNT-ATWTB) for a particular Batch (MCH1-CHARG).
Thanks & Regards,
Kumar

Hi,
Can anyone let me know how to get the link between MCH1, AUSP, CAWN and CAWNT tables as I want to get the description (CAWNT-ATWTB) for a particular Batch (MCH1-CHARG).
Thanks & Regards,
Kumar

Relation between different GUID and tables in RPM

Hi All,
can you tell me the relation between different GUID and tables in RPM. Many thanks.
Regards,
J B

Hi Deepesh,
Try the foll. join :
    SELECT fragment_guid INTO (some internal Table)
         FROM comm_pr_frg_rod
         WHERE product_guid = (your product guid list)
This should give u a complete match of the products.
Hope this helps.
Regards,
Raviraj

Is there any table for relation between batch number and valuation type ?

hi,
I would like to know where i can find relation between batch number and valuation type ?
thank you and Best regards
Fernand

Hello
MCHA

Where can I find the relation between company code and plant?

where can I find the relation between company code and plant?
I need to the list of plants under a company code.
Which table?

yes,wayne weng .What you said is right.
Thank you very much!
My MSN:[email protected]

Relation between GL Account and Invoice?

Hi Experts,
I am working with the FI reports for the first time and I do not have any idea on FI functional flow. I have some basic questions like
What is the Relation between GL Account and Invoice?
When will an Invoice be posted into BKPF, BSEG, BSAD, BSID, BSAK and BSIK? Is there any field in these tables which gives the Invoice number against which a GL Account is created?
For example if I want to calculate " no of vendor invoices without PO how can I do that"? How can I know what are vendor invoices created against a PO or without PO?
Thanks for any help in advance and I am bound to reward points.
Sri

What is the Relation between GL Account and Invoice?
SAP's Glossary for GL Account is
"A structure that records value movements in a company code and represents the G/L account items in a chart of accounts.
A G/L account has transaction figures that record changes to the account during a posting period. These figures are totals that are used for G/L reporting."
In accountancy, an account is a label used for recording and reporting a quantity of almost anything. For example when a company pays salary to its staff, They debit Salary account. This is to identify what is the nature of an expense.
An invoice is a message to the buyer of goods or services that contains, among other things, Name of the goods or services, Quantity sent, & Remuneration due.
Invoice is also a SD document used to charge a customer for a delivery of goods or for services rendered.
When will an Invoice be posted into BKPF, BSEG, BSAD, BSID, BSAK and BSIK? Is there any field in these tables which gives the Invoice number against which a GL Account is created?
If it were a vendor invoice. (i.e you purchase items or service and recieve invoice)
Invoice get posted to the tables once someone makes a Logistics Invoice verification through t-code MIRO etc. The teble RBKP gets the first posting.
If it were your own invoice to your customers, then VBAK and VBAP get the posting. The connectivity of tables are available in http://www.erpgenie.com/abap/tables.htm As far as SAP is concerned an invoice is a document, so you can only trace invoice as a document number, field name is usually BELNR. Even if a vendor invoice arrive, an internal invoice number is generated where the vendor invoice is entered only as a reference field. This is because, each vendor can have inovices of different size and pattern.
How can I know what are vendor invoices created against a PO or without PO?
For a purchase order you can find in table EKBE for BEWTP = Q any invoice document.

Difference between Data staging and Dimension Table ?

Difference between Data staging and Dimension Table ?

Data Staging:
Data extraction and transformation is done here.
Meaning that, if we have source data in flat file, we extract it and load into staging tables, we take care of nulls, we change datetime format etc.. and after such cleansing/transformation at then end, load it to Dim/Fact tables
Pros: Makes process simpler and easy and also we can keep track of data as we have data in staging
Cons: Staging tables need space hence need memory space
Dimension Table:
tables which describes/stores the attribute about specific objects
Below is star schema which has dimension storing information related to Product, Customer etc..
-Vaibhav Chaudhari

Relation between Business Partner and User

Hi everyone.
Where can i found the relation between the business partnes and user in the tables of CRM application.
Thanks.
Mauricio N.

But in the database where is located this data, which is the table in the database that has the relation between business partners and users???
Thanks,
Mauricio N.

Relation between server's and runtime Data Model?

I am working on a project utilizing the MVC architecture.
After some doubts, I decided to create one DataModel class for each table of the server's normalized database and create the necessary relations at runtime and not in SQL prior to download.
The database is only a few MB and I need the flexibility.
I would appreciate some links to theoretical material regarding the relation between the runtime and the server's DB data model.
Thanks,
David

Hi Anirudh/Deepa,
As You said first I have created Outbound Connection Pool for DB adapter and given eis/DB/HRDBDataSource as JNDI name. It asked to save the file Plan.xml and i saved it in Oracle_soa1/Soa/Plan.xml
Next I created datasorce with JNDI name jdbc/HRDBDataSource and provided all credentials.
For AQ also i created connectionpool with JNDI name eis/AQ/MyAQ . Here also it asked to save the Plan.xml and Isaved it in Oracle_soa1/Soa/applications/Plan.xml
In Jdev while configuring AQ adapter I have selected the database [for this only i created connection pool and datasource] and given the JNDI Name as eis/AQ/MyAQ . (I tried with and without giving datasorce value jdbc/HRDBDataSource in AQ adapter )
Still I am getting the below error.
*Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'Enqueue' failed due to: JCA Binding Component connection issue. JCA Binding Component is unable to create an outbound JCA (CCI) connection. Queue:EnQueue [ Enqueue_ptt::Enqueue(EMP_MESSAGE_TYPE) ] : The JCA Binding Component was unable to establish an outbound JCA CCI connection due to the following issue: No suitable driver found for . ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. No suitable driver found for 0*
Please guide me
Regards
PavanKumar.M

Relation between Co document and FI Document

Hi sap Gurus,
Can someone tell how is the best way to get the Co document from the FI document? I need a good relation between then.
I saw table cobk but that table hasn´t the the Fi document.
Best Regards
 João Fernandes

Hi All,
To find link between FI and CO documents:
1) Go to "BKPF-AWKEY" in table BKPF ( FI document header -> Reference key and AUAK )
 From here you get a reference document number.
2) Now for field name "REFBN" in table "COBK" you will get the CO document number in field
 "COBK-BELNR"
<Reward request removed by moderator>
Thanks
Mahendra Joshi
Message was edited by: Vinod Kumar

Relation between statistical document and the real document

How do I get relation between statistical document and the real document.
Actually I want to reverse the posted real document and then convert statistical document into real document.
Problem is that I have the Main/Sub transaction of statistical document but not of real document. So how do i link both of them.

Hello,
LFA1 is just a master data table.
To get the number of open items you refer table BSIK
To get the number of cleared items, you refer table BSAK
These two tables gives you the number of line items posted on vendors.
Hope this is informative.
Regards,
Ravi

Relation between Sales order and Production order

Hi,
In Make to stock scenario how the relation between Sales order and production order are related.In which table we will get the related fields (expect AUFK,VBAK,AUFO).
warm regards,
Surendar reddy.

The relation between sales order and prodution order is as follows.
Pass AUFNR to AFKO/AFPO Get AUFPL.
Pass AUFPL to AFVC Get BANFN.
Pass BANFn to EBAN Get EBELN.
Hope this works .
Cheers,
Lakshmi Prasanna Gandham

What is the difference between standard,sorted and hash table

can anyone say what is the difference between standard,sorted and hash tabl

Hi,
Standard Tables:
Standard tables have a linear index. You can access them using either the index or the key. If you use the key, the response time is in linear relationship to the number of table entries. The key of a standard table is always non-unique, and you may not include any specification for the uniqueness in the table definition.
This table type is particularly appropriate if you want to address individual table entries using the index. This is the quickest way to access table entries. To fill a standard table, append lines using the (APPEND) statement. You should read, modify and delete lines by referring to the index (INDEX option with the relevant ABAP command). The response time for accessing a standard table is in linear relation to the number of table entries. If you need to use key access, standard tables are appropriate if you can fill and process the table in separate steps. For example, you can fill a standard table by appending records and then sort it. If you then use key access with the binary search option (BINARY), the response time is in logarithmic relation to
the number of table entries.
Sorted Tables:
Sorted tables are always saved correctly sorted by key. They also have a linear key, and, like standard tables, you can access them using either the table index or the key. When you use the key, the response time is in logarithmic relationship 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, and you must specify either UNIQUE or NON-UNIQUE in the table definition. Standard tables and sorted tables both belong to the generic group index tables.
This table type is particularly suitable if you want the table to be sorted while you are still adding entries to it. You fill the table using the (INSERT) statement, according to the sort sequence defined in the table key. Table entries that do not fit are recognised before they are inserted. The response time for access using the key is in logarithmic relation to the number of
table entries, since the system automatically uses a binary search. Sorted tables are appropriate for partially sequential processing in a LOOP, as long as the WHERE condition contains the beginning of the table key.
Hashed Tables:
Hashes tables have no internal linear index. You can only access hashed tables by specifying the key. The response time is constant, regardless of the number of table entries, since the search uses a hash algorithm. The key of a hashed table must be unique, and you must specify UNIQUE in the table definition.
This table type is particularly suitable if you want mainly to use key access for table entries. You cannot access hashed tables using the index. When you use key access, the response time remains constant, regardless of the number of table entries. As with database tables, the key of a hashed table is always unique. Hashed tables are therefore a useful way of constructing and
using internal tables that are similar to database tables.
Regards,
Ferry Lianto

Relation between Mara, CAWN and CABN table.

Similar Messages

Maybe you are looking for