Process Defination-Table Name

What is Table name in Process deff reffers to?

Its design doc
See we have a application to be intergrated and for that I need to provision some details to AD custom Attributes.
Now to represent that app
1.I created a RO as application
2.Created a process deff and in the object name I added the app name.Now as per this doc the table name field has to have a value UD_appname.
Now when I enter this UD_appname and try to save it gives me error as stated

Similar Messages

2005 PL07 User define table name size changed?

Hi everyone,
I just upgrade Add-on from SBO 2004 to SBO 2005 PL07, there is a problem, when a DBDatasource bind to an User difine table, if the UDT name length <=7, the code runs good under, but under 2005 PL07, when UDT name Length >7, an error "Data source - Invalid table name" shows when code runs to the statement "oDBDataSource.Query(oConditions)".
who knows what's the reason of this problem, is this by the UDT name longer than SBO 2005 PL07 SDK constraint or other reasons.
Thanks in advance!
Kathy

Hi Kathy,
I haven't experienced this error, but it looks like Barend has. I am not sure if he has solved his problem, but it seems to be the same. His table name is also longer than 7 characters. Look at this post posted a couple of days ago:
SBO 2005 DBDatasource
Hope it helps,
Adele

Table names and column names defined by other languages, not English.

Hi, everyone.
I am wondering if there are any possible problems or any inconvenience
when I define table names and column names by Japanese, not English.
Currently, we are using SQL server 2000 as a db and windows as a operating
system. In the near future, we have the plan to change the database software
and operating system to "Oracle 10g" and "Linux O/S".
I have not experienced the oracle database, which has table names and column
names defined by other languages, not English.
Personally, I would like to use English as table names and column names.
In this case, I might have to provide appropriate reasons.
Are there any possible problems or any "inconvenience" in terms of
system maintenance, development, or something else ?
What could be pros and cons in this case?
Thanks in advance.
Have a nice day.
Best Regards.
Ho.

First you need to make sure your database has character set that support Japanese.
Choosing a Character Set
http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14225/ch2charset.htm#i1007681
The main "inconvenience" you will have is if the client doesn't support Japanese or unicode, it will have trouble to access the table.
And say in future after the application been developed, you want to implement the schema in some English environment, you will have hard time to do it.
My point is English tablename and column names doesn't prevent you use it in Japanese environment and save Japanese data but not vice-versa. Hope you understand.

Define variable a ROWTYPE based on a table name passed as a parameter

I am trying to write a procedure that processes rows for tables of differing structures. Table_name is passed as an IN parameter to the procedure. I define a cursor within the function that is defined by a SELECT * FROM table_name. I also need to define two variables, l_this_row and l_prev_row. I need to define them as table_name%ROWTYPE. Of course, table_name is a VARCHAR2 that contains the name of a table, whereas Oracle is expecting an actual table name in the declaration. How can I define these variables to make something like the code shown below compile and work properly? I am using Oracle 10gR2.
DEFINE PROCEDURE foo(table_name IN VARCHAR2) IS
l_this_row table_name%ROWTYPE;
l_prev_row table_name%ROWTYPE;
l_cursor SYSREFCURSOR;
BEGIN
OPEN l_cursor FOR
'SELECT * FROM '
|| table_name
|| ' ORDER BY '
|| get_pk_col_name_for_table(table_name)
|| ', version_num'; --version_num is guaranteed to be a valid column name in every table, although the other column names vary in name, quantity, and type per table.
LOOP
FETCH l_cursor INTO l_this_record;
EXIT WHEN l_cursor%NOTFOUND;
-- dynamic comparison of l_this_record and l_prev_record and conditional processing based on the comparison occurs here
l_prev_record := l_this_record;
END LOOP;
END;

Billy Verreynne wrote:
Well, one method is to keep the SQL projection consistent across the number of dynamic SQLs being dealt with. With the projection being consistent, your code does not need to guess what the row structure the column returns.Unfortunately, what I need to compare is almost everything except the primary keys. So one table might contain addresses and another might contain invoice headers. There's no way to get them into the same structure.
Billy Verreynne wrote:
This approach can also be done in a generic fashion - dealing with an arbitrary number of columns per row. This dynamic structure is more flexible, but also increases the complexity of the code that has to deal with this. For example:
create or replace type TStrings is table of varchar2(4000);Now SQLs can be created to pass any number of columns to the code to process:
select TStrings( empid, ename, jobid, date_employed, date_of_birth ) from emp order by empidThe code then uses the Count method of the TStrings type to determine the number of columns passed and processes that.Then the problem becomes having to specify all the column names. I need to figure them out dynamically, as in "SELECT column_name FROM user_tab_cols WHERE column_name NOT IN ('ID', 'PREV_ID', 'NEXT_ID')". It would, of course, be best if I didn't have to populate each array element with an individual SELECT in its own EXECUTE IMMEDIATE statement. That would certainly slow things down. If I were trying to write this using ADO.NET, I could reference something like table_name(row_index).columns(ix) without having to know any of the column names, and I could exclude columns by name using a reference like table_name.columns(column_index).name. (I don't recall the exact syntax, but it is something reasonably close to that.) But PL/SQL doesn't seem to have anything close to this.
Ideally, I want to get it to where I can do something like this in a private function:
FOR ix IN 1..TStrings.Count LOOP
   IF this_row(ix) <> last_row(ix) THEN
      RETURN FALSE;
   END IF;
END LOOP;
RETURN TRUE;
Billy Verreynne wrote:Last comment. I have to echo what the others said. This is not optimal. Dealing with variant/dynamic structures and processing rows using PL/SQL (in a slow-by-slow fashion) does not scale well. Scalability and performance comes from processing data sets using SQL.I completely understand. I'm a big fan of replacing a lot of code with one SQL statement, but that just won't work for this problem.

Need table name for removing WT in IT14 for Retro PY Processing

hey experts
could any one provide me pointers to the table name where I can make a change in the WTs in IT14 such that they do not have retrospective processing.
sample WTs 4153, 4154,4300 for the country grpng 13.
Please advise.
Regards
KK

Hi Kushagra,
while reading forum found you thread for resolving my issue to stop retro for a particular wage type in IT0014
did ur issue got resolved?
If so can you help me as well
I have did following config
1. V_582A_D : Retro acctg payroll marked as T and Past entry all marked as X
2. V_T588G : inserted one entry
0014 Recur. Payments/Deds P0014 LGART 1
3. V_T591B : checked No wage type depend.entry in payr past
anything i am missing out......
but retro is still triggering when i run payroll
any tips really helpful

Unifier Table name used for storing User-Defined Reports Information

Hello Everyone,
I am looking for the table name that stores all the User-Defined Reports information pertaining to report creation details. I want to create a dataview that will provides all the user-defined reports the system presently had on file.
Does anyone know about the system auto-created table name for User Defined Reports. It might start with "sys_"
Thanks

For custom reports, you can find them through data views - "sys_custom_report". I am wondering why UDR tables were not included.
The only effort left is manually copy pasting each name and information from Unifier on an Excel sheet. It will take a lot of time though. I will also log a SR meanwhile.
Thanks everyone for your help.

Table defined as *Standard table name

Hi all,
Tables in standard program are defined as *table name, i want to know how to use it and why they r defined as *table name
and what is the use of defining like this.
example:
Include Program FPLTDATA
TABLES: FPLT, *FPLT, TFPLT.
TABLES: FPLTD, *FPLTD.
TABLES: CCDATA, *CCDATA, CCDATE, CCARD_CVV, CCARD_RCVV.
Thanks
Venkatesh babu V

Hi Venkatesh,
just use F1 help on command TABLES.
Tables *tablename
declares an additional table work area.
Regards
rea

"ORA-00903: invalid table name" when enqueue using a CLOB in an ADT payload

I am attempting to enqueue into an AQ that has an ADT with a CLOB field in it. If I leave the CLOB empty, it works. As soon as I place content in it, I get the error below in the BPEL log.
I actually get the same problem when I run the "AQ_ADT_with_CLOB_Payload" example. Please help!
Error in the BPEL log:
<2005-11-08 09:22:07,784> <ERROR> <default.collaxa.cube.ws> <AQ Adapter::Outbound> MessageWriter_enqueue: Could not enqueue message due to database error
<2005-11-08 09:22:07,784> <ERROR> <default.collaxa.cube.ws> <AQ Adapter::Outbound>
java.sql.SQLException: ORA-00903: invalid table name
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:137)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:304)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:271)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:625)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:181)
at oracle.jdbc.driver.T4CPreparedStatement.execute_for_describe(T4CPreparedStatement.java:661)
at oracle.jdbc.driver.OracleStatement.execute_maybe_describe(OracleStatement.java:951)
at oracle.jdbc.driver.T4CPreparedStatement.execute_maybe_describe(T4CPreparedStatement.java:693)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1057)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:2901)
at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:2942)
at oracle.tip.adapter.aq.database.MessageWriter.doEnqueue(MessageWriter.java:530)
at oracle.tip.adapter.aq.database.MessageWriter.enqueue(MessageWriter.java:341)
at oracle.tip.adapter.aq.database.MessageWriter.writeMessage(MessageWriter.java:303)
at oracle.tip.adapter.aq.outbound.AQEnqueuer.execute(AQEnqueuer.java:108)
at oracle.tip.adapter.aq.AQInteraction.executeRunTime(AQInteraction.java:194)
at oracle.tip.adapter.aq.AQInteraction.execute(AQInteraction.java:180)
at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeRequestResponseOperation(WSIFOperation_JCA.java:469)
at oracle.tip.adapter.fw.wsif.jca.WSIFOperation_JCA.executeInputOnlyOperation(WSIFOperation_JCA.java:652)
at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:441)
at com.collaxa.cube.ws.WSInvocationManager.invoke2(WSInvocationManager.java:310)
at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:184)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:601)
at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:316)
at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:185)
at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3398)
at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1905)
at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(PerformMessageHandler.java:75)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:100)
at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:185)
at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5410)
at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1300)
at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:509)
at com.collaxa.cube.engine.ejb.impl.CubeDeliveryBean.handleInvoke(CubeDeliveryBean.java:307)
at ICubeDeliveryLocalBean_StatelessSessionBeanWrapper16.handleInvoke(ICubeDeliveryLocalBean_StatelessSessionBeanWrapper16.java:1796)
at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(InvokeInstanceMessageHandler.java:37)
at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:76)
at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:70)
at com.collaxa.cube.engine.ejb.impl.WorkerBean.onMessage(WorkerBean.java:86)
at com.evermind.server.ejb.MessageDrivenBeanInvocation.run(MessageDrivenBeanInvocation.java:123)
at com.evermind.server.ejb.MessageDrivenHome.onMessage(MessageDrivenHome.java:748)
at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:921)
at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186)
at java.lang.Thread.run(Thread.java:534)

OK, I figured it out myself. :)
Turns out when I define the queue name in the AQ Adapter definition, I was specifying "<Default Schema>" as the schema name. When I changed this to my actual schema name (eg: "SCOTT"), it worked. Nice little bug there!
The reason it broke with the example program is because I was changing the schema name before I deployed it. As I didn't have a SCOTT schema.
So the moral of the story here is, don't use "<Default Schema>"!
I was running on 10.1.2.0.0 [build #1787 ]. In case anyone wants to fix this.

ALL_TAB_COLUMNS table name showing with fancy characters

Dear All
when i execure followowing query and got a table name as BIN$eeHkLT/tL+PgRAAhKBTEWA==$0
select * from all_tab_columns
where column_name like '%APPLICATIONORDER%'
Please let me know what is this and how to select the data from it
thanking you

its recycle bin ; please refer to oracle documentation to understand this feature;
see below from oracle documentaion : (http://www.oracle.com/technology/pub/articles/10gdba/week5_10gdba.html)
Managing the Recycle Bin
If the tables are not really dropped in this process--therefore not releasing the tablespace--what happens when the dropped objects take up all of that space?
The answer is simple: that situation does not even arise. When a tablespace is completely filled up with recycle bin data such that the datafiles have to extend to make room for more data, the tablespace is said to be under "space pressure." In that scenario, objects are automatically purged from the recycle bin in a first-in-first-out manner. The dependent objects (such as indexes) are removed before a table is removed.
Similarly, space pressure can occur with user quotas as defined for a particular tablespace. The tablespace may have enough free space, but the user may be running out of his or her allotted portion of it. In such situations, Oracle automatically purges objects belonging to that user in that tablespace.
In addition, there are several ways you can manually control the recycle bin. If you want to purge the specific table named TEST from the recycle bin after its drop, you could issue
PURGE TABLE TEST;
or using its recycle bin name:
PURGE TABLE "BIN$04LhcpndanfgMAAAAAANPw==$0";
This command will remove table TEST and all dependent objects such as indexes, constraints, and so on from the recycle bin, saving some space. If, however, you want to permanently drop an index from the recycle bin, you can do so using:
purge index in_test1_01;
which will remove the index only, leaving the copy of the table in the recycle bin.
Sometimes it might be useful to purge at a higher level. For instance, you may want to purge all the objects in recycle bin in a tablespace USERS. You would issue:
PURGE TABLESPACE USERS;
You may want to purge only the recycle bin for a particular user in that tablespace. This approach could come handy in data warehouse-type environments where users create and drop many transient tables. You could modify the command above to limit the purge to a specific user only:
PURGE TABLESPACE USERS USER SCOTT;
A user such as SCOTT would clear his own recycle bin with
PURGE RECYCLEBIN;
You as a DBA can purge all the objects in any tablespace using
PURGE DBA_RECYCLEBIN;
As you can see, the recycle bin can be managed in a variety of different ways to meet your specific needs.

Usage of TRM Field attributes: table name in BRF+

Hi,
in the customizing activity SM34 - VC_FMCA_TRM_SCENARIO (Define Forms) you can define in the "TRM Fields Attributes" folder for each field the Setting for BRFPLUS where you should write a Table Name.
The name you enter in this field is used by BRFPLUS_MANAGER.
Could you please explain for what and when is useful this customizing?
Thanks.
Miroslav

As explained in the IMG activity documentation:
" To compare values from different versions of a form in your Tax Processing Web Dynpro application, you select the form view field, double-click the TRM Fields Attribute entry on the left-hand side and make the required entries.
7. In the TRM Fields Attribute area you can also define which form fields you want to analysis in BW. If you mark the extraction-relevant field, the system automatically defaults the field name. The derivation of this field name is done via event P343. The system shows this field name in the DataSource as well as in the program that generates the DataSource for an ISR form. For more information, about this program, follow this link.
If you are using BRFplus as the rules engine for tax returns validation and tax calculation you can enter a table name for form fields. Customizing activity Define BRFplus Objects for Form Bundles generates one BRFplus data object of the type 'table' for all fields assigned to one table name.
Caution:
Be very careful when assigning fields to table names as you can neither undo the assignment nor use this field for any other assignment."
I think it's self explanatory....
Kind regards

Cursor using variable table name

I'm new to Oracle, and am wondering if I can create a cursor that can take a variable name as the table it's selecting from. I am working on an application that is loading data to 1 of 3 tables. The table name is stored as a variable and the loads are done using dymanic sql to constuct the insert statement. At the end, I want to select and process some specific info from the table that's been loaded by cycling thru a cursor on whichever of the 3 tables was populated. I could create 3 cursors, one for each table, test the table_name variable, and then reference the specific cursor that way, but I thought there must be another way to do this. I want to be able to do something like this:
CURSOR loaded_table is select distinct(process_key) from 'v_tablename' (where v_tablename is either TABLE2, TABLE2 or TABLE3)
Any suggestions would be greatly appreciated.
Tks...MCR

It's possible to use dynamic SQL for something like this. If we're only talking about three tables, though, my hunch is that you'll be much happier defining three different cursors. Dynamic SQL is significantly harder to write, debug, and maintain than static SQL, so you're better off resorting to it only when there are so many tables that static SQL is impractical.
Justin
Distributed Database Consulting, Inc.
www.ddbcinc.com/askDDBC

OM: CLEARING THE PROCESS MESSAGES TABLES

제품 : MFG_OM
작성날짜 : 2004-10-11
OM: CLEARING THE PROCESS MESSAGES TABLES
==========================================
PURPOSE
OM 모듈을 어느 기간 사용하다 보면 process messages table -
OE_PROCESSING_MSGS_TL/OE_PROCESSING_MSGS - 에 많은 data가 쌓여 있는것을
확인할 수 있다.
이 tables의 size를 줄임으로써 system performance 향상도 기대할 수 있다.
Explanation
OE_PROCESSING_MSGS_TL table은 Order Entry concurreny problem이 실행되거
나 User interface process가 실행될때 발생하는 processing messages를
저장하는 table이다.
아래의 3가지 방법중 하나를 이용하여 process messagea tables
- OE_PROCESSING_MSGS_TL/OE_PROCESSING_MSGS -의 정보를 delete 할 수 있다.
1.SQL을 이용하여 table을 truncate
(OE_PROCESSING_MSGS_TL를 먼저 truncate 시켜야 함을 주의)
경고: 만약 truncate 방법을 선택했다면, 위 두 tables에 있는 모든 정보를
잃게 될 것이다.
2.OM application의 Process Messages form을 이용.
Delete 될 messages는 사용자의 query에 따른다.
Process Messages form에서 delete 하고자 하는 messages range를 설정하여
조회한 후, 그 query된 messages만 delete 할 수 있다.
1) Navigation: Orders, Returns>Process Messages
2) Messages source를 선택
3) Query를 원하는 Messages Request ID range를 입력
4) Query를 원하는 Messages의 Order Number range를 입력
5) Query를 원하는 Messages의 Request Date range를 입력
6) Query를 원하는 Messages의 Program Name을 선택
7) 특정한 Workflow Activity를 가지고 있는 Workflow Activity를 선택
WF activity는 Order의 actual stage를 참조한다.
8) Query를 원하는 Message의 Order Type을 선택
9) Attribute를 선택, Default는 null
10) Customer Name or Number를 선택
11) Requester를 선택
12) Find button을 선택
Process Messages window displays.
13) Query된 모든 messages를 delete 하기 위새 'Delete All' button을
click.
3.SQL을 이용하여 특정 일자전의 모든 process messages를 delete.
(OE_PROCESSING_MSGS_TL 의 data를 먼저 delete 함을 명심!!)
위 1번의 truncate option을 이용하면, SQL statement는 어떤 messages를
delete하는지 전혀 식별할 수가 없다.
만약 특정 process에 관련된 messages만을 delete하길 원하면 아래의
truncate option 2를 이용한다.
아래는 sample script이며, creation date를 근간으로 delete한다.
만약 오늘 날짜(dd-mon-yy)를 입력하면 script는 7일전의 messages만을
delete 할 것이다.
====================================================
DECLARE
l_date DATE := to_date('&delete_date');
BEGIN
Delete from oe_processing_msgs_tl
Where creation_date <= l_date - 7;
Delete from oe_processing_msgs
Where creation_date <= l_date - 7;
Exception
WHEN Others THEN
Null;
END;
After executing this script commit and exit from sqlplus.
=======================================================
Note: 꼭 기억해야 할 것은 'Delete/Truncate' 작업시 'OE_PROCESSING_MSGS'
data를 delete 전에 꼭 'OE_PROCESSING_MSGS_TL' data를 먼저 delete
해야 한다는 것이다.
Example
Reference Documents
Note 123150.1

You can include PSA's in process chain and schedule deletion periodically.
You can include process type 'Deletion of Requests from PSA / Deletion of Requests from the Change Log ' in process chain . After EHP1 upgrade you can define pattern like 2lis* or 0* it will delete all the PSA's starting with 2lis or 0 data source .
Ravi

Naming Convention and way to locate Table Names in B.I

Hello All,
I like to know information about
How to find a table
Naming convention of table
Important Tables
I will be thankful ,if anyone provide this information..

Hi Path,
I will provide information what i had got through various sources...
1) <b>Identifying Table</b>
The best way to find out from which tables the data source is getting updated is to search in <b>help.sap.com</b> by using the selection criteria<b> "datasource and the name of the data source".</b>
This displays a table which gives the name of the fields and the table names
2) <b>Naming Convention</b>
1./bic/f (cube name) is the fact table of a content cube
2./bic/D (cube name) P is the package dimension of a content cube
3./bic/D(cube name) U is the unit dimension of a content cube
4./bic/D(cube name) T is the time dimension of a content cube
5./bic/D(cube name) I is the user defined dimension of a content cube
6./bic/m (object name) master data of object
7./bic/t (object name) text data of object
8./bic/H (object name) hierarchy data of object
9./BIC/I* SID Structure of Hierarchies
10./BIC/K* Conversion of Hierarchy Nodes - SID
11./BIC/P* Master Data (Time-Ind.): Characteri
12./BIC/Q* Master Data (Time-Ind.): Characteri
13./BIC/S* Master Data IDs: InfoObject
14./BIC/T* Texts: Char.
15./BIC/X* Attribute SID Table: InfoObject
16./BIC/Y* Attribute SID Table (Time-Dep.):
17./BIC/B* Transfer structure PSA/Changelog
18./BIC/A* ODS Active records
19./BIC/F* Info cube F-Fact table
20.BIC/E* Info cube E-Fact table (compressed records)
21./BIC/D* info cube dimension tables
3) <b>Important tables</b>
I has collected some important tables that may help you..
authorization:
RSSTOBJDIR (Management Table for Authorization Objects): Link between specific authorization object and Info source (table used by transaction RSSM)
InfoPackage
RSLDPIO Links datasource to infopackages
RSLDPIOT InfoPackage Text Description
RSLDPRULE ABAP source code for InfoPackages
RSLDPSEL Hardcoded selections in InfoPackages
ProcessChain
RSEVENTCHAIN Event Chain Processing Event Table
RSEVENTHEAD Header for the event chain
RSEVENTHEADT Header for the event chain
RSPCCHAIN Process chain
RSPCCHAINATTR Attributes for a Process Chain
Queries
RSZELTDIR Directory of the reporting component elements
RSZELTTXT Texts of reporting component elements
RSZELTXREF Directory of query element references
RSRREPDIR Directory of all reports (Query GENUNIID)
RSZCOMPDIR Directory of reporting components
Workbooks
RSRWBINDEX?
List of binary large objects (Excel workbooks)
RSRWBINDEXT?
Titles of binary objects (Excel workbooks)
RSRWBSTORE?
Storage for binary large objects (Excel workbooks)
RSRWBTEMPLATE?
Assignment of Excel workbooks as personal templates
RSRWORKBOOK?
Where-used list for reports in workbooks

SE16: Syntax error in program "/1BCDWB/DB table name "

Hello experts,
I am facing one problem with SE16 transaction code. I am getting a dump saying 'Syntax error in program "/1BCDWB/DB<Z table name> ". SE16 is giving dump only for few Z tables and not for all.
We have created another transaction code ZZSE16 which resembles SE16 but with few authorizations.
I am getting similar dump with ZZSE16 also. But this time for all tables Z tables and standard tables.
It was working fine until yesterday. No code has been changed to the technical objects involved.
The dump says :
The following syntax error occurred in program "/1BCDWB/DB<table name> " in
include "/1BCDWB/DB<table name> " in
line 1060:
"The field "%_ENQU_<table name>" is unknown.
This is occurring in so many boxes with different landscapes.
In some boxes it is working fine. The program "/1BCDWB/DB<table name> " has no field starting with %_ENQU. Instead at line 1060 the field is %_K<table name> which was defined.
Can anybody please help me in solving this? Thanks in advance.
Thanks & Regards,
Paddu.

Paddu,
Please try these:
Try to activate your Ztable from SE11. Of course you may see that the table is in active state, but still try to activate it.
While activating the table if you get a pop-up saying "Display activation errors and warnings" (the message may be not exactly same) the click on No button.
Now go to transaction SE14 (Database utility), provide table name and press enter
Select Processing type as Direct, choose radio button Save data and click on "Activate and adjust database" button.
You will get a pop-up with message "Request: Adjust". Click Yes button.
Once it is completed, you can try opening the table in SE16.
I hope this helps.
Regards,
Venkat

Table name& field name for production order & operation confirmation

Hi All,
          I would like to know the table name and field name for the production order "confirmation" (CNF) and the operation confirmation (CNF).
Thanks and Regards,
PSS

Hi there,
CORU(R/3 Application development: PP Confirmations )
AFFW      Goods movements with errors from confirmatio
AFRC      Table of planned changes to conf.: Automatic
AFRD      Default values for collective confirmation
AFRH      Header information for confirmation pool
AFRP1      Table of planned changes to conf.: Automatic
AFRP2      Table of planned changes for confirmation: B
AFRP3      Table of planned changes for confirmation: C
AFRP4      Table of planned changes to confirmatn: Data
AFRU      Order completion confirmations
AFWI      Subsequently posted goods movements for conf
TAFWD      CORU: Messages that are not interpreted as e
TCORD      Table for field-dependent check routines
TCORU      Parameters for order confirmations
TCORV      Table with Routines for structureing variabl
TCORW      Confirmation: Window Control
TPARU      Control parallelized confirmation processes
TPRRU      Control table for process chain for confirma
TPRRUT     Text table for process control of confirmati
TRUGS      User status caused by deviation
CO(R/3 Application development: PP Production orders )
AFBP       CIM order: Batch print requests
AFFL       Work order sequence
AFKO       Order header data PP orders
AFPO       Order item
AFVC       Operation within an order
AFVU       DB structure of the user fields of the opera
AFVV       DB structure of the quantities/dates/values
FAPW       Index of production-/issuing plant for produ
FTIND       Missing parts index
ORDCOM      Communication control Operation download
T024F       Production scheduler
T399X       Parameters dependent on order type
T441C       Profile - availability check
T441CT      Texts for Profile "Display Availability Chec
T490       Transactions PP - orders - order category
T496B       CIM order: Assigning document types to refer
T496D       CIM: Destination/lists/spool parameters per
T496F       CIM order: Form description of the list
T496K       CIM order: Entity table of possible table id
T496N       CIM order: List descriptions
T496P       Print PP documents: Determination of output
T496R       Print PP shop papers: Report control
T496T       Print PP shop papers: Transaction control
T496V       PP Print: Default Value for Printing Online
T496Z       CIM order: Table-controlled table access
TC32       Assigning subscreen to processing location
TC34        Allocating operation to object type for the
TC62        Sequence of detail screens when processing h
TCO01      Sequence/operations control in logicstics or
TCO03      CIM order: Texts for TCO01, Description of o
TCO04      Table for controlling the screen sequence gr
TCO05      CUA status depending on panel, trans. type,
TCO06      Exclusive functions for PP orders
TCO09      CIM order: Text IDs of objects in orders
TCO10      Valuation variant for order costing
TCO11      Control table for production orders - availa
TCO12      Control table production orders - stock dete
TCO36      PP orders: Control table for calling up pop-
TCO41      CIM order: Default values for generating ope
TCO43      PP-SFC order profile
TCO43T      Description of production scheduler profile
TCO60      Sequence keys for input facility and verific
TCO61      Sequence key for PP orders
TCO62      Defining screen sequences for input facility
TCO63      Sequence of detail screens when maintaining
TCODB      Database fields development class CO per ord
TCOF        Profile for missing parts info system
TCOFF      Profile for Missing Parts Info System: Displ
TCOFFT      Texts for Missing Parts Info System: Display
TCOFG      Profile for missing parts info system: crite
TCOFGT      Texts for Missing Parts Info System: Criteri
TCOFK      Texts for functions in milestones/trigger po
TCOFS      Profile for Missing Parts Info System: Sort
TCOFST      Texts for Missing Parts Info System: Sort Cr
TCOFT      Texts for Missing Parts Info System
TCOKO      Constants for PP orders
TCOKT      Account assignment categories for order
TCOP        Field selection profile
TCOPS      Field selection profile
TCOPT      Description of Profile for Field Selection
TDUMMY      Dummy structure of a table for READ with VER
TRUG        Reason for variances in completion confirmat
TRUGT      Text describing the reason for a variance in
TXPR1      XPRA control - missing parts info system
Regards
Hemant G

Process Defination-Table Name

Similar Messages

Maybe you are looking for