Relation b/w PRPS and RPSCO tables

Hi PS Experts,
What is the Relation b/w PRPS and RPSCO tables
PRPS : WBS (Work Breakdown Structure) Element Master Data
RPSCO : Project info database: Costs, revenues, finances
Thanks in Advance,
Regards,
sudharsan.

Hello Sasikanth Thank u for ur information,
and i need some more information, am working on abap, now i got a requirement in PS,
i want 2 calculate the values like Planned Revenue, Planned Cost, Actuall Rev, Actuall Cost, Actuall Billing, Revenue Taken, Cost Taken, BNS and SNB.
based on i/p parameters: Company Code, Fiscal year and month.
pls let me know how to calculate the above values, its very urgent for me.
Thanks in advance,
sudharsan.

Similar Messages

Relationship between PRPS and FPLT table

How to arrive to a billing plan in FPLT table with project ID or WBS ID in PRPS table.
Thanks,
Vaishnavi

Hi
I hope there is no common element in both tables..extract the mile stone data from FPLT and MLST tables and then WBS element data from PRPS and MLST tables (first two gives the mile stone and next two tables gives the WBS element to which mile stone is attached)..
thanks

Link between Prps and Vbap table

Hi all,
How can i link PRPS and VBAP table .
Please suggest.
Thanks and regrads
Neha Kapoor

hi,
neha try this.
PRPS-PSPNR = VBAP-PS_PSP_PNR
rgds
anver

Sy-tabix in relation to LOOP AT and READ TABLE

Hi All,
As per SAP documentation,
1) While looping through an internal table (LOOP AT), sy-tabix contains the index number of current row(for standard and sorted tables)
2)When successfully reading from an internal table(READ TABLE), sy-tabix is set to the index of the result row.
But what happens when READ TABLE is used while looping through another internal table?
i.e. Loop at TAB1...
write sy-tabix.
READ TABLE TAB2...
write sy-tabix.
endloop.
If we are looping through 1st row of TAB1 and the result of read statement is found in 3rd row of TAB2, I expected that sy-tabix before READ would be 1 and after the READ be 3.
But, I found that sy-tabix remains unchanged at 1. Can someone expalin why?
Thanks,
Jagan

Hi
If after reading the table TAB2 the system variable SY-TABIX has still the previous value, that menas the READ TABLE fails or it was read the first record of TAB2.
After READ TABLE TAB2 try to check the SY-SUBRC:
LOOP AT TAB1.
   WRITE: / 'TAB1 index:', SY-TABIX.
   READ TABLE TAB2 .........
   IF SY-SUBRC = 0.
     WRITE: 'TAB2 index:', SY-TABIX.
Try this:
DATA: BEGIN OF ITAB OCCURS 0,
        FIELD1,
      END   OF ITAB.
DATA: BEGIN OF ITAB2 OCCURS 0,
        FIELD1,
      END   OF ITAB2.
DATA: INDEX TYPE I.
DO 10 TIMES.
APPEND ITAB.
ENDDO.
DO 10 TIMES.
APPEND ITAB2.
ENDDO.
LOOP AT ITAB.
WRITE: / 'ITAB:', SY-TABIX.
INDEX = SY-TABIX + 2.
READ TABLE ITAB2 INDEX INDEX.
IF SY-SUBRC = 0.
    WRITE: 'ITAB2:', SY-TABIX.
ENDIF.
ENDLOOP.
Max

Relation between Mara, CAWN and CABN table.

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

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

Unable to insert records in PRPS and PROJ tables.

I want to insert entries in PROJ and PRPS tables with new company code.
I am selecting entries with existing company code and changing old co. code to new co. code in work area.
Then I am using insert PRPS from work area in the same way inserting in PROJ.
Please help, why insert statement is not working with these tables..

I hope you are in a sandbox system.
The internal and primary key is PSPNR, and this key is associated with an internal range number. If you don't want to use program, you have to get yourself the next number for PROJ and each PRPS, then you MUST insure that related objects like OBJNR the CO object number is adjusted (PR or PD + internal number/) else you will incur severe problem with your database. You MUST insure that other unique indexes are respected PSPID, etc.
*The correct way is reached via BAPI or Batch Input/Call Transaction*
For BTC or call transaction just record via [SHDB|https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=shdb&adv=false&sortby=cm_rnd_rankvalue] a single run with [CJ2D transaction|https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=cj2d+transaction&adv=false&sortby=cm_rnd_rankvalue].
BAPI suitable are :
- [BAPI_PS_INITIALIZATION|https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=bapi_ps_initialization&adv=false&sortby=cm_rnd_rankvalue] to start the job
- to read the model use BAPIs like [BAPI_PROJECTDEF_GETDETAIL|https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=bapi_projectdef_getdetail&adv=false&sortby=cm_rnd_rankvalue]
- to create the new project use BAPIs like [BAPI_PROJECTDEF_CREATE|https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=bapi_projectdef_create&adv=false&sortby=cm_rnd_rankvalue]
- [BAPI_PS_PRECOMMIT|https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=bapi_ps_precommit&adv=false&sortby=cm_rnd_rankvalue] and then BAPI_TRANSACTION_COMMIT or ROLLBACK to end.
Regards

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

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

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

Doc listing all OBIA RPD Projects and related Subject areas and Presentation tables.

Hi All,
Can anyone help with the Oracle document ID which gives the RPD Projects and related Subject areas only and Presentation tables.
I tried using the documentation utlity but it is unable to give me result according to the RPD Projects.
Thanks,
Dev

It is combination of different activities:
Product guide, check here cool-bi.com
RPD documentation based on prod guide.
There might be a project called Project and try to import rpd contents into another then generate rpd doc.
if helps mark

Transfer data from one database to another without identities but keep the relation b/w PK and Foreign key

Hi,
I need to transfer data from one database to another database (both are identical databases).
1. Not transferring identity columns (primary keys). the destination table might have the same key.
2. keep the PK's and FK's relation b/w parent and child table
3. I have 4 levels
Example: tableA (col1 int identity(1,1) , col2, col3)
tableB (col1 int identity(1,1) ,
col2 , col3) -- col2 has the foreign key relation with tableA.col1
tableC (col1 int identity(1,1) ,
col2, col3) -- col2 has the foreign key relation with tableB.col1
tableD (col1 int identity(1,1) , col2, col3) -- col2 has the foreign key relation with tableC.col1
please advise me.
Thanks in advance

Try the below:
/********************************SAMPLE TARGET***************************************************************/
Use MSDNSamples
create table TableA(LevelValueId int identity(1,1) primary key, name varchar(100))
Insert into TableA(name) Select 'R1'
Insert into TableA(name) Select 'R2'
create Table TableB(ChildId int identity(100,1),name varchar(100), LevelValueID int references TableA(LevelValueId))
Insert into TableB(name,LevelValueID) Select 'Childname1',1
/********************************SAMPLE TARGET***************************************************************/
/********************************SAMPLE SOURCE***************************************************************/
Use Sample
create table TableA(LevelValueId int identity(1,1) primary key, name varchar(100))
Insert into TableA(name) Select 'C1'
Insert into TableA(name) Select 'C2'
create Table TableB(ChildId int identity(100,1),name varchar(100), LevelValueID int references TableA(LevelValueId))
Insert into TableB(name,LevelValueID) Select 'Kidname1',1
/********************************SAMPLE SOURCE***************************************************************/
USe MSDNSamples
/********************************MIGRATION INTERMEDIATE TABLE***************************************************************/
--Migration table
Create table Mg_TableA(LevelValueId int, NewValueId int)
/********************************MIGRATION INTERMEDIATE TABLE***************************************************************/
/********************************ACTUAL MIGRATION FOR MASTER TABLE***************************************************************/
MERGE INTO TableA
USING sample.dbo.TableA AS tv
ON 1 = 0
WHEN NOT MATCHED THEN
INSERT(name) Values(tv.name)
Output tv.levelValueId ,inserted.LevelValueid INTO
Mg_TableA;
/********************************ACTUAL MIGRATION FOR MASTER TABLE***************************************************************/
/********************************ACTUAL MIGRATION FOR CHILD TABLE***************************************************************/
Insert into TableB (name,LevelValueID)
Select A.name,B.NewValueId From sample.dbo.TableB A
Inner join Mg_TableA B on A.LevelValueID = B.LevelValueId
/********************************ACTUAL MIGRATION FOR CHILD TABLE***************************************************************/
/********************************TEST THE VALUES***************************************************************/
Select * From TableA
Select * From Mg_TableA
Select * From TableB
/********************************TEST THE VALUES***************************************************************/
Drop table TableB,Tablea,Mg_TableA
Use Sample
Drop Table TableB,Tablea

Best Practice - Outer Join between Fact and Dim table

Hi Gurus,
Need some advice on the below scenario
I have an OOTB subject area and we have around 50-60 reports based on it. The related subject area Fact and Dim1 table are having inner join.
Now I have a scenario for one report where outer join has to be implemented between Fact and Dim1. Here I am against changing the OOTB subject area join as the outer join will impact the performance of other 50-60 reports.
Can anyone provide any inputs on what is the best way to handle this scenario?
Thanks

Ok. I tried this:
Driving table : Fact, Left outer join -- didnt work.
Driving table: Dimension D left outer join -- didnt work either
In either the case, I see physical query as D left outer Join on Fact F. and omitting the rows.
And then I tried this -
Driving table: Fact, RIght outer join.
Now, this is giving me error:
Sybase][ODBC Driver]Internal Error. [nQSError: 16001] ODBC error state: 00000 code: 30128 message: [Sybase][ODBC Driver]Data overflow. Increase specified column size or buffer size. [nQSError: 16011] ODBC error occurred while executing SQLExtendedFetch to retrieve the results of a SQL statement. (HY000)
I checked all columns, everything matched with database table type and size.
I am pulling Fact.account number, Dimension.account name, Fact.Measures. I am seeing this error each time I pull Fact.Account number.

Foreign keys in SCD2 dimensions and fact tables in data warehouse

Hello.
I have datawarehouse in snowflake schema. All dimensions are SCD2, the columns are like that:
ID (PK) SID NAME ... START_DATE END_DATE IS_ACTUAL
1 1 XXX 01.01.2000 01.01.2002 0
2 1 YYX 02.01.2002 01.01.2004 1
3 2 SYX 02.01.2002 1
4 3 AYX 02.01.2002 01.01.2004 0
5 3 YYZ 02.01.2004 1
On this table there are relations from other dimension and fact table.
Need I create foreign keys for relation?
And if I do, on what columns? SID (serial ID) is not unique. If I create on ID, I have to get SID and actual row in any query.

>
I have datawarehouse in snowflake schema. All dimensions are SCD2, the columns are like that:
ID (PK) SID NAME ... START_DATE END_DATE IS_ACTUAL
1 1 XXX 01.01.2000 01.01.2002 0
2 1 YYX 02.01.2002 01.01.2004 1
3 2 SYX 02.01.2002 1
4 3 AYX 02.01.2002 01.01.2004 0
5 3 YYZ 02.01.2004 1
On this table there are relations from other dimension and fact table.
Need I create foreign keys for relation?
>
Are you still designing your system? Why did you choose NOT to use a Star schema? Star schema's are simpler and have some performance benefits over snowflakes. Although there may be some data redundancy that is usually not an issue for data warehouse systems since any DML is usually well-managed and normalization is often sacrificed for better performance.
Only YOU can determine what foreign keys you need. Generally you will create foreign keys between any child table and its parent table and those need to be created on a primary key or unique key value.
>
And if I do, on what columns? SID (serial ID) is not unique. If I create on ID, I have to get SID and actual row in any query.
>
I have no idea what that means. There isn't any way to tell from just the DDL for one dimension table that you provided.
It is not clear if you are saying that your fact table will have a direct relationship to the star-flake dimension tables or only link to them through the top-level dimensions.
Some types of snowflakes do nothing more than normalize a dimension table to eliminate redundancy. For those types the dimension table is, in a sense, a 'mini' fact table and the other normalized tables become its children. The fact table only has a relation to the main dimension table; any data needed from the dimensions 'child' tables is obtained by joining them to their 'parent'.
Other snowflake types have the main fact table having relations to one or more of the dimensions 'child' tables. That complicates the maintenance of the fact table since any change to the dimension 'child' table impacts the fact table also. It is not recommended to use that type of snowflake.
See the 'Snowflake Schemas' section of the Data Warehousing Guide
http://docs.oracle.com/cd/B28359_01/server.111/b28313/schemas.htm
>
Snowflake Schemas
The snowflake schema is a more complex data warehouse model than a star schema, and is a type of star schema. It is called a snowflake schema because the diagram of the schema resembles a snowflake.
Snowflake schemas normalize dimensions to eliminate redundancy. That is, the dimension data has been grouped into multiple tables instead of one large table. For example, a product dimension table in a star schema might be normalized into a products table, a product_category table, and a product_manufacturer table in a snowflake schema. While this saves space, it increases the number of dimension tables and requires more foreign key joins. The result is more complex queries and reduced query performance. Figure 19-3 presents a graphical representation of a snowflake schema.

Fact and Dimension tables

Hi all,
Please let me know the relation between the fact and dimension table(s).
regards
chandra kanth.

Hi Chandra, it would be useful if you read a little bit about BI before start working with a BI tool.
Anyway, I'll try to help you.
A dimension is a structure that will be join to the fact table to so that users can analyze data from different point of views and levels. The fact table will most probably (not always) have data at the lowest possible level. So, let's suppose you have SALES data for different cities in a country (USA). Your fact table will be:
CITY --- SalesValue
Miami --- 100
NYC --- 145
Los Angeles --- 135 (because Arnold is not managing the State very well ;-) )
You will then can have a Dimension table with the "Country" structure. This is, a table containing the different cities along with their states, counties, and finally the country. So your dimension table would look like:
NATION --- STATE --- COUNTY --- CITY
USA --- Florida --- Miami --- Miami
USA --- NY ---- NY --- NYC
USA --- Los Angeles --- LA --- Los Angeles
This dimension will allow you to aggregate the data at dffirent lavels. This is, the user will not only be able to see data at the lowest level, but also at the County, State and Country level.
You will join your fact table (field CITY) with your dimension table (field CITY). The tool will then help you with the aggregation of the values.
Ihope this helps.
J.-

RSNAST00 program and NAST table.

Can anybody tell what is the relation between
RSNAST00 program and
NAST Table ?
1). Actually, it seems RSNAST00 program first check the Object key entries in NAST table ...if it does not find the exact entry in NAST table, then RSNAST00 program creates one entry in NAST tables and generated spool...
Please validate me ...

Hi Sam,
The ABAP Program RSNAST00 is the standard ABAP, which is used to collect unprocessed NAST message and to execute the assigned action.
RSNAST00 can be executed as a collector batch run,that eventually looks for unprocessed IDocs. The usual way of doing that is to define a batch-run job with
transaction SM37. This job has to be set for periodic processing and start a program that triggers the IDoc re-sending.
Regards,
Chandra Sekhar

Relation Between BPEG & PRPS Table

Can anyone let me know the relation between BPEG Table & PRPS Table in Project System

Hi
kindly check the PRPS table and BPEG tables.
PRPS - WBS element master table
BPEG - Line Item Overall Values
link is PRPS-OBJNR = BPEG-OBJNR.
Thanks
Sunil

Excise invoice table and billing table relation???

Can anyone please tell me how excise invoise and billing table are related??

Hi
check these table VBRP and VBRK
you wil get idea.
if its useful reward points
thanks
senthil

Relation b/w PRPS and RPSCO tables

Similar Messages

Maybe you are looking for