Fields in infocube and DSO?

Hi Experts,
                 I need some information regarding maximum number of fields in infocube and DSO?
     According to my knowledge, in Infocube - characteristics --248
                                                                         Keyfigures--233
                                                In DSO - key fields - 16
                                                              Data fields -749
             I thought dat DSO has 3 tables. maximum number of columns in a table is 255. So 255 * 3( 3tables in DSO) is 755.
                                             755(total fields)-16(key fields)= 749(data fields).
Is it correct?can anyone clarify my doubt pls?
Thanks in Advance
Jani Sk.

Hi,
In cube , table consists of 255 columns, in which 6 are internally used by SAP,16 for dimensions and the remaining 233 are for Key figures. Each dimension key connected to 248 master data tables at max through dimension and SID tables.So, We can analyse the data at 16*248 dimensions.
ODS/DSO is a two dimensional flat structure.It consists of total 1024 columns, out of which 16 are used for Key fields and remaining 1000 are for data fields.
Thanks,
Sandeep

Similar Messages

How to get the size of all InfoCubes and DSO's?

Hi all,
My client wants a complete list of all InfoCubes and DSO's in terms of size (no records but KB). This list of the Cubes / DSO's gives us a picture of the used storage per Area and can be charged. Iu2019ve seen some threats and looked into the possibilities of ST14 and DB02. ST14 provides the ideal list but with a restriction for the top 30 InfoCubes and the top 30 DSO's. Does anyone know how to get such a list for all InfoCubes and DSO's?
Thnx in advance,
Henk.

Hello Henk,
while I am searching for some performance problems in our BI, I tried to look through the new DB02 of BI 7.0. And there is a function which helps a lot creating lists of Cube, DSOs and so on:
Start DB02
On the left side find SPACE -> Additional Functions -> BW Analysis
A Doubleclick will give you a broad survey of the current memory disposition regarding BI/BW objects.
In the BW Area "Cubes & related objects" you can find Infocube E- and F-Facttable. Depending on the Compressed state of your cubes you will find more data in E or F. Just doubleclick on one of these Entries. In my environment currently F-Tables are more effective.
You will then get a list of all Infocubes with size.
You will have to this for E and F Tables and some up over the Infocubes. But, because this will show only the Cubes and not the partitions of the cube it will be much easier to handle than DB02OLD.
Perhaps this helps, because you did not mention your BW/BI release.
Kind regards,
Jürgen

Load data to a modified InfoCube and ODS used in Production

Hi,
I have added few fields (InfoObjects) to the cube(s) and DSOs in BI 7.0. These Cubes and DSOs are BW 3.5 Objects and are in-use in Production.
My question: After I transport this new/enhanced InfoCube and DSO from Dev/Qua to Production, how to retrieve the old data from original Cube/DSO and populate data to new fields at DSO and Cube level.
Please advise.
Thanks,
~S

Hi Siddhartha Nayak
As ur enhanced the IC & ODS which r 3.x objects, i guess u havn't used the remodeling tool. Then u have to follow the old procedure to enhancing the cube.
Create a copy cube , Delete the contents of existing cube, enhance it & load the data to existing cube back from copy cube.
Same thing u have to follow in ur case also.
Regards,
Shaiksha.

How to Map the Unit field in case of DSO and INFOCUBE

Dear Experts,
I have a issue ,Please help me to solve this
I have DSO as provider ,
And, i have to map transformations btw the Datasource and DSO.
In generic Data source, i have unit fields like BASME,MEINS (Quantity units) & STWAE (currency field)
and normal Quantity fields like KWMNG,OAUME(quantity related),OAUWE (value related).
In DSO data fields as Key figure info objects like 0Quantity (which have 0Unit as unit of measure) and some other key figures which have there respective unit of measure in info object definition.
So you Please tell me how to map the Quantity ,Amounts, unit fields to key figures that we have.
(How it will be for both DSO and Info cube is there any difference?)
Edited by: AnjunathNaidu on Jan 18, 2012 1:20 PM

Navasamol ,
If it is works ,will u please tell me what is the difference ,if the transformations btw data source and DSO and
what is the difference btw data source and info cube and btw DSO to Infocube or cube to cube .
And i have seen the Quantity fields and there respective unit fields are mapped directly to key figure info object
in case of Info cube . Its working fine .
If only 1:1 mapping allowed in DSO data fields key figures and there respective unit of measure characteristic.
why this difference btw DSO and Info cube can any one explain me in detail.
Expecting your valuable suggestions.
Thanks & Regards,
Anjunath Naidu
Edited by: AnjunathNaidu on Jan 18, 2012 4:05 PM

Infocube and ODS populated with DATA (need to add one more field?)

Hi,
If infocube and ODS have been populated with data for past 3 months. Then we need to add one more field to this cube. What is the impact? Please advise.
The following is my understanding. Please correct me if I am wrong.
1) Need to delete content of ODS and infocube.
2) insert the new field at ODS and infocube.
3) reload the data into ODS and infocube.
Is there a way that the current data need not be deleted.
Just add in this new field and only subsequent month, infocube will have this new field? Please advise what is the best approach without affecting existing data.

Hi,
Siggi is right. You dont need to delete the previously loaded data to CUBE or ODS. The only catch is that, your new field will be empty as far as history is concerned. But so long as you did map it to the datasource and the datasource is able to fill it up, then your new field will now have value for incoming DELTA Updates.
Addition of a field is not that complicated compared to deletion of a field from CUBE or ODS.
--Jkyle

Regarding Info cube and DSO

Hi,
Generally reporting will be done on Info Cube rather than DSO.
Suppose If we assign the same data source to Info Cube and DSO then both contains the same data.
Info cube have additive and aggregated functionality where DSO have the overwrite functionality .
Are we using cube for this functionality only ?
What about the Dimensions in Cube how they differ from data fields and key fields in DSO when we are developing same Bex Report on both ?
Please advice me .
Thanks in advance.
Thanks & Regards,
Ramnaresh.p

It is hard to compare Cube and DSO.
Both thier own usage.
1. InfoCube is always additive, while DSO supports overwrite functionality.
2. In InfoCube, combination of all the characteristic value is a Key in the Fact Table, while in ODS, you can specify your own Key Fields based on which you want to generate unique record in the DSO.
3. DSO supports many delta modes like D, R, N, X, after image, before image, while cube does not support all the modes. You can not delete the record based on the key from the cube by just loading the data. While DSO automaitcally deletes the record from active table and generates the reverse entry for Cube.
4. DSO is a flat structure and therefore, it is used to store information at detail level, while cube is used to store information at aggregated level.
So both the structures are very much different from each other. One can replace other at some places, but both the objects have thier own functionality.
- Danny

The table for storing data for infocube and ODS

Hi all:
could you please tell me how to find the table for storing data for infocube and ODS?
thank you very much!

Hi Jingying Sony,
To find tables for any infoprvider go to SE11.
In database table field enter the following
Cube -
Has fact table and dimension table
For customized cube - ie cube names not starting with ' 0 '
Uncompressed Fact table - /BIC/F<infocubename>
Compressed fact table - /BIC/E<infocubename>
Dimension table - /BIC/D<infocubename>
For standard cube - ie cube names starting with ' 0 '
Uncompressed Fact table - /BI0/F<infocubename>
Compressed fact table - /BI0/E<infocubename>
Dimension table - /BI0/D<infocubename>
Click on display.
For DSO,
For standard DSO active table- /BI0/A<DSO name>00.
You use 40 for new table.
Click on display.
For customized DSO use- /BIC/A<DSO name>00.
An easier way is in the database table field, write the name of the cube/DSO preceeded and followed by ' * ' sign. Then press F4 . It shall give you the names of the available table for that info provider.
Double click on the name and choose display.
Hope this helps,
Best regards,
Sunmit.

Transformation between DS and DSO missing Non-cumulative KYF

Hi SDN,
I installed the business content for CML, and am working with 0CML_DELTA_CAP datasource. I would like to create a transformation between this datasource and DSO 0CML_O03.
By default, when you install the CML business content, the datasources use the 3.x dataflow concept (transfer rules, infosources, and update rules).
I would like to use the 7.x dataflow concept and created a transformation between the 0CML_DELTA_CAP datasource and the 0CML_O03 DSO. In the transformation, it is missing the fields 0CML_B330, 0CML_B340, 0CML_B360, 0CML_B380 in the datatarget. These key figures are non-cumulative with NCum Value change (0CML_B330 uses 0CML_B331 as value change). The value change key figures show up in the transformation, but the non-culmulative key figures do not.
Does anyone have any ideas why the non-cuml. kyf are not showing up in the transformation?
Thanks,

Hi Brendon,
The non- cumulative key figures are not mapped in the transformation. Only the 'Inflow' and 'Outflow' key figures for the non- cumulative key figure are mapped.
You can check the property for the non- *** KF in RSD1, where you would find the corresponding inflow and outflow kf. If both of these are mapped in the transformation, the non- *** kf would calculate the value in the report in which it is included as:
Non-*** KF value = Inflow value - Outflow value.
Hope this helps.
Regards,
Abhishek.

Filled fields become blank in DSO change log

Hi experts,
I find an unusual behavior in DSO activation.
For some records for which I find in PSA, new data table (and in debug also!!!) correct data, when the request is activated I find in change log table all characteristic fields empty; the key fields and key figure fields are ok and correct in all tables.
It happen randomly for some orders and for a few requests.
It happen when I have one storno record, for example:
PSA (order, item, customer, material, storno, quantity)
10000, 10, AAA, YYY, , 25
10000, 10, AAA, YYY, X, -25
DEBUG (order, item, customer, material, storno, quantity)
10000, 10, AAA, YYY, , 25
10000, 10, AAA, YYY, X, -25
CHANGE LOG (order, item, customer, material, storno, quantity)
10000, 10, AAA, YYY, , 25
10000, 10, , , X, -25
ACTIVE DATA (order, item, customer, material, storno, quantity)
10000, 10, AAA, YYY, 25
In some other cases:
ACTIVE DATA (order, item, customer, material, storno, quantity)
10000, 10, , , -25
Have you some ideas? It is very strange.
We are on a 7.0 BW system, but with 3.5 data flow (update rule).
Thanks in advance.

Vito,
This happens some times...
1. Did you transport any change to this DSO where characteristics were added and are these the ones that are blank...
When this happens - see if you can clear the change log ( if this is an option ) and then reactivate the cube.
Also there is a program to regenerate the activation program, I am not able to locate this - but then usually reactivating the ODS will usually clear this issue because it regenerates the activation program.

Data fields not filled in DSO Activation

Dear All,
I have written an End routine to extract data into a DSO to fill some data fields. The End routine will perform a lookup on another DSO and modifies the records of the result_package. The data fields are characteristics and hence in the transformation, they are set to No Transformation.
When I extracted the data into DSO, the new table has all the data fields correctly filled. But, after activating the request, all the data fileds data are erased. However, the keyfields data is still available in the Active table.
Can you please help me on this.
Thanks,
Srinivas

Hi Srinivas
I have faced the same issue.Data was coming till new table,but after activation fields were getting
blank.
There is no necessity for doing a dummy mapping. In the transformation screen you will be having an ikon near to the delete
routine symbol with an arrow symbol
similar to select all and unselect all, just clikc on it and then mention the setting as Update all the target fields need to be populated.
This will solve the issue, if it is not solved, then you can make a direct mapping to any of the field in the source, it need not be the
exact field in the target.
Thanks,
Saveen Kumar

Multiple rows in BI Infocube/or DSO for one row in source system

Hi Gurus,
I have a typical scenario where in I have a ztable in R/3 system and it contains some custome transaction data.
The business scenario wants it to split into multiple records in BI ( ofcourse keys for each records in BI would be unique). Either infocube or DSO can be used to store the data in BI.
Is it possible to do that. As far as my knowledge goes( I have limited BI exposure) one record from source system ( read row) is transformed into one record ( row) in BI in simple transformation.
Please give me some rough idea if its possible how can we achieve it.
I know we can write an ABAP program and create a ztable to do it and use the ztable as source for incube/dso. But I want to use this as last option.
Thanks
Sumit

Hi,
An ODS will be better.
Use a start routine.
data-package --> package2
create your own package with your rules.
update.insert.modify.append....
package2 --> data_package
and from 1 row, you create n row as your rules would like..
Regards,

Infocubes and info objects

Hi guys,
i'm new to BI. can any one differentiate between Infocubes and info objects..
please be a bit specific.....

Hi,
An InfoCube describes (from an analysis point of view) a self-contained dataset, for example, for a business-orientated area. You analyze this dataset in a BEx query.
An InfoCube is a set of relational tables arranged according to the star schema: A large fact table in the middle surrounded by several dimension tables.
Use
InfoCubes are filled with data from one or more InfoSources or other InfoProviders. They are available as InfoProviders for analysis and reporting purposes.
Structure
The data is stored physically in an InfoCube. It consists of a number of InfoObjects that are filled with data from staging. It has the structure of a star schema.
The real-time characteristic can be assigned to an InfoCube. Real-time InfoCubes are used differently to standard InfoCubes.
ODS versus Info-cubes in a typical project scenario
ODS
why we use ods?
why is psa & ods nessasary
InfoObject: Basic building block of BW.. ( Its like a field )
Definition
Business evaluation objects are known in BI as InfoObjects. They are divide into characteristics (for example, customers), key figures (for example, revenue), units (for example, currency, amount unit), time characteristics (for example, fiscal year) and technical characteristics (for example, request number).
Use
InfoObjects are the smallest units of BI. Using InfoObjects, information is mapped in a structured form. This is required for constructing InfoProviders.
InfoObjects with attributes or texts can themselves also be InfoProviders (if in a query).
Regards,
Ram.

Multiprovider on top of Infocube and ods

Hi,
I'm just wondering, I would like to create an Multiprovider on top of infocube and ods. While creating multirovider I can able to see my infocube but in ODS tab I'm not getting ODS which I need to consider.
I've gone through all available ODS's in ODS tab while creating Multiprovider but my ODS is coming here.
I'm working on BW 3.5 Version.
Advance thanks you very much.

Hi,
Just check weather u have any keyfigur in ur DSO or not. If not just add one keyfigur in your ODS and activate it and then try to look for it in multiprovider.
Hope it will help you.
Thanks
Mayank

DYNPRO_WRITE_FAILED on every InfoObject, InfoCube, Characteristic, DSO

I met a fatal error: DYNPRO_WRITE_FAILED when I use "Display Data" function on any InfoObject or InfoCube or DSO or characteristic in my InfoArea. I use sm50, sm51 to see that server always has 3 pink error process running (1 is DIA, 2 are BGD).
Some online article mentions that DYNPRO_WRITE_FAILED might be related to memory, buffer issues. And I use st22 to view the application failure log. It told me to terminate the ABAP program with ID: "GPDAV......"
I enter running process screen via sm50, and use "cancel without core", or "end session" or "cancel program". But whatever I tried, those 3 process keep in pink error status.
Can anyone help me out. How can I clean up those error processes on the server to avoid this DYNPRO_WRITE_FAILED error?
Thanks for your help in advance.
Regards,
Roy Zhou

Hi, Suman
Thanks for your suggestion.
I use DB02 to see the Database overview. Totally 80GB space, 71% is used. Looks like 16GB free space are good. In fact, I am not sure it is memory issue or not.
I use st11 to get the dev_w1 log, there is one section describes the DYNPRO_WRITE_FAILED error information. But I can not figure out what that means. Could you please take look my log to see what is the better solution to avoid this DYNPRO_WRITE_FAILED error. Because the result of DTP, transform result are all in green status in the monitor screen. But when I choose "Display Data" menu item, then the following errors occur:
A Wed Jul 20 00:57:19 2011
A GENER starting inline generation: GPDAW7NZRD7O8K2ZW71UFNWU4MC (reason: program touched by own LUW).
C *** ERROR => OCI-call 'OCILobWrite' failed with rc=1691
[dboci.c      2561]
C *** ERROR => ORA-1691 occurred when writing to a LOB
[dbsloci.c    10366]
C sc_p=0000000012770AE8,no=71,idc_p=000000001278F6E0,con=0,act=1,slen=133,smax=2048,#vars=4,stmt=0000000035C35B90,table=DYNPSOURCE
C prep=0,lit=0,nsql=0,lobret=1,#exec=1,dbcnt=1,upsh_p=0000000000000000,ocistmth_p=0000000039DB1B28
C IN : cols=3,rmax=1,xcnt=1,rpc=0,rowi=0,rtot=1,upto=-1,rsize=88,vmax=64,bound=1,iobuf_p=00000000326D9C40,vda_p=000000003546BA70
C       lobs=1,lmax=4,lpcnt=0,larr=0000000035D01880,lcurr_p=0000000000000000,rret=0
C OUT: cols=1,rmax=152,xcnt=0,rpc=0,rowi=0,rtot=0,upto=0,rsize=404,vmax=256,bound=0,iobuf_p=0000000000000000,vda_p=00000000361E6C90
C       lobs=1,lmax=4,lpcnt=1,larr=0000000035D03380,lcurr_p=0000000035D03380,rret=1
C INSERT INTO "DYNPSOURCE" (PROGNAME, DYNPNUMBER, R3STATE, "FIELDINFO" ) VALUES ( :A0 , :A1 , 'A', :A2\
C   ) RETURNING "FIELDINFO" INTO :A3;
Y *** ERROR => DY-SRC_WRITE COMMIT: error len=169092, rc=1 !! [dgdynp.c     1394]
Y *** ERROR => SQL-ERROR: 0 "" [dgdynp.c     1401]
A TH VERBOSE LEVEL FULL
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.
A ** RABAX: level LEV_RX_ROLLBACK entered.
A
A Wed Jul 20 00:57:20 2011
A ** RABAX: level LEV_RX_ROLLBACK completed.
A ** RABAX: level LEV_RX_DB_ALIVE entered.
A ** RABAX: level LEV_RX_DB_ALIVE completed.
A ** RABAX: level LEV_RX_HOOKS entered.
A ** RABAX: level LEV_RX_HOOKS completed.
A ** RABAX: level LEV_RX_STANDARD entered.
A ** RABAX: level LEV_RX_STANDARD completed.
A ** RABAX: level LEV_RX_STOR_VALUES entered.
A ** RABAX: level LEV_RX_STOR_VALUES completed.
A ** RABAX: level LEV_RX_C_STACK entered.
A ** RABAX: level LEV_RX_C_STACK completed.
A ** RABAX: level LEV_RX_MEMO_CHECK entered.
A ** RABAX: level LEV_RX_MEMO_CHECK completed.
A ** RABAX: level LEV_RX_AFTER_MEMO_CHECK entered.
A ** RABAX: level LEV_RX_AFTER_MEMO_CHECK completed.
A ** RABAX: level LEV_RX_INTERFACES entered.
A ** RABAX: level LEV_RX_INTERFACES completed.
A ** RABAX: level LEV_RX_GET_MESS entered.
A ** RABAX: level LEV_RX_GET_MESS completed.
A ** RABAX: level LEV_RX_INIT_SNAP entered.
A ** RABAX: level LEV_RX_INIT_SNAP completed.
A ** RABAX: level LEV_RX_WRITE_SYSLOG entered.
A ** RABAX: level LEV_RX_WRITE_SYSLOG completed.
A ** RABAX: level LEV_RX_WRITE_SNAP entered.
A ** RABAX: level LEV_SN_END completed.
A ** RABAX: level LEV_RX_SET_ALERT entered.
A ** RABAX: level LEV_RX_SET_ALERT completed.
A ** RABAX: level LEV_RX_COMMIT entered.
A ** RABAX: level LEV_RX_COMMIT completed.
A ** RABAX: level LEV_RX_SNAP_SYSLOG entered.
A ** RABAX: level LEV_RX_SNAP_SYSLOG completed.
A ** RABAX: level LEV_RX_RESET_PROGS entered.
A ** RABAX: level LEV_RX_RESET_PROGS completed.
A ** RABAX: level LEV_RX_STDERR entered.
A Wed Jul 20 00:57:20 2011
A
A Generating ABAP Program GPDAW7NZRD7O8K2ZW71UFNWU4MC             .
A Source ???????????????????????????????????????? Line 0.
A Error Code DYNPRO_WRITE_FAILED.
A Module $Id: //bas/700_REL/src/krn/dyng/dgdynp.c#4 $ SAP.
A Function dg_wrdys Line 499.
A ** RABAX: level LEV_RX_STDERR completed.
A ** RABAX: level LEV_RX_RFC_ERROR entered.
A ** RABAX: level LEV_RX_RFC_ERROR completed.
A ** RABAX: level LEV_RX_RFC_CLOSE entered.
A ** RABAX: level LEV_RX_RFC_CLOSE completed.
A ** RABAX: level LEV_RX_IMC_ERROR entered.
A ** RABAX: level LEV_RX_IMC_ERROR completed.
A ** RABAX: level LEV_RX_DATASET_CLOSE entered.
A ** RABAX: level LEV_RX_DATASET_CLOSE completed.
A ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.
A ** RABAX: level LEV_RX_RESET_SHMLOCKS completed.
A ** RABAX: level LEV_RX_ERROR_SAVE entered.
A ** RABAX: level LEV_RX_ERROR_SAVE completed.
A ** RABAX: level LEV_RX_ERROR_TPDA entered.
A ** RABAX: level LEV_RX_ERROR_TPDA completed.
A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
A ** RABAX: level LEV_RX_END entered.
A ** RABAX: level LEV_RX_END completed.
A ** RABAX: end RX_GOTO_GENEXIT
A TH VERBOSE LEVEL FULL
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.
A ** RABAX: level LEV_RX_ROLLBACK entered.
A ** RABAX: level LEV_RX_ROLLBACK completed.
A ** RABAX: level LEV_RX_DB_ALIVE entered.
A ** RABAX: level LEV_RX_DB_ALIVE completed.
A ** RABAX: level LEV_RX_HOOKS entered.
A ** RABAX: level LEV_RX_HOOKS completed.
A ** RABAX: level LEV_RX_STANDARD entered.
A ** RABAX: level LEV_RX_STANDARD completed.
A ** RABAX: level LEV_RX_STOR_VALUES entered.
A ** RABAX: level LEV_RX_STOR_VALUES completed.
A ** RABAX: level LEV_RX_C_STACK entered.
A ** RABAX: level LEV_RX_C_STACK completed.
A ** RABAX: level LEV_RX_MEMO_CHECK entered.
A ** RABAX: level LEV_RX_MEMO_CHECK completed.
A ** RABAX: level LEV_RX_AFTER_MEMO_CHECK entered.
A ** RABAX: level LEV_RX_AFTER_MEMO_CHECK completed.
A ** RABAX: level LEV_RX_INTERFACES entered.
A ** RABAX: level LEV_RX_INTERFACES completed.
A ** RABAX: level LEV_RX_GET_MESS entered.
A ** RABAX: level LEV_RX_GET_MESS completed.
A ** RABAX: level LEV_RX_INIT_SNAP entered.
A ** RABAX: level LEV_RX_INIT_SNAP completed.
A ** RABAX: level LEV_RX_WRITE_SYSLOG entered.
A ** RABAX: level LEV_RX_WRITE_SYSLOG completed.
A ** RABAX: level LEV_RX_WRITE_SNAP entered.
A ** RABAX: level LEV_RX_WRITE_SNAP completed.
A ** RABAX: level LEV_RX_SET_ALERT entered.
A ** RABAX: level LEV_RX_SET_ALERT completed.
A ** RABAX: level LEV_RX_COMMIT entered.
A ** RABAX: level LEV_RX_COMMIT completed.
A ** RABAX: level LEV_RX_SNAP_SYSLOG entered.
A ** RABAX: level LEV_RX_SNAP_SYSLOG completed.
A ** RABAX: level LEV_RX_RESET_PROGS entered.
A ** RABAX: level LEV_RX_RESET_PROGS completed.
A ** RABAX: level LEV_RX_STDERR entered.
A ** RABAX: level LEV_RX_STDERR completed.
A ** RABAX: level LEV_RX_RFC_ERROR entered.
A ** RABAX: level LEV_RX_RFC_ERROR completed.
A ** RABAX: level LEV_RX_RFC_CLOSE entered.
A ** RABAX: level LEV_RX_RFC_CLOSE completed.
A ** RABAX: level LEV_RX_IMC_ERROR entered.
A ** RABAX: level LEV_RX_IMC_ERROR completed.
A ** RABAX: level LEV_RX_DATASET_CLOSE entered.
A ** RABAX: level LEV_RX_DATASET_CLOSE completed.
A ** RABAX: level LEV_RX_RESET_SHMLOCKS entered.
A ** RABAX: level LEV_RX_RESET_SHMLOCKS completed.
A ** RABAX: level LEV_RX_ERROR_SAVE entered.
A ** RABAX: level LEV_RX_ERROR_SAVE completed.
A ** RABAX: level LEV_RX_ERROR_TPDA entered.
A ** RABAX: level LEV_RX_ERROR_TPDA completed.
A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
A ** RABAX: level LEV_RX_END entered.
A ** RABAX: level LEV_RX_END completed.
A ** RABAX: end no http/smtp
A ** RABAX: end RX_GOTO_RABAX
A
A Wed Jul 20 00:57:46 2011
A GENER starting inline generation: GPDAW7O21HQNLXZ3FC8HHWC8YXW (reason: program touched by own LUW).
C
C Wed Jul 20 00:57:47 2011
C *** ERROR => OCI-call 'OCILobWrite' failed with rc=1691
[dboci.c      2561]
C *** ERROR => ORA-1691 occurred when writing to a LOB
[dbsloci.c    10366]
C sc_p=0000000012770AE8,no=71,idc_p=000000001278F6E0,con=0,act=1,slen=133,smax=2048,#vars=4,stmt=0000000035C35B90,table=DYNPSOURCE
C prep=0,lit=0,nsql=0,lobret=1,#exec=1,dbcnt=1,upsh_p=0000000000000000,ocistmth_p=0000000039DB1B28
C IN : cols=3,rmax=1,xcnt=1,rpc=0,rowi=0,rtot=1,upto=-1,rsize=88,vmax=64,bound=1,iobuf_p=00000000326D9C40,vda_p=000000003546BA70
C       lobs=1,lmax=4,lpcnt=0,larr=0000000035D01880,lcurr_p=0000000000000000,rret=0
C OUT: cols=1,rmax=152,xcnt=0,rpc=0,rowi=0,rtot=0,upto=0,rsize=404,vmax=256,bound=0,iobuf_p=0000000000000000,vda_p=00000000361E6C90
C       lobs=1,lmax=4,lpcnt=1,larr=0000000035D03380,lcurr_p=0000000035D03380,rret=1
C INSERT INTO "DYNPSOURCE" (PROGNAME, DYNPNUMBER, R3STATE, "FIELDINFO" ) VALUES ( :A0 , :A1 , 'A', :A2\
C   ) RETURNING "FIELDINFO" INTO :A3;
Y *** ERROR => DY-SRC_WRITE COMMIT: error len=208620, rc=1 !! [dgdynp.c     1394]
Y *** ERROR => SQL-ERROR: 0 "" [dgdynp.c     1401]
A TH VERBOSE LEVEL FULL
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX entered.
A ** RABAX: level LEV_RX_PXA_RELEASE_MTX completed.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER entered.
A ** RABAX: level LEV_RX_COVERAGE_ANALYSER completed.
A ** RABAX: level LEV_RX_ROLLBACK entered.
A ** RABAX: level LEV_RX_ROLLBACK completed.
A ** RABAX: level LEV_RX_DB_ALIVE entered.
A ** RABAX: level LEV_RX_DB_ALIVE completed.
A ** RABAX: level LEV_RX_HOOKS entered.
A ** RABAX: level LEV_RX_HOOKS completed.
A ** RABAX: level LEV_RX_STANDARD entered.
A ** RABAX: level LEV_RX_STANDARD completed.
A ** RABAX: level LEV_RX_STOR_VALUES entered.
A ** RABAX: level LEV_RX_STOR_VALUES completed.
A ** RABAX: level LEV_RX_C_STACK entered.
A ** RABAX: level LEV_RX_C_STACK completed.
A ** RABAX: level LEV_RX_MEMO_CHECK entered.
A ** RABAX: level LEV_RX_MEMO_CHECK completed.
A ** RABAX: level LEV_RX_AFTER_MEMO_CHECK entered.
A ** RABAX: level LEV_RX_AFTER_MEMO_CHECK completed.
A ** RABAX: level LEV_RX_INTERFACES entered.
A ** RABAX: level LEV_RX_INTERFACES completed.
A ** RABAX: level LEV_RX_GET_MESS entered.
A ** RABAX: level LEV_RX_GET_MESS completed.
A ** RABAX: level LEV_RX_INIT_SNAP entered.
A ** RABAX: level LEV_RX_INIT_SNAP completed.
A ** RABAX: level LEV_RX_WRITE_SYSLOG entered.
A ** RABAX: level LEV_RX_WRITE_SYSLOG completed.
A ** RABAX: level LEV_RX_WRITE_SNAP entered.
A ** RABAX: level LEV_SN_END completed.
A ** RABAX: level LEV_RX_SET_ALERT entered.
A ** RABAX: level LEV_RX_SET_ALERT completed.
A ** RABAX: level LEV_RX_COMMIT entered.
A ** RABAX: level LEV_RX_COMMIT completed.
A ** RABAX: level LEV_RX_SNAP_SYSLOG entered.
A ** RABAX: level LEV_RX_SNAP_SYSLOG completed.
A ** RABAX: level LEV_RX_RESET_PROGS entered.
A ** RABAX: level LEV_RX_RESET_PROGS completed.
A ** RABAX: level LEV_RX_STDERR entered.
A Wed Jul 20 00:57:47 2011
A
A Generating ABAP Program GPDAW7O21HQNLXZ3FC8HHWC8YXW             .
A Source ???????????????????????????????????????? Line 0.
A Error Code DYNPRO_WRITE_FAILED.
A Module $Id: //bas/700_REL/src/krn/dyng/dgdynp.c#4 $ SAP.
A Function dg_wrdys Line 499.
A ** RABAX: level LEV_RX_STDERR completed.
A ** RABAX: level LEV_RX_RFC_ERROR entered.
Thanks for your help in advance.
Regards,
Roy Zhou

Issue to make mandatory field(SELD/BBD and Date of manufactor)in migo for particular Material type and material Number starting with'1' series.

Hi friend,
i have issue regarding mandatory self life field (SELD/BBD and Date of manufactor)in migo for Batch Tab for particular Material start with '1' Series and material type.
i want to make mandatory above field during GR from migo..any one let me know exit or badi for that to full fill this goal..
Regard's,
shaikh Khalid.

Hi Shaikh
First of all Thread is not closed seconldy as a good practice if you have resolved your issue kindly document it here so that it may help someone in future
Nabheet

Fields in infocube and DSO?

Similar Messages

Maybe you are looking for