I-Receivables Base Tables

Hi All,
Can any one pls share the base tables for I-RECEIVABLES module.
Regards,
Susi.

Hi Susi,
Did you have check on the:
http://etrm.oracle.com/
Thanks &
Best Regards,

Similar Messages

Interface and Base tables for Receiving Transaction Processor Program

Hi Everyone,
My requirement is to move data from staging table to rcv interface tables and then run Receiving transaction processor program. How will in know what interface tables i need to insert data into? and after I run the concurrent program what are the base tables that i need to check to confirm?
Please help!
Thanks
Sunny

RCV_HEADERS_INTERFACE
RCV_TRANSACTIONS_INTERFACE
If you have serial numbers or lot numbers for the receipts, then you need to insert into
RCV_SERIALS_INTERFACE
RCV_LOTS_INTERFACE
Once the transactions are processed, you will see records in
RCV_SHIPMENT_HEADERS
RCV_SHIPMENT_LINES
For details on the interface, check irep.oracle.com
See Import PO Receipts using custom conversion. for some scripts.
And see http://www.oracleug.com/tables/purchasing/rcvheadersinterface and http://www.oracleug.com/tables/purchasing/rcvtrnsactionsinterface for details on the tables.
Hope this answers your question,
Sandeep Gandhi

PO Base Tables and Validation

Hello All,
I need to develop conversion interface of open purchase orders.
Need help to know what are the base tables which are used for the same.
Also Need to know what all validations needs to be done.
I have identified a few.
1     PO Number already Exists in Oracle EBS.
2     Vendor not defined in Oracle EBS.
3     Currency Code not defined in Oracle EBS.
4     Bill to Location Not defined.
5     Ship to Location not defined.
6     Payment Terms not defined in Oracle EBS.
7     Vendor Site not defined
8     Buyer Not defined in EBS
9     EBS Ship to Org does not exist
9     UOM Code not defined in EBS
10     Account Code not valid
Can someone pls help with the experiences.
Thanks

Hi,
3 important tables when you are converting the PO's in Oracle interface are
PO_HEADERS_INTERFACE
PO_LINES_INTERFACE
PO_DISTRIBUTIONS_INTERFACE
Normally when you are converting the data through the stanadard interface, all validations are taken care by the above interface tables, Import Standard Purchase Orders is the standard concurrent program provided by oracle to load the data from standard interface to the base tables. PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_DISTRIBUTIONS_ALL.
And also you need to take care of the partially received PO's, Partially Billed PO's.
Hope this Helps,
Raghav

Base Tables Related To Workflow

Hai all,
Can anyone of u give me details about the base tables related to workflow

Hi,
Please find some important tables which are used in workflow
SWEINSTCOU     : Instance Linkage Event u2013 Receiver
SWFDEVINST     : Event Linkages with Instance Reference
SWW_CONTOB     : Work Item Data Container (WI to Business Objects)
SWW_CONT          : Workflow Runtime: Work Item Data Container
SWWORGTASK     : Assignment of WIs to Org. Unit/Task (WI to Task)
SWWWIHEAD     : Header Table for All Work Item Types
SWW_WI2OBJ     : Workitem form Bus Object Key ( e.g. Material No )
SWWLOGHIST     : History of a Work Item
SWW_OUTBOX     : DB View for Selection of Outbox ( WI text, WI stat etc)
SWWUSERWI     : Current Work Items Assigned to a User
Thanks
Sanjay

Transfer elements between 2 base table forms.

Environment
OS: WinXP
Oracle 10g (9.0.4.0.0) Developer suite
Scenario:
2 base table forms
Form1 is based on table1 and has 10 elements
Form1 has a button which when triggered, causes 5 of the 10 elements to be inserted in table2
Form2 is based on table2 and has 10 elements 5 of which are obtained from Form1
When I do a query-execute in Form2 to pull all the records, only records that were entered through Form2 show up. The transferred elements (record) from Form1 are not pulled up.
When I do a query->enter and search for records in Form2 that were transferred from Form1, I receive a FMR-40301 Query caused no records to be retrieved. Re-enter.
However the records transferred from Form1 are pulled up if I run a sql in the Database.
Please advice.
Here is the code that is triggered when button is pressed in Form1 to transfer elements to form2.
DECLARE
     raiDate               RAI_PROPOSAL.STAMP1%TYPE;
     raiTime RAI_PROPOSAL.STAMP2%TYPE;
     sPropNo               RAI_PROPOSAL.PROP_NO%TYPE;
     selRec               RAI_PROPOSAL%ROWTYPE;
     CURSOR getProp(propNo IN RAI_PROPOSAL.PROP_NO%TYPE) IS
          SELECT      *
          FROM          RAI_PROPOSAL
          WHERE          RAI_PROPOSAL.PROP_NO = propNo;
BEGIN
     sPropNo := :RAI_PROPOSAL.PROP_NO;
     /* Open cursor and fetch selected row */
     IF( NOT (getProp%ISOPEN) )THEN
          OPEN getProp(sPropNo);
     END IF;
     FETCH getProp INTO selRec;
     CLOSE getProp;
     /* Get date and time of transfer */
     raiDate := sysdate();
     raiTime := TO_CHAR(sysdate(), 'hh24:mi:ss');
/* list all elements being transferred - all have values so NOT NULL fields are taken care of*/
MESSAGE(selRec.cdfa_no || ', ' || selRec.con_sub || ', ' || selRec.cs_amt || ', ' || selRec.cs_source || ', ' || selRec.dept_prdir || ', ' || selRec.dept_proj2 || ', ' || selRec.dept_proj3 || ', ' ||
selRec.human_subj || ', ' || selRec.initials || ', ' || selRec.prime_agre || ', ' || selRec.prodir_fn || ', ' || selRec.prodir_ln || ', ' || selRec.prodir2fn || ', ' || selRec.prodir2ln || ', ' || selRec.prodir3fn || ', ' || selRec.prodir3ln || ', ' ||      selRec.proj_type || ', ' ||     selRec.prop_date || ', ' || selRec.prop_no || ', ' ||
selRec.prop_title || ', ' || selRec.propr_info || ', ' || selRec.school || ', ' || selRec.sol_no || ', ' || selRec.spon_typ || ', ' || selRec.sponsor || ', ' || raiDate || ', ' || raiTime || ', ' || selRec.vert_anm);
     /* Insert selected proposal into award table */
     INSERT INTO
     RAI_AWARD(CDFA_NO, CON_SUB, CS_AMT, CS_SOURCE,
               DEPT_PRDIR, DEPT_PROJ2, DEPT_PROJ3,
               HUMAN_SUBJ, INITIALS, PRIME_AGRE, PRODIR_FN, PRODIR_LN,
               PRODIR2FN, PRODIR2LN, PRODIR3FN, PRODIR3LN, PROJ_TYPE,
               PROP_DATE, PROP_NO, PROP_TITLE, PROPR_INFO, SCHOOL,
               SOL_NO, SPON_TYP, SPONSOR, STAMP1, STAMP2, VERT_ANM)
     VALUES(selRec.cdfa_no, selRec.con_sub, selRec.cs_amt, selRec.cs_source,
          selRec.dept_prdir, selRec.dept_proj2, selRec.dept_proj3,
          selRec.human_subj, selRec.initials, selRec.prime_agre, selRec.prodir_fn,
selRec.prodir_ln, selRec.prodir2fn, selRec.prodir2ln, selRec.prodir3fn, selRec.prodir3ln, selRec.proj_type, selRec.prop_date, selRec.prop_no, selRec.prop_title, selRec.propr_info, selRec.school, selRec.sol_no, selRec.spon_typ, selRec.sponsor, raiDate, raiTime, selRec.vert_anm);
     MESSAGE ('INSERTED');
     /* Commit the data inserted */
     FORMS_DDL('COMMIT');
END;

Hi,
Do you have radio buttons, a check box or a list item on your form?
I have seen this before. If the value queried from the database does not match the allowable values, the record is "silently rejected" and is not queried into the form. You say your records are in the database if you query table2 via SQL, but Forms is rejecting the records.
Look up the Forms Help for the topics "Creating a Record Group", or "Mapping of Other Values", or Search for the word "silently". It will say something like:
"Leave the Mapping of Other Values property blank to indicate that other values are not allowed for this item. Any queried record that contains a value that does not match one of the values associated with an element in the List is silently rejected. Any attempt to assign an other value is disallowed."
HTH.

Base table not found

CF5 Newbie needs help.
I am trying to create a webpage with a searchable access
database that displays photos.
I am getting the message ODBC Error Code = S0002 (Base table
not found). I have verified my database.
Maybe there is a problem with one of my initial files. I have
the search, results and details querry set up am I missing an
additional file here that would cause this problem?
Thanks -any help is greatly appreciated,
Jen

Hi,
pPerhaps one should explain some basics about privileges in the database.
You connected as sysdba, named superdba.
The table(s) you are looking for have been created by the user SAPAJ4DB.
If a user creates a table, noone !!, really noone is allowed to select them except this owner.
Not even the sysdba is allowed to select them.
And it is good that it is like this. I personally do have some private info in tables and do NOT
want to let them being seen by my boss being the sysdba of the db.
If the owner wants to allow access to this table, he has to grant privileges to other users.
There are select, insert, update, delete ( to name the DML-privileges ).
If the owner of the table you are looking for, did not do this, the sysdba is not allow to see them.
And then he will receive the error -4004.
Yes, the table DOES exist. But for the user not having a privileges for this table,
this table looks like not existing, causing this error to occur.
Therefore: connect as the owner, select there what you want.
And then think about your needs and grant the corresponding privileges to other users / the sysdba.
Have a nice weekend,
Elke

Required to create a script for base table update using XMLSTORE package.

Hi can anybody provide me some help full suggestion on how to update base table using XMLSTORE package.
I created a simple script for Employee table and can able to do the basic operation like Insert and update on the table.
Query is as follow's
DECLARE
insCtx DBMS_XMLSTORE.ctxType;
rows NUMBER;
xmlDoc CLOB :=
'<ROWSET>
<ROW num="1">
<EMPLOYEE_ID>922</EMPLOYEE_ID>
<SALARY>1801</SALARY>
<HIRE_DATE>17-DEC-2007</HIRE_DATE>
<JOB_ID>ST_CLERK</JOB_ID>
<EMAIL>RAUSSJACK</EMAIL>
<LAST_NAME>JACK</LAST_NAME>
<DEPARTMENT_ID>20</DEPARTMENT_ID>
</ROW>
<ROW>
<EMPLOYEE_ID>923</EMPLOYEE_ID>
<SALARY>2001</SALARY>
<HIRE_DATE>31-DEC-2005</HIRE_DATE>
<JOB_ID>ST_CLERK</JOB_ID>
<EMAIL>PATHAK</EMAIL>
<LAST_NAME>PRATIK</LAST_NAME>
<DEPARTMENT_ID>20</DEPARTMENT_ID>
</ROW>
</ROWSET>';
BEGIN
insCtx := DBMS_XMLSTORE.newContext('EMPLOYEES'); -- Get saved context
DBMS_XMLSTORE.clearUpdateColumnList(insCtx); -- Clear the update settings
-- Set the columns to be updated as a list of values
DBMS_XMLSTORE.setUpdateColumn(insCtx, 'EMPLOYEE_ID');
DBMS_XMLSTORE.setUpdateColumn(insCtx, 'SALARY');
DBMS_XMLSTORE.setUpdateColumn(insCtx, 'HIRE_DATE');
DBMS_XMLSTORE.setUpdateColumn(insCtx, 'JOB_ID');
DBMS_XMLSTORE.setUpdateColumn(insCtx, 'EMAIL');
DBMS_XMLSTORE.setUpdateColumn(insCtx, 'LAST_NAME');
DBMS_XMLSTORE.setUpdateColumn(insCtx, 'DEPARTMENT_ID');
-- Insert the doc.
rows := DBMS_XMLSTORE.insertXML(insCtx, xmlDoc);
--COMMIT;
DBMS_OUTPUT.put_line(rows || ' rows inserted.');
-- Close the context
DBMS_XMLSTORE.closeContext(insCtx);
END;
SELECT employee_id, LAST_name FROM employees WHERE employee_id = 114;
DECLARE
updCtx DBMS_XMLSTORE.ctxType;
rows NUMBER;
xmlDoc CLOB :=
'<ROWSET>
<ROW>
<EMPLOYEE_ID>114</EMPLOYEE_ID>
<LAST_NAME>PRABHU</LAST_NAME>
</ROW>
</ROWSET>';
BEGIN
updCtx := DBMS_XMLSTORE.newContext('EMPLOYEES'); -- get the context
DBMS_XMLSTORE.clearUpdateColumnList(updCtx); -- clear update settings
-- Specify that column employee_id is a "key" to identify the row to update.
DBMS_XMLSTORE.setKeyColumn(updCtx, 'EMPLOYEE_ID');
rows := DBMS_XMLSTORE.updateXML(updCtx, xmlDoc); -- update the table
DBMS_XMLSTORE.closeContext(updCtx); -- close the context
commit;
END;
Nowi want little modification on this above query like as i am passing static XML tags and i want it to pick the dynamic XML from web and use the XMLSTORE for the update.
and also for complex XML having 2-3 levels how this query needs to be changed.As i am new to this Oracle utillity any help from xepert will be a great help for me.
Thanks

Nowi want little modification on this above query like as i am passing static XML tags and i want it to pick the dynamic XML from webFrom a Web Service?
You'll need UTL_HTTP or HttpUriType interface to send the request and receive the XML response.
Search in the forum, there are already a lot of useful examples available.
and also for complex XML having 2-3 levels how this query needs to be changed.DBMS_XMLStore is OK for readily processing a canonical XML format (/ROWSET/ROW/COLUMN structure or alike).
However, if you have to deal with a more complex structure, you either have to :
- use a target object table that matches the XML structure
- preprocess the input document using XSLT to transform it to canonical format
That's why DBMS_XMLStore is not appropriate for multilevel documents, especially if they contain nested repeating groups.
In this case, XMLTable is a more flexible way of parsing the XML and process it relationally at the same time.
Depending on the size of the document, performance may be improved with schema-based object-relational storage.
For more help, please post a new thread in the {forum:id=34} forum, with the following information :
- database version (select * from v$version)
- a sample XML document (the complex one)
- DDL of your target table
- mapping between XML elements and columns (ie which tag goes to which column?)
- an XML schema (if you have one)

How to stored data after clicking checkbox in data base table

REPORT ZT                                      .
TYPE-pools: slis.
tables:mkpf,mseg,mard,COWB_COMP,ZTABLE.
Types:BEGIN OF tp_data,
     mblnr LIKE mseg-mblnr,
     matnr LIKE mseg-matnr,
     werks LIKE mard-werks,
     lgort LIKE mard-lgort,
     lgpbe LIKE mard-lgpbe,
     charg LIKE mseg-charg,
     bwart LIKE mseg-bwart,
     budat LIKE mkpf-budat,
     menge LIKE mseg-menge,
     meins LIKE mseg-meins,
     kostl LIKE mseg-kostl,
     aufnr LIKE mseg-aufnr,
     rsnum LIKE mseg-rsnum,
     endkz like COWB_COMP-endkz,
END OF tp_data,
tp_tbl_data TYPE STANDARD TABLE OF tp_data.
MODIFIED*******************
DATA: WA TYPE TP_DATA.
MODIFIED*******************
*data: t_data like Y00_MM_ISSUE_DAT occurs 0 with header line.
Constants
Data objects (variable declarations and definitions)
Report data to be shown.
DATA: it_data TYPE STANDARD TABLE OF tp_data.
MODIFIED*******************
DATA : V_REPID LIKE SY-REPID.
MODIFIED*******************
Heading of the report.
DATA: t_heading TYPE slis_t_listheader.
*========================== Selection Screen
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
SELECT-OPTIONS:smblnr FOR mseg-mblnr MODIF ID m1,
              smatnr FOR mseg-matnr MODIF ID m2,
              swerks FOR mard-werks MODIF ID m3,
              slgort FOR mard-lgort MODIF ID m4,
              slgpbe FOR mard-lgpbe MODIF ID m5,
              scharg FOR mseg-charg MODIF ID m6,
              sbwart FOR mseg-bwart MODIF ID m7,
              skostl FOR mseg-kostl MODIF ID m8,
              saufnr FOR mseg-aufnr MODIF ID m9,
              srsnum FOR mseg-rsnum MODIF ID m10.
SELECTION-SCREEN END OF BLOCK b1.
SELECTION-SCREEN BEGIN OF BLOCK b2 WITH FRAME TITLE text-002.
PARAMETERS:pre RADIOBUTTON GROUP radi USER-COMMAND ucomm DEFAULT 'X',
          pse RADIOBUTTON GROUP radi,
          bps RADIOBUTTON GROUP radi.
SELECTION-SCREEN END OF BLOCK b2.
SELECTION-SCREEN BEGIN OF BLOCK b3 WITH FRAME TITLE text-003.
PARAMETER:layout TYPE i.
SELECTION-SCREEN END OF BLOCK b3.
MODIFIED*******************
INITIALIZATION.
V_REPID = sy-repid.
MODIFIED*******************
*=========================== Event Blocks
AT selection-SCREEN.
start-OF-selection.
PERFORM get_data USING it_data.
END-OF-selection.
PERFORM build_alv USING it_data t_heading.
*=========================== Subroutines
*&      Form get_data
      Gets the information to be shown in the report.
FORM get_data USING t_data TYPE tp_tbl_data.
SELECT msegmblnr msegmatnr mardwerks mardlgort mard~lgpbe
msegcharg msegbwart mkpf~budat
   msegmenge msegmeins msegkostl msegaufnr mseg~rsnum
INTO CORRESPONDING FIELDS OF TABLE t_data
FROM mseg
JOIN mard ON mardmatnr EQ msegmatnr
              JOIN mkpf ON msegmblnr EQ mkpfmblnr
              WHERE mseg~matnr IN smatnr.
ENDFORM.                    " get_data
*&      Form build_alv
      Builds and display the ALV Grid.
FORM build_alv USING t_data TYPE tp_tbl_data
     t_heading TYPE slis_t_listheader.
ALV required data objects.
DATA: w_title   TYPE lvc_title,
       w_comm    TYPE slis_formname,
       w_status TYPE slis_formname,
       x_layout TYPE slis_layout_alv,
       t_event    TYPE slis_t_event,
       t_fieldcat TYPE slis_t_fieldcat_alv,
       t_sort     TYPE slis_t_sortinfo_alv.
REFRESH t_fieldcat.
REFRESH t_event.
REFRESH t_sort.
CLEAR x_layout.
CLEAR w_title.
Field Catalog
PERFORM set_fieldcat2 USING:
       1 'MBLNR' 'MBLNR' 'MSEG' space space space space space space
space space space space space space t_fieldcat ,
       2 'MATNR' 'MATNR' 'MSEG' space space space space space space
space space space space space space t_fieldcat ,
       3 'WERKS' 'WERKS' 'MARD' space space space space space space
space space space space space space t_fieldcat,
       4 'LGORT' 'LGORT' 'MARD' space space space space space space
space space space space space space t_fieldcat ,
       5 'LGPBE' 'LGPBE' 'MARD' space space space space space space
space space space space space space t_fieldcat ,
       6 'CHARG' 'CHARG' 'MSEG' space space space space space space
space space space space space space t_fieldcat ,
       7 'BWART' 'BWART' 'MSEG' space space space space space space
space space space space space space t_fieldcat,
       8 'BUDAT' 'BUDAT' 'MKPF' space space space space space space
space space space space space space t_fieldcat,
       9 'MENGE' 'MENGE' 'MSEG' space space space space space space
space space space space space space t_fieldcat,
       10 'MEINS' 'MEINS' 'MSEG' space space space space space space
space space space space space space t_fieldcat,
       11 'KOSTL' 'KOSTL' 'MSEG' space space space space space space
space space space space space space t_fieldcat,
       12 'AUFNR' 'AUFNR' 'MSEG' space space space space space space
space space space space space space t_fieldcat,
       13 'RSNUM' 'RSNUM' 'MSEG' space space space space space space
space space space space space space t_fieldcat,
   14 'ENDKZ' 'ENDKZ' 'COWB_COMP' space space 'select' 'Select this row' 'Sel' 'Select this row' space space space 'X' 'X' space t_fieldcat.
Layout
x_layout-zebra = 'X'.
Top of page heading
PERFORM set_top_page_heading USING t_heading t_event.
Events
PERFORM set_events USING t_event.
GUI Status
w_status = ''.
User commands
w_comm   = 'USER_COMMAND'.
Order
Example
PERFORM set_order USING '<field>' 'IT_DATA' 'X' space space t_sort.
PERFORM set_order USING 'MBLNR' 'IT_DATA' 'X' space 'X' t_sort.
PERFORM set_order USING 'EBELN' 'IT_DATA' 'X' space 'X' t_sort.
PERFORM set_order USING 'EBELP' 'IT_DATA' 'X' space space t_sort.
Displays the ALV grid
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
   i_callback_program       = V_REPID
   it_fieldcat              = t_fieldcat
   is_layout                = x_layout
   it_sort                  = t_sort
   i_callback_pf_status_set = w_status
   i_callback_user_command = w_comm
   i_save                   = 'X'
   it_events                = t_event
   i_grid_title             = w_title
TABLES
   t_outtab                 = t_data
EXCEPTIONS
   program_error            = 1
   OTHERS                   = 2.
IF sy-subrc <> 0.
   MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
   WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
ENDFORM.                    " build_alv.
*&      Form set_top_page_heading
      Creates the report headings.
FORM set_top_page_heading USING t_heading TYPE slis_t_listheader
     t_events TYPE slis_t_event.
DATA: x_heading TYPE slis_listheader,
       x_event   TYPE LINE OF slis_t_event.
Report title
CLEAR t_heading[].
CLEAR x_heading.
x_heading-typ = 'H'.
x_heading-info = 'Reporte Prueba'(001).
APPEND x_heading TO t_heading.
Program name
CLEAR x_heading.
x_heading-typ = 'S'.
x_heading-KEY = 'Program: '.
x_heading-info = sy-repid.
APPEND x_heading TO t_heading.
User who is running the report
CLEAR x_heading.
x_heading-typ = 'S'.
x_heading-KEY = 'User: '.
x_heading-info = sy-uname.
APPEND x_heading TO t_heading.
Date of execution
CLEAR x_heading.
x_heading-typ = 'S'.
x_heading-KEY = 'Date: '.
WRITE sy-datum TO x_heading-info.
APPEND x_heading TO t_heading.
Time of execution
CLEAR x_heading.
x_heading-typ = 'S'.
x_heading-KEY = 'Time: '.
WRITE sy-uzeit TO x_heading-info.
APPEND x_heading TO t_heading.
Top of page event
x_event-name = slis_ev_top_of_page.
x_event-FORM = 'TOP_OF_PAGE'.
APPEND x_event TO t_events.
ENDFORM.
*&      Form set_events
      Sets the events for ALV.
      The TOP_OF_PAGE event is alredy being registered in
      the set_top_page_heading subroutine.
FORM set_events USING t_events TYPE slis_t_event.
DATA: x_event   TYPE LINE OF slis_t_event.
Example
clear x_event.
x_event-name = .
x_event-form = .
append x_event to t_event.
ENDFORM.
*&      Form set_order
      Adds an entry to the order table.
FORM set_order USING p_fieldname p_tabname p_up p_down p_subtot
     t_sort TYPE slis_t_sortinfo_alv.
DATA: x_sort TYPE slis_sortinfo_alv.
CLEAR x_sort.
x_sort-fieldname = p_fieldname.
x_sort-tabname   = p_tabname.
x_sort-UP = p_up.
x_sort-down = p_down.
x_sort-subtot = p_subtot.
APPEND x_sort TO t_sort.
ENDFORM.                    "set_order
*&      Form set_fieldcat2
      Adds an entry to the field catalog.
FORM set_fieldcat2 USING p_colpos p_fieldname p_ref_fieldname
p_ref_tabname
     p_outputlen p_noout
     p_seltext_m p_seltext_l p_seltext_s p_reptext_ddic p_ddictxt
     p_hotspot p_showasicon p_checkbox p_edit
     p_dosum
     t_fieldcat TYPE slis_t_fieldcat_alv.
DATA: wa_fieldcat TYPE slis_fieldcat_alv.
CLEAR wa_fieldcat.
General settings
wa_fieldcat-fieldname = p_fieldname.
wa_fieldcat-col_pos = p_colpos.
wa_fieldcat-no_out = p_noout.
wa_fieldcat-HOTSPOT = p_hotspot.
wa_fieldcat-CHECKBOX = p_checkbox.
wa_fieldcat-ICON = p_showasicon.
wa_fieldcat-do_sum = p_dosum.
Set reference fieldname, tablenam and rollname.
If p_ref_tabname is not given, the ref_fieldname given is a data
*element.
If p_ref_tabname is given, the ref_fieldname given is a field of a
*table. In case ref_fieldname is not given, it is copied from the
*fieldname.
IF p_ref_tabname IS INITIAL.
   wa_fieldcat-rollname =   p_ref_fieldname.
ELSE.
   wa_fieldcat-ref_tabname = p_ref_tabname.
   IF p_ref_fieldname EQ space.
     wa_fieldcat-ref_fieldname =   wa_fieldcat-fieldname.
   ELSE.
     wa_fieldcat-ref_fieldname =   p_ref_fieldname.
   ENDIF.
ENDIF.
Set output length.
IF NOT p_outputlen IS INITIAL.
   wa_fieldcat-outputlen = p_outputlen.
ENDIF.
Set text headers.
IF NOT p_seltext_m IS INITIAL.
   wa_fieldcat-seltext_m = p_seltext_m.
ENDIF.
IF NOT p_seltext_l IS INITIAL.
   wa_fieldcat-seltext_l = p_seltext_l.
ENDIF.
IF NOT p_seltext_s IS INITIAL.
   wa_fieldcat-seltext_s = p_seltext_s.
ENDIF.
IF NOT p_reptext_ddic IS INITIAL.
   wa_fieldcat-reptext_ddic = p_reptext_ddic.
ENDIF.
IF NOT p_ddictxt IS INITIAL.
   wa_fieldcat-ddictxt = p_ddictxt.
ENDIF.
Set as editable or not.
IF NOT p_edit IS INITIAL.
   wa_fieldcat-INPUT     = 'X'.
   wa_fieldcat-EDIT     = 'X'.
ENDIF.
APPEND wa_fieldcat TO t_fieldcat.
ENDFORM.                   "set_fieldcat2
*&      Form top_of_page
      Called on top_of_page ALV event.
      Prints the heading.
FORM top_of_page.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
EXPORTING
     i_logo             = 'TRVPICTURE04'
   it_list_commentary = t_heading.
ENDFORM.                    " alv_top_of_page
*&      Form user_command
      Called on user_command ALV event.
      Executes custom commands.
FORM user_command USING r_ucomm     LIKE sy-ucomm
     rs_selfield TYPE slis_selfield.
case sy-ucomm.
WHEN '&DATA_SAVE'.
LOOP AT IT_DATA INTO WA WHERE ENDKZ = 'X'.
   IF WA-ENDKZ = 'X'.
*******MODIFIED*********************************
U DELETE THIS CODE N USER UR INSERT CODE TO CHECK
SY-MSGV1 = WA-MBLNR.                              " U CAN DELETE
SY-MSGV2 = WA-MATNR.                              " U CAN DELETE
MESSAGE ID 'BC_BOR' TYPE 'I' NUMBER '888'          " U CAN DELETE
        WITH SY-MSGV1 SY-MSGV2. " U CAN DELETE
*******MODIFIED*********************************
   INSERT ZTABLE.
   ENDIF.
endloop.
ENDCASE.
ENDFORM.                    "user_command
this is my code, database will stored in fields only.data is empty,
how to slove that one,send any sugestion.

Hi Lakshmi,
       Can u explain briefly what is ur requirement. U mean to say that after clicking the checkbox in data base table or Screen?
Regards,
Jayaram...

Data Not loaded from ap_invoice_lines_interface to the base table

Hi ,
Please I'm working on Interface which load invoices from Cobol system to oracle , anyway procedure is working on fine & all data is loaded to the interface as i'm inserting 4 attributes which is DFF on the invoice line level
Now when i ran the import program all data is loaded to the base table except one of the attributes isnot loaded .
will anyone tell me what is the reason or how can i trace that ..........
Thanks In Advance

Dear All ,,,,
Please i got it's a matter of size of the attribute1 segment i increased it ,,,,,,,,,but now the issue that data is saved in the base table but not showing in the screen
will you please help me in that
Edited by: miro_feps on May 21, 2012 1:01 AM

How to stored data after clicking check box save in data base table

TABLES:mseg,mard,mkpf.
TYPE-POOLS:slis.
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
SELECT-OPTIONS:smblnr FOR mseg-mblnr MODIF ID m1,
               smatnr FOR mseg-matnr MODIF ID m2,
               swerks FOR mard-werks MODIF ID m3,
               slgort FOR mard-lgort MODIF ID m4,
               slgpbe FOR mard-lgpbe MODIF ID m5,
               scharg FOR mseg-charg MODIF ID m6,
               sbwart FOR mseg-bwart MODIF ID m7,
               skostl FOR mseg-kostl MODIF ID m8,
               saufnr FOR mseg-aufnr MODIF ID m9,
               srsnum FOR mseg-rsnum MODIF ID m10.
SELECTION-SCREEN END OF BLOCK b1.
SELECTION-SCREEN BEGIN OF BLOCK b2 WITH FRAME TITLE text-002.
PARAMETERS:pre RADIOBUTTON GROUP radi USER-COMMAND ucomm DEFAULT 'X',
           pse RADIOBUTTON GROUP radi,
           bps RADIOBUTTON GROUP radi.
SELECTION-SCREEN END OF BLOCK b2.
SELECTION-SCREEN BEGIN OF BLOCK b3 WITH FRAME TITLE text-003.
PARAMETER:layout TYPE i.
SELECTION-SCREEN END OF BLOCK b3.
DATA:BEGIN OF itab OCCURS 0,
     mblnr LIKE mseg-mblnr,
     matnr LIKE mseg-matnr,
     werks LIKE mard-werks,
     lgort LIKE mard-lgort,
     lgpbe LIKE mard-lgpbe,
     charg LIKE mseg-charg,
     bwart LIKE mseg-bwart,
     budat LIKE mkpf-budat,
     menge LIKE mseg-menge,
     meins LIKE mseg-meins,
     kostl LIKE mseg-kostl,
     aufnr LIKE mseg-aufnr,
     rsnum LIKE mseg-rsnum,
     checkbox TYPE c,
     END OF itab.
DATA: gt_fieldcat TYPE slis_t_fieldcat_alv,
       gw_fieldcat TYPE slis_fieldcat_alv,
       gt_layout TYPE slis_layout_alv.
START-OF-SELECTION.
SELECT msegmblnr msegmatnr mardwerks mardlgort mardlgpbe msegcharg msegbwart mkpfbudat
    msegmenge msegmeins msegkostl msegaufnr mseg~rsnum
INTO TABLE itab FROM
          mseg JOIN mard ON mardmatnr EQ msegmatnr
               JOIN mkpf ON msegmblnr EQ mkpfmblnr
               WHERE mseg~matnr IN smatnr.
IF sy-subrc EQ 0.
    SORT itab BY matnr.
    PERFORM display_alv_output.
ENDIF.
*&      Form display_alv_output
      text
--> p1        text
<-- p2        text
FORM display_alv_output.
REFRESH gt_fieldcat.
gw_fieldcat-fieldname = 'MBLNR'.
gw_fieldcat-tabname = 'itab'.
gw_fieldcat-col_pos = 1.
gw_fieldcat-seltext_m = 'material document'.
gw_fieldcat-key = 'x'.
APPEND gw_fieldcat TO gt_fieldcat.
CLEAR gw_fieldcat.
gw_fieldcat-fieldname = 'MATNR'.
gw_fieldcat-tabname = 'itab'.
gw_fieldcat-col_pos = 2.
gw_fieldcat-seltext_m = 'material'.
gw_fieldcat-key = ' '.
APPEND gw_fieldcat TO gt_fieldcat.
CLEAR gw_fieldcat.
gw_fieldcat-fieldname = 'WERKS'.
gw_fieldcat-tabname = 'itab'.
gw_fieldcat-col_pos = 3.
gw_fieldcat-seltext_m = 'plant'.
gw_fieldcat-key = ' '.
APPEND gw_fieldcat TO gt_fieldcat.
CLEAR gw_fieldcat.
gw_fieldcat-fieldname = 'LGORT'.
gw_fieldcat-tabname = 'itab'.
gw_fieldcat-col_pos = 4.
gw_fieldcat-seltext_m = 'storage location'.
gw_fieldcat-key = ' '.
APPEND gw_fieldcat TO gt_fieldcat.
CLEAR gw_fieldcat.
gw_fieldcat-fieldname = 'LGPBE'.
gw_fieldcat-tabname = 'itab'.
gw_fieldcat-col_pos = 5.
gw_fieldcat-seltext_m = 'storage bin'.
gw_fieldcat-key = ' '.
APPEND gw_fieldcat TO gt_fieldcat.
CLEAR gw_fieldcat.
gw_fieldcat-fieldname = 'CHARG'.
gw_fieldcat-tabname = 'itab'.
gw_fieldcat-col_pos = 6.
gw_fieldcat-seltext_m = 'Batch number'.
gw_fieldcat-key = ' '.
APPEND gw_fieldcat TO gt_fieldcat.
CLEAR gw_fieldcat.
gw_fieldcat-fieldname = 'BWART'.
gw_fieldcat-tabname = 'itab'.
gw_fieldcat-col_pos = 7.
gw_fieldcat-seltext_m = 'Movement Type (Inventory Management)'.
gw_fieldcat-key = ' '.
APPEND gw_fieldcat TO gt_fieldcat.
CLEAR gw_fieldcat.
gw_fieldcat-fieldname = 'BUDAT'.
gw_fieldcat-tabname = 'itab'.
gw_fieldcat-col_pos = 8.
gw_fieldcat-seltext_m = 'Posting Date in the Document'.
gw_fieldcat-key = ' '.
APPEND gw_fieldcat TO gt_fieldcat.
CLEAR gw_fieldcat.
gw_fieldcat-fieldname = 'MENGE'.
gw_fieldcat-tabname = 'itab'.
gw_fieldcat-col_pos = 9.
gw_fieldcat-seltext_m = 'QUANTITY'.
gw_fieldcat-key = ' '.
APPEND gw_fieldcat TO gt_fieldcat.
CLEAR gw_fieldcat.
gw_fieldcat-fieldname = 'MEINS'.
gw_fieldcat-tabname = 'itab'.
gw_fieldcat-col_pos = 10.
gw_fieldcat-seltext_m = 'Basic unit of measure'.
gw_fieldcat-key = ' '.
APPEND gw_fieldcat TO gt_fieldcat.
CLEAR gw_fieldcat.
gw_fieldcat-fieldname = 'KOSTL'.
gw_fieldcat-tabname = 'itab'.
gw_fieldcat-col_pos = 11.
gw_fieldcat-seltext_m = 'Cost center'.
gw_fieldcat-key = ' '.
APPEND gw_fieldcat TO gt_fieldcat.
CLEAR gw_fieldcat.
gw_fieldcat-fieldname = 'AUFNR'.
gw_fieldcat-tabname = 'itab'.
gw_fieldcat-col_pos = 12.
gw_fieldcat-seltext_m = 'Order Number'.
gw_fieldcat-key = ' '.
APPEND gw_fieldcat TO gt_fieldcat.
CLEAR gw_fieldcat.
gw_fieldcat-fieldname = 'RSNUM'.
gw_fieldcat-tabname = 'itab'.
gw_fieldcat-col_pos = 13.
gw_fieldcat-seltext_m = 'Number of Reservation / Depe'.
gw_fieldcat-key = ' '.
APPEND gw_fieldcat TO gt_fieldcat.
CLEAR gw_fieldcat.
gw_fieldcat-col_pos = 14.
gw_fieldcat-fieldname = 'CHECKBOX'.
gw_fieldcat-seltext_m = 'Compltd'.
gw_fieldcat-checkbox = 'X'.
gw_fieldcat-edit = 'X'.
APPEND gw_fieldcat TO gt_fieldcat.
CLEAR gw_fieldcat.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
    I_CALLBACK_PROGRAM                = 'ZREPORT'
    IS_LAYOUT                         = gt_layout
    IT_FIELDCAT                       = gt_fieldcat
   TABLES
     t_outtab                          = itab
EXCEPTIONS
    PROGRAM_ERROR                     = 1
    OTHERS                            = 2.
ENDFORM.                    " display_alv_output
this is mycode .
send me replay.

Hi Lakshmi,
       Can u explain briefly what is ur requirement. U mean to say that after clicking the checkbox in data base table or Screen?
Regards,
Jayaram...

View's base table ?

how do i knw the views base table...
i can view text from user_source
but i there any dictionary table which show view name and base table name..?

Hmm , jsut a note to mention that you may use , v$fixed_view_definition also.
For example,
SQL> select view_definition
2 from v$fixed_view_definition where view_name=’V$LOG’;
VIEW_DEFINITION
select   GROUP# , THREAD# , SEQUENCE# , BYTES , MEMBERS , ARCHIVED , STATUS , FI
RST_CHANGE# , FIRST_TIME from GV$LOG where inst_id = USERENV(’Instance’)
SQL> select view_definition
2 from v$fixed_view_definition where view_name=’GV$LOG’;
VIEW_DEFINITION
select le.inst_id, le.lenum, le.lethr, le.leseq, le.lesiz*le.lebsz, ledup, decod
e(bitand(le.leflg,1),0,’NO’,'YES’), decode(bitand(le.leflg,24), 8, ‘CURRENT’,
                         16,’CLEARING’,                            24,’CLEARING_
CURRENT’,        decode(sign(leseq),0,’UNUSED’,        decode(sign((to_number(rt
.rtckp_scn)-to_number(le.lenxs))*        bitand(rt.rtsta,2)),-1,’ACTIVE’,'INACTI
VE’))), to_number(le.lelos), to_date(le.lelot,’MM/DD/RR HH24:MI:SS’,'NLS_CALENDA
R=Gregorian’) from x$kccle le, x$kccrt rt where le.ledup!=0 and le.lethr=rt.rtnu
m and le.inst_id = rt.inst_id
SQL>HTH
Aman....

ORA-01776: cannot modify more than one base table through a join view

I have created EO based on a database view than consists of two tables, and only one is updateable.
When I try to update a row using EO, I got a following message: "ORA-01776-cannot modify more than one base table through a join view"
In Forms, this issue is resolved by setting "Query Only" property of non-updateable items to "True".
Is it possible to do something like that in ADF BC?
Thanks

Thanks for answer.
When I set "updateable" property to "Never", that attribute is protected from any change.
I'm sorry for incomplete usecase.
I have set up a list of value on that attribute, because it is a lookup field for another table and I need to get an ID from that table.
Basically, I need that attribute to be updateble for BC, but not for database.
Edited by: MarioK on Oct 13, 2011 9:28 AM

Cannot modify more than one base table through a join view

hi guys, my current problem is that i have a datablock based on a view, now all the fields bar 1 are updateable, but this one field that is obtained through a join is displayed, the user can enter data in this field which then pupulates other fields which are required, but this specific field should not be updated. Is there an option to state this as i keep getting the error:
cannot modify more than one base table through a join view
Any help would be greatly appreciated, thanks.

the user can enter data in this field which then pupulates other fields So, using the value of "this field" you then query the rest of the fields? Can you show us the code you use to populate the rest of the fields?
but this specific field should not be updatedHave you tried setting the "Query Only" property of the field to "Yes" and the other DML properties (Ins, Upd, Del) to No?
Also, what is your Forms version?
Thanks,
Craig B-)
If someone's response is helpful or correct, please mark it accordingly.

Create a materized view without primary key constraint on the base table?

Hi
I tried to create a materized view but I got this error:
SQL> CREATE MATERIALIZED VIEW TABLE1_MV REFRESH FAST
START WITH
to_date('04-25-2009 03:00:13','MM-dd-yyyy hh24:mi:ss')
NEXT
sysdate + 1
AS
select * from TABLE1@remote_db
SQL> /
CREATE MATERIALIZED VIEW TABLE1_MV REFRESH FAST
ERROR at line 1:
ORA-12014: table 'TABLE1' does not contain a primary key constraint.
TABLE1 in remote_db doesn't have a primary key constraint. Is there anyway that I can create a materized view on a base table which doesn't have a primary key constraint?
Thanks
Liz

Hi,
Thanks for your helpful info. I created a materialized view in the source db with rowid:
SQL> CREATE MATERIALIZED VIEW log on TABLE1 with rowid;
Materialized view log created.
Then I created a MV on the target DB:
CREATE MATERIALIZED VIEW my_schema.TABLE1_MV
REFRESH FAST
with rowid
START WITH
to_date('04-25-2009 03:00:13','MM-dd-yyyy hh24:mi:ss')
NEXT
sysdate + 1
AS
select * from TABLE1@remote_db
SQL> /
CREATE MATERIALIZED VIEW my_schema.TABLE1_MV
ERROR at line 1:
ORA-12018: following error encountered during code generation for
"my_schema"."TABLE1_MV"
ORA-00942: table or view does not exist
TABLE1 exists in remote_db:
SQL> select count(*) from TABLE1@remote_db;
COUNT(*)
9034459
Any clue what is wrong?
Thanks
Liz

Assigning a Value to a Base Table BLock Field

hi,
I have a form in which a block is a base table block . i need to change the value of a field. currently it shows the value of a field from the Table on which the block is based . I need to change the value of that field to display some other value of another table.
i have a written select statement like this
select name into vname from ws_emp where ecode = 101
then i have assigned to this base table field
:bt_person.ti_v_name := vname;
this i have created in the base table blocks Post query
but it is not assigning value
pls correct me and suggest me if there is any other better method to do this
Sarav

That SHOULD work in the Post-Query trigger of the block, but doing that is never a good idea. By replacing a base-table field with any value, it causes Forms automatic processing to lock the row immediately, so no other person running your form can call up the same data. And it causes Forms to think you need to update the record, so the record's status is changed to 'CHANGED' from 'QUERY'.
It would be better to create a non-base-table field in the block, and put the name into that field.

I-Receivables Base Tables

Similar Messages

Maybe you are looking for