How to generate bad records for varchar2 type

Hi
Iam using sqlldr to load records from a flat file to a table.
Table columns contains varchar2 datatype
Data is loaded by fixedlength position.
There is no not null restriction on the fields.
I want to have a bad file generated.
Can anyone let me know how to get the bad file?
What type of data can be modified in a file to get a bad record.
Thanks in advance

how to get the bad file?Make the field length longer than its corresponding DB field length?
I.e. when your DB field length is varchar2(10) make one of the fields in the file greater than 10.

Similar Messages

How to create a record for table PLAF with order type 'NB'.

How to create a record for table PLAF with order type 'NB'(standard purchase order).
who can tell me the T-code or some usefull information?
Thanks.

Hi
This will be updated automatically when generate planned orders thru MRP. (MD02)
regards
Srinivas

PT_QTA00 is generating repetative records for the same quota type

PT_QTA00 is generating repetative records for the same quota type and one more thing i have already maintained 10 days of quota in 2006 and when i run for the same employee its creating one more record with 10 days again how can we restrict it in configuration

As said earlier, you want to setup Time Constraints for It2006 which is in table: V_T582A
You should set the Time Constraint to 2.
HR master data uses the following three time constraints:
Time Constraint 1
For the entire time that the employee works at the enterprise, exactly one valid infotype record must exist. The validity periods of the individual records must not overlap. If a new record is created, the system automatically uses the start date of the new record as the delimitation date of the old record. Gaps are only allowed between the employeeu2019s entry date and the start date of the first record.
Time constraint 1 must be used for all of the infotypes containing information that must be available at all times. This is particularly true of personal and organizational assignment data.
If a record is delimited because of time constraint 1, the system displays an appropriate message.
Time Constraint 2
No more than one valid record can exist at any one time. Records with constraint 2 must not overlap. Their existence is not obligatory. If a new record is created, the system automatically delimits the previous record, if one exists.
If a record is delimited because of time constraint 2, the system displays an appropriate message.
Time Constraint 3
Any number of valid records can exist at any one time. The individual records do not conflict with each other.

How to generate a set of date type records

How to generate a set of date-type records, with a fixed interval, starting from a date like 2008-01-01.

Some thing like this
SQL> select to_char(to_date('2008-01-01','yyyy-mm-dd') + (level - 1),'DD-MON-YYYY') my_date
2 from dual
3 connect by level <= 10
4 /
MY_DATE
01-JAN-2008
02-JAN-2008
03-JAN-2008
04-JAN-2008
05-JAN-2008
06-JAN-2008
07-JAN-2008
08-JAN-2008
09-JAN-2008
10-JAN-2008
10 rows selected.

How to create an output condition record for output type

For SD LE shipping...
Create an output condition record for output type
Thanks!
Message was edited by:
        Hoo Laa
Message was edited by:
        Hoo Laa

Hi Hoo,
Follow the path.
SAP Easy Access -> Logistics -> Logistics Execution -> Master Data -> Output   -> Shipping - > Create.
Tcode: VV21.
Hope I have clarified your query. Do reward if so.
Regards
Nadarajah Pratheb

Mappingtool generates bad DDL for sybase (J2ee tutorial)

Running the mappingtool on the J2EE tutorial app (3.0.0RC1) generates bad
DDL for sybase. It's trying to create a table with a column of type
"IndexName":
C:\devtools\kodo\samples\j2ee>mappingtool -a refresh package.jdo
0 INFO [main] kodo.Tool - Mapping tool running on type "class
samples.j2ee.Car" with action "refresh".
0 INFO [main] kodo.Tool - The tool is now reading existing schema
information; this process may take some time. En
able the kodo.jdbc.Schema logging category to see messages about schema
data. Also see the -readSchema tool flag.
3716 INFO [main] kodo.Tool - Recording mapping and schema changes.
Exception in thread "main" kodo.util.FatalException:
com.solarmetric.jdbc.ReportingSQLException: Can't specify a length
or scale on type 'IndexName'.
{stmnt 7576378: CREATE TABLE CAR (COLOR IndexName(255) NULL, JDOCLASS
IndexName(255) NULL, JDOID NUMERIC(38) NOT NULL,
JDOVERSION INT NULL, MAKE IndexName(255) NULL, MODEL IndexName(255) NULL,
YEAR0 IndexName(255) NULL, UNQ_INDEX NUMERIC I
DENTITY UNIQUE, CONSTRAINT P_CAR PRIMARY KEY (JDOID))} [code=2716,
state=ZZZZZ]
NestedThrowables:
com.solarmetric.jdbc.ReportingSQLException: Can't specify a length or
scale on type 'IndexName'.
{stmnt 7576378: CREATE TABLE CAR (COLOR IndexName(255) NULL, JDOCLASS
IndexName(255) NULL, JDOID NUMERIC(38) NOT NULL,
JDOVERSION INT NULL, MAKE IndexName(255) NULL, MODEL IndexName(255) NULL,
YEAR0 IndexName(255) NULL, UNQ_INDEX NUMERIC I
DENTITY UNIQUE, CONSTRAINT P_CAR PRIMARY KEY (JDOID))} [code=2716,
state=ZZZZZ]
at kodo.jdbc.meta.MappingTool.record(MappingTool.java:431)
at kodo.jdbc.meta.MappingTool.run(MappingTool.java:790)
at kodo.jdbc.meta.MappingTool.main(MappingTool.java:729)
NestedThrowablesStackTrace:
com.solarmetric.jdbc.ReportingSQLException: Can't specify a length or
scale on type 'IndexName'.
{stmnt 7576378: CREATE TABLE CAR (COLOR IndexName(255) NULL, JDOCLASS
IndexName(255) NULL, JDOID NUMERIC(38) NOT NULL,
JDOVERSION INT NULL, MAKE IndexName(255) NULL, MODEL IndexName(255) NULL,
YEAR0 IndexName(255) NULL, UNQ_INDEX NUMERIC I
DENTITY UNIQUE, CONSTRAINT P_CAR PRIMARY KEY (JDOID))} [code=2716,
state=ZZZZZ]
at
com.solarmetric.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:67)
at
com.solarmetric.jdbc.LoggingConnectionDecorator.access$400(LoggingConnectionDecorator.java:19)
at
com.solarmetric.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingStatement.executeUpdate(LoggingConne
ctionDecorator.java:506)
at
com.solarmetric.jdbc.DelegatingStatement.executeUpdate(DelegatingStatement.java:125)
at kodo.jdbc.schema.SchemaTool.executeSQL(SchemaTool.java:1042)
at kodo.jdbc.schema.SchemaTool.createTable(SchemaTool.java:803)
at kodo.jdbc.schema.SchemaTool.add(SchemaTool.java:334)
at kodo.jdbc.schema.SchemaTool.add(SchemaTool.java:186)
at kodo.jdbc.meta.MappingTool.record(MappingTool.java:364)
at kodo.jdbc.meta.MappingTool.run(MappingTool.java:790)
at kodo.jdbc.meta.MappingTool.main(MappingTool.java:729)
Anyone else seen this? It works ok with Hypersonic (though i can't get the
tutorial app to run with hypersonic - see my earlier post).
Alex.

Some bugs in RCs sometimes don't make it into Bugzilla as it is a
release candidate and not production quality.
I would reocmmend upgrading as it fixes a number of major bug fixes and
you should be able to use the same eval key.
Alex Robbins wrote:
Abe White wrote:
I should also have asked: what JDBC driver are you using?Hi Abe,
I haven't tried with RC2 - has this been fixed in RC2? I didn't find this
bug on bugzilla.
I'm using Sybase JConnect JDBC driver (com.sybase.jdbc2.jdbc.SybDriver in
jconn2.jar) - looks like this is the version:
jConnect (TM) for JDBC(TM)/5.5(Build 25008)/P/JDK12/Tue May 29 14:37:46
2001
Should I upgrade from RC1 to RC2, and if so, can I continue to use the
same eval license key or can i download a new one?
thanks,
alex
Stephen Kim
[email protected]
SolarMetric, Inc.
http://www.solarmetric.com

How to generate BP number for the employee (ECC to CRM) ...

Hi all,
can any one give solution for ,how to generate BP number for the employee from ECC to CRM other than active status,as i downloaded employee data from ECC to CRM through ALE/IDOC,as only active employment status employees are got BP number generated,remaining also transfered to CRM but BP number is not generated for those employees,these employee records i can able to see in the HRP5580- HRP5587 tables.
thanks in advance.
vamshi.
Message was edited by:
vamshidher rao

Hi,
Or are you looking for this:
SELECT serial_number, paaf.assignment_number
FROM pay_assignment_actions paa, per_all_assignments_f paaf
WHERE action_status = 'C'
AND paaf.assignment_id = paa.assignment_id
AND serial_number IS NOT NULL
AND SYSDATE BETWEEN paaf.effective_start_date AND paaf.effective_end_date;
- Viky
Edited by: Viky on Dec 17, 2010 11:42 AM

How to generate xml-file for SAP Fiori (UI add-on) with Solution Manager 7.0.1?

Hello Guru,
could you please help with my issue with Fiori Installation.
We want to install SAP Fiori Front-End (GW+UI) on the Sandbox system with SAP Netweaver 7.3.1. (SP14)
Gateway component (SAP GW CORE 200 SP10) was installed without any problems.
But I need to install UI-add-on (NW UI Extensions v1.0) and when I try to install it via SAINT, transaction said me that I need to generate xml-file for it (as in General notes for UI add-on mentioned).
But I have Solution Manager 7.0.1 and in MOPZ for this version I do not have option "install Add-on" as it written in Guide for ui add-on installation.
Could you please help me with advice how to generate xml-file for UI add-on installation on SolMan v.7.0.1?
If where is no way, but only to upgrade Solution Manager, maybe somebody could give me xml-file for your system (for NW 731) and I will change it to my needs, I will be very grateful!
Thanks in advance for any help!!!
Bets regards,
Natalia.

Hello Guru,
could you please help with my issue with Fiori Installation.
We want to install SAP Fiori Front-End (GW+UI) on the Sandbox system with SAP Netweaver 7.3.1. (SP14)
Gateway component (SAP GW CORE 200 SP10) was installed without any problems.
But I need to install UI-add-on (NW UI Extensions v1.0) and when I try to install it via SAINT, transaction said me that I need to generate xml-file for it (as in General notes for UI add-on mentioned).
But I have Solution Manager 7.0.1 and in MOPZ for this version I do not have option "install Add-on" as it written in Guide for ui add-on installation.
Could you please help me with advice how to generate xml-file for UI add-on installation on SolMan v.7.0.1?
If where is no way, but only to upgrade Solution Manager, maybe somebody could give me xml-file for your system (for NW 731) and I will change it to my needs, I will be very grateful!
Thanks in advance for any help!!!
Bets regards,
Natalia.

How to generate an Interupt for DMA transfer from Counter on NI-PCI-6602

dear guys:
      how to generate an Interupt for DMA transfer from Counter on NI-PCI-6602,and I have set the DMA and DMA_INT, and also the global interrupt register.
but there is no Interupt generated in the Interupt callback function.And when I have set the DMA_INT and global interrupt register ,and then read the relevant register,the relevant bit is also 0.
     I suspect there is an Interupt register contral, like the MITE, you must write the value to 0xc4 for opening .
     there is some codes In my enclosure .What can I do?
Attachments:
TEST.C ‏21 KB

dear Steven_T:
        the registers are In my enclosure ,if you have some ideas,please reply me first time.thank you !
Attachments:
PCI6602.pdf ‏818 KB

How to maintain master record for a user before assigning it to group?

Hi!
how to maintain master record for a user before assigning it to group?
I am in SQ03 and would like to assign user to a group, but SAP sais that my user has no user master data... where it is maintained?
Help will be appreciated,
Mindaugas

I guess it will be SU12 Transaction.
Thanks
Seshu

How To Generate Spool request for a SAP-Script form

How To Generate Spool request for a SAP-Script form

Hai Rahaman,
After getting the print preview of the SCRIPT.
Click On PRINT.
Buttom of the page one spool request will be generated by system.
Go to SP01.
You Can Find SPOOL Reqest Number.
Regards.
Eshwar.

How to generate test data for all the tables in oracle

I am planning to use plsql to generate the test data in all the tables in schema, schema name is given as input parameters, min records in master table, min records in child table. data should be consistent in the columns which are used for constraints i.e. using same column value..
planning to implement something like
execute sp_schema_data_gen (schemaname, minrecinmstrtbl, minrecsforchildtable);
schemaname = owner,
minrecinmstrtbl= minimum records to insert into each parent table,
minrecsforchildtable = minimum records to enter into each child table of a each master table;
all_tables where owner= schemaname;
all_tab_columns and all_constrains - where owner =schemaname;
using dbms_random pkg.
is anyone have better idea to do this.. is this functionality already there in oracle db?

Ah, damorgan, data, test data, metadata and table-driven processes. Love the stuff!
There are two approaches you can take with this. I'll mention both and then ask which
one you think you would find most useful for your requirements.
One approach I would call the generic bottom-up approach which is the one I think you
are referring to.
This system is a generic test data generator. It isn't designed to generate data for any
particular existing table or application but is the general case solution.
Building on damorgan's advice define the basic hierarchy: table collection, tables, data; so start at the data level.
1. Identify/document the data types that you need to support. Start small (NUMBER, VARCHAR2, DATE) and add as you go along
2. For each data type identify the functionality and attributes that you need. For instance for VARCHAR2
a. min length - the minimum length to generate
b. max length - the maximum length
c. prefix - a prefix for the generated data; e.g. for an address field you might want a 'add1' prefix
d. suffix - a suffix for the generated data; see prefix
e. whether to generate NULLs
3. For NUMBER you will probably want at least precision and scale but might want minimum and maximum values or even min/max precision,
min/max scale.
4. store the attribute combinations in Oracle tables
5. build functionality for each data type that can create the range and type of data that you need. These functions should take parameters that can be used to control the attributes and the amount of data generated.
6. At the table level you will need business rules that control how the different columns of the table relate to each other. For example, for ADDRESS information your business rule might be that ADDRESS1, CITY, STATE, ZIP are required and ADDRESS2 is optional.
7. Add table-level processes, driven by the saved metadata, that can generate data at the record level by leveraging the data type functionality you have built previously.
8. Then add the metadata, business rules and functionality to control the TABLE-TO-TABLE relationships; that is, the data model. You need the same DETPNO values in the SCOTT.EMP table that exist in the SCOTT.DEPT table.
The second approach I have used more often. I would it call the top-down approach and I use
it when test data is needed for an existing system. The main use case here is to avoid
having to copy production data to QA, TEST or DEV environments.
QA people want to test with data that they are familiar with: names, companies, code values.
I've found they aren't often fond of random character strings for names of things.
The second approach I use for mature systems where there is already plenty of data to choose from.
It involves selecting subsets of data from each of the existing tables and saving that data in a
set of test tables. This data can then be used for regression testing and for automated unit testing of
existing functionality and functionality that is being developed.
QA can use data they are already familiar with and can test the application (GUI?) interface on that
data to see if they get the expected changes.
For each table to be tested (e.g. DEPT) I create two test system tables. A BEFORE table and an EXPECTED table.
1. DEPT_TEST_BEFORE
     This table has all EMP table columns and a TEST_CASE column.
     It holds EMP-image rows for each test case that show the row as it should look BEFORE the
     test for that test case is performed.
     CREATE TABLE DEPT_TEST_BEFORE
     TESTCASE NUMBER,
     DEPTNO NUMBER(2),
     DNAME VARCHAR2(14 BYTE),
     LOC VARCHAR2(13 BYTE)
2. DEPT_TEST_EXPECTED
     This table also has all EMP table columns and a TEST_CASE column.
     It holds EMP-image rows for each test case that show the row as it should look AFTER the
     test for that test case is performed.
Each of these tables are a mirror image of the actual application table with one new column
added that contains a value representing the TESTCASE_NUMBER.
To create test case #3 identify or create the DEPT records you want to use for test case #3.
Insert these records into DEPT_TEST_BEFORE:
     INSERT INTO DEPT_TEST_BEFORE
     SELECT 3, D.* FROM DEPT D where DEPNO = 20
Insert records for test case #3 into DEPT_TEST_EXPECTED that show the rows as they should
look after test #3 is run. For example, if test #3 creates one new record add all the
records fro the BEFORE data set and add a new one for the new record.
When you want to run TESTCASE_ONE the process is basically (ignore for this illustration that
there is a foreign key betwee DEPT and EMP):
1. delete the records from SCOTT.DEPT that correspond to test case #3 DEPT records.
          DELETE FROM DEPT
          WHERE DEPTNO IN (SELECT DEPTNO FROM DEPT_TEST_BEFORE WHERE TESTCASE = 3);
2. insert the test data set records for SCOTT.DEPT for test case #3.
          INSERT INTO DEPT
          SELECT DEPTNO, DNAME, LOC FROM DEPT_TEST_BEFORE WHERE TESTCASE = 3;
3 perform the test.
4. compare the actual results with the expected results.
     This is done by a function that compares the records in DEPT with the records
     in DEPT_TEST_EXPECTED for test #3.
     I usually store these results in yet another table or just report them out.
5. Report out the differences.
This second approach uses data the users (QA) are already familiar with, is scaleable and
is easy to add new data that meets business requirements.
It is also easy to automatically generate the necessary tables and test setup/breakdown
using a table-driven metadata approach. Adding a new test table is as easy as calling
a stored procedure; the procedure can generate the DDL or create the actual tables needed
for the BEFORE and AFTER snapshots.
The main disadvantage is that existing data will almost never cover the corner cases.
But you can add data for these. By corner cases I mean data that defines the limits
for a data type: a VARCHAR2(30) name field should have at least one test record that
has a name that is 30 characters long.
Which of these approaches makes the most sense for you?

O/R mapping tool generates bad descriptors for CMP2.0

The O/R tool has many problems with EJB-CMP 2.0.
It generates bad ejb-jar.xml (misses the <cmr-field-type> tag, has the same relationship field included in both the <entity> tag and the <relationships> tag).
The worst part is that is generates bad TopLink descriptors!
I have numerous indirect 1-1 bean-pojo (plain old java object). When I have the 'tool' generate the ejb-jar.xml and deployment xml it generates all these relationships incorrectly.
The O/R 'tool' forces you to use transparent indirection for CMP 2.0 relationships; transparent indirection does not allow you to specify 'use method accessing'. Fine. But when I go to deploy the compiled jar, I get ALL sorts of errors complaining that:
EXCEPTION [TOPLINK-1] (TopLink (WLS CMP) - 9.0.3 (Build 423)): oracle.toplink.exceptions.DescriptorException
EXCEPTION DESCRIPTION: The attribute [addressToDesc] is not declared as type ValueHolderInterface, but its mapping uses indirection.
MAPPING: oracle.toplink.mappings.OneToOneMapping[addressToDesc]
DESCRIPTOR: Descriptor(...
ARGH!! What the heck do I need to do to get this 'tool' to work? It won't LET me use valueholder in EJB-CMP2.0, but then it complains when when I don't!?!?!
Frustrated,
Andrew

(from toplink support)
Andrew,
Hi there. I've performed some research regarding
your question, and it appears that having an
"automatic" 1:1 indirect relationship between an EJB
2.0 Entity Bean and a dependent Java object is not
currently supported by TopLink. Examining the
documentation, this non-support unfortunately isn't
documented. I have entered a feature request on your
behalf so that we might be able to support it in a
future major version of TopLink.
However, there are a couple of alternatives which
you can use:
1) We do support non-indirect 1:1 relationships
between an EJB 2.0 Entity Bean and a dependent Java
object. You could disable indirection, and maybe
make the relationship a batch read relationship so
that your performance will not be degraded.
2) You can write a concrete getter and setter, and
provide an instance variable on the entity bean for
your dependent object of type ValueHolderInterface.
Provide the private getters and setters for set and
get -Holder. Map this normally using TopLink, and
make sure Indirection is specified in the Mapping
Workbench.
IMPORTANT: TopLink will handle the normal
persistence management for this relationship,
however you will need to handle the merging back of
this object yourself (you had to do this in EJB 1.1
in TopLink as well). Luckily there are good docs on
this, and it's covered in detail - look at the
TopLink for WebLogic documentation : Runtime
Considerations > Managing dependent objects.
Personally, I would implement solution 1) with batch
reading on the attribute, because the dependent
object shouldn't be that "big" (otherwise it would
be an entity bean). This is an easier solution,
however you should investigate 2) fully yourself.

Conditon record for condition type

Hi
i create my condition record for my condition type( pr00, MWST,) in pricing in vk11 but when i create my condition type for output type, account determination and text determination i don't create the condition record in vk11 so how is itpossibile
Vinz

Hi Vinz,
For Account determination in SAP, Condition Technique is used. First we Create condition tables. Then we create the key combination/Access sequence(Sequence of condition tables created), then we create condition types(We have two standard condition types-- KOFI(With out controlling and KOFKWith Controlling). We assign these Condition types to the Procedure and the procedure is assigned to the billing types. One of the combinations is " Application/sales org/chart of accounts/ condition type/acount assignment group of customer/acct assign group of mat/ account key/gl account."This combination is nothing but access sequence and this is assigned to a condition type. In "VKOA" we specify the system whats the G/L Account to be picked up. This acts as a condition record. Account keys are assigned to each condition type in pricing procedure. Based on the account key of particular pricing condition type(Ex: PR00ERL) ,system will pick up the respective condition type from "VKOA". Kindly please let me know If you need any more Information on this,
Regards,
Ram Pedarla
Edited by: RamPedarla on Mar 17, 2010 5:59 PM

Generating an IDOC for Message type PROJECT in Change pointer?

Hi,
I am trying to generate an IDOC. for the Message Type PROJECT(Actually this msg. type PROJECT is for BAPI method) in CHANGE POINTERS but it is possible Error is coming, is there any other method to use the message type in change pointer technic.
Thanks,
Vinayak,
Message was edited by: vinayaga sundaram

Hi Vinay,
Had a similar requirement few days back..
What we did was to do a multimapping of 1:N where N = N1 and N2, N1 is the Idocs which you are doing today, N2 is the set of invalid records...
Now we have written this as a file and then created another interface which will pick the file and based on the name of file we decided the To address. We have used mail package and this interface (file to mail ) was made as a generic one so that it can be used across many interfaces...
filename and To address relationship was maintained as a value mapping in ID... You can have a thought of this approach and try to send the invalid records as a mail rather than alert.
Regards
Suraj

How to generate bad records for varchar2 type

Similar Messages

Maybe you are looking for