I can create delta generation and i can see data in BO,but I want to know, If I want to create delta generation ,I must have timestamp or date field in my table or result of program?

If table doesn't have any date field ,how to do? I must add date field to table?

Hi Experts,

We have a requirement where we should authorized to pull only few company codes from SAP ECC extractors, namely all FI extractors.

Since its very sensitive data, our client is not agreeing for info package selections, they want a solution where BW system cannot see/pull the data for restricted company codes.

Is there any solution ?

TKIA

Anil

Hi Experts,

I have loaded the data to PSA successful, but when i am trying to load data to DSO it is giving me below error. Kindly help me to rectify below issue.

Regards,

Penchalaiah N

End Routine Vs Field Routine on Target DSO Key fields

Applies To:                 SAP BW 7.X transformations. For more information, visit the EDW homepage.

Summary:                   This document describes to reader whether to choose End routine or Field routine for DSO key fields.

Author:                       Kuldeep Jain

Company:                   Altimetrik

Created on:                19 September 2015

Author Bio:

Kuldeep Jain is BW certified and HANA certified Consultant. He got rich experience on various BW Implementation, support and upgrade projects in both SAP BW 3.5 and SAP BI 7.X.

Details:                        When it comes to write routine just before storing data to Target, we are having two options End Routine or Field Routine. Both routines are having its own advantages but what to chose for DSO Key fields Part.

Scenario:                     Let assume we are loading data from source DS/DSO to target DSO. One of Key field (Service material) is coming from different lookup table.

1. Sales order and Service Material No. is key field of target DSO.
2. For dashed transformation rule, we need to decide whether to write end routine or field routine.

Example data for Source table

Example data for Lookup Table

Target table (Should be)

Case 1: Lookup through End routine

When we write lookup code in End routine target DSO data will store data like below table:

Target table data (when using End routine lookup)

Reason for one row:               When data moves from SOURCE_PACKAGE to RESULT_PACKAGE internal table, data will get aggregate based on Target aggregation behaviour and key fields.

Before execution of end routine RESULT_PACKAGE data will be as follows:

Service material no. is blank. So three rows get aggregate and only last row (per DSO property) remain in RESULT_PACKAGE internal table.

After execution of end routine RESULT_PACKAGE data will be as follows:

This value will go to target and store.

Case 2: Lookup through field routine

When we write lookup code in field routine target DSO will store data like below table:

Target table data (when using field routine lookup)

Field routine will get execute for every records. It will execute before data moves to RESULT_PACKAGE so RESULT_PACKAGE will be having sales order along with service material no.

Conclusion: When it require to have routine for key fields. It is better to write in field routine. For performance perspective, we can push select statement to start routine and keep necessary data to global internal table then we can refer this global internal table at field routine.

Hi everybody,

I am trying to update cube from the PSA via End Routine to be able to data in the following scenario:

Source (Plan-yearly)

Mat. No. Cal Year          Prod. Amt            Prod. Price

ABC         2013               1200 PCS             USD 120000

ABC         2014               1500 PCS             USD 150000

ABC         2015               1600 PCS             USD 160000

Target (Plan-daily)

Material Cal. Year  Cal. Month      Cal. Day      Production Amt       Production Price

ABC       2013        01.2013          01.01.2013      1200 PCS /365            USD 120000/365

ABC       2013        01.2013          02.01.2013      1200 PCS /365            USD 120000/365

.........................................................................................................................

.........................................................................................................................

ABC       2013        12.2013          31.12.2013      1200 PCS/365            USD 120000/365

ABC       2014        01.2014          01.01.2014       15000 PCS/365          USD 150000/365

ABC       2014        01.2014          02.01.2014       15000 PCS/365          USD 150000/365

.........................................................................................................................

.........................................................................................................................

ABC       2014        12.2014          31.12.2014       15000 PCS/365          USD 150000/365

I am aiming to fill production amount and price data for each day of the year by dividing number of days in that particular year.

My first question is that if i need cal day and cal month in the source CSV document whichI donothave those time characteristics in the plan csv at  the moment.

another one is that the structure of the routine.

I need your input on that topic and thanks a lot

Regards.

Eddy

Hi Experts,

We have a Z query fro Creditors - Ageing W.R.T to invoice date.

Data flowin BW 3.5 is 0FI_AP_4 ---> 0FIAP_O03 - Z_AGEING REPORT.

Issue: end user is facing data mismatch with ECC.But till 2011 november figures were match correctly which is stated by end user .Please find attached design query in BW.

Regards

Taniya

We have a requirement to retrieve the Delivery level historical data stored in the Archiving session for the year 2008 from the source system to the BW system.I have found that the function module ARCHIVE_GET_TABLE can be used to retrieve the data from the archiving session.While i try to execute the function module,it is asking the input information as below.Kindly suggest me with your valuable input.

                 Archive_Handle =

                 Record Structure =

                 All records Of Object =

                 Automatic Conversion =

Customer wants to include the fields “E-Mail” and “Train station” from the Customer General Data from ECC and then update the information in the BW report.I have checked the standard data-source 0Customer_Attr ,here i have found the field Train Station ( BAHNS ) as the standard one present in the extract structure itself which fetches information from the table KNA1.And for the field E-Mail (SMTP_ADDR) ,it fetches information from the structure SZA1_D0100.Kindly suggest how to get the data from this structure for the field E-Mail.whether i have to go enhancing this standard data source for getting E-Mail information into BW.

Hi guyz,

I still didn't get the solution in my problem below..

RSA7 always ZERO even with new transactions

As an alternative, I'm planning to do a full load based on system date using the FM /POSDW/SEARCH_TLOG..I saw several documents but all of them are telling me to use the FM RSAX_BIW_GET_DATA_SIMPLE or RSAX_BIW_GET_DATA..

Some documents:

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/a0f46157-e1c4-2910-27aa-e3f4a9c8df33?overridelayout=t…

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/30f1a423-02ae-2e10-bd85-bde64e61fe7b?overridelayout=t…

Khoder Elzein's Blog: Create Generic Datasource using Function Module and Timestamps

I just want to ask if using the mentioned FM is the only way to do a generic extractor based on FM? I tried to use directly the FM /POSDW/SEARCH_TLOG and in the extract structure I used the ET_TRANSACTION in the EXPORT part of the FM..

But I got the error below:

I also tried to use the structure /POSDW/TRANSACTION_INT of the table above but also got this error:

I searched for some threads to solve the error above and got this..

Create Datasource with RSO2 & Function Module | SCN

But after copying the FM and creating my own table or structure to be included in the TABLES tab, I still encountered the same errors above..

Any idea how can I use the FM/POSDW/SEARCH_TLOG to create a GENERIC EXTRACTOR?

Thank you..

Loed

Hi everyone,

I am stuck on a problem for a while and can't find the solution to this in other posts. I have made a query which is working properly but I have to change one more thing in the output. Because of the size of the output, it is not really an option to adjust everything manually. In essence this is the problem:

In column A (Code), I see for every row a code (mostly unique codes, but sometimes they match with other rows). In column B (type), I see a certain letter. (For calculations in other columns, column A has to be sorted (A-Z).

The thing I would like to have now: If two codes are the same, and one of the Types is a "D", then all Types with this code should be a "D". So as example; In row 6 (with code 4444) the "E" should become a "D". Furthermore, in row 8, 9, 10, the "C" should both become a "D". For the two rows at the bottom, the Bs should not be changed.

I tried the following: If Previous([Code])=[Code] And Previous([Type])="D" Then "D" Else [Type]

However, there is apparently no Next function, so it only works for one direction. Furthermore, sometimes multiple rows have to be changed into a D (for example row 8, 9, 10).

I am looking for a way to do this. It does not really matter whether I have to adjust the formula for variable "Type" or to create a new variable. (Maybe important to mention, I have simplified the case in this post, the codes consist normally out of 10 random numbers which I don't know beforehand and do not have a relation to the Type). If I forgot any crucial information or if I was unclear, please let me know.

Thanks a lot in advance for your help!

Hi Expert,

i have the following error message when activating the data in DSO ( SAP BW on HANA )

Error during in-memory activation (see long text)

Message no. RSODSO_PROCESSING094

Diagnosis

SQL Code:129

SQL Text: transaction rolled back by an internal error: fail

Please, need your help.

Regards

Emile

a)  In sap bi 7.0 how to retrive deleted data back which was deletd wrongly.

Thanks & Regards,

Niiikitha

Hi,

After upgrade to BW 7.4 SP12, we are facing error while loading the data to SPO.

Runtime error: OBJECTS_OBJREF_NOT_ASSIGNED

Exception: CX_SY_REF_IS_INITIAL

ABAP program: CL_RSTRAN_TRFN================CP

We have similar issue while activating the transformation, "No transformation exists"

Can you please advise me if any possible solution.

Regards

Reddy

Hi Friends,

In our process chain we stuck up with some error could some one help me on this issue its very use full to me.

The create index step its showing the below error

No logs available for this index construction run.

In data target data was successfully loaded.

For your reference I have attached screen shots.

Regards,

Bhaskar.

Hello SAP BW Gurus!!

I have come across with several threads to understand the functionality of the Attribute only option of an info object

I understood the following thigs

1.  Take any info object and if you do not check the option as attribute only , this object can be added as an attribute to another char info object and

     by default the attribute is display attribute . If you wanted to make the attribute behavior as navigational attribute ( to use similarly char info object) you can change it to navigational attribute.

2. But if you have an info object , explicitly you checked that attribute only option , once you add this info object as an attribute to another info object it behaves just like display attribute . you cannot change it to display attribute . That means without having main char info object , you cannot use this info object in query(generally it is possible thru navigaional attributes)

IS my understanding is correct ???

And i have main doubt on the below statement

1. If you mark one info object as attribute only , you cannot use this info object in Info cube

2. But you can use this info object in DSO?

May i know the reason why it is given like that ? If you are able to include this object in DSO , why we will not be able to  include in infocube ?

Final doubt..

Once you mark an object is attribute only and this is being used in multiple places in bw (different info providers ) can we uncheck it and vice versa i.e

Initially object is not marked as attribute only , this object is being used in multiple data providers . can we change the object to attribute only?

Kindly clear the above questions

Thanks

Teja

There is an OFB solution how to model drill down using Analysis Items in WAD. What it takes is to pass selection from parent analysis item to child one. But this solution has two major problems:

• Bad Performance (since there is no parent Analysis Item initial selection, it takes long time to load detailed data of child analysis item);
• Not intuitive interface (since there is no parent Analysis Item initialial selection, it is not clear that parent analysis item should limit data of child one).

In my blog I will explain how to model drill down with initial selection to make analysis application both responsive and intuitve (some JavaScript knowledge will be required).

    Once my analysis application is refreshed it looks like this

This is what is required to make initial selection work:

• Initially hide child Analysis Item (in Web Template definition);
• Find first Product from parent Analysis Item (onload JavaScript);
• Select first row in parent Analysis Item (onload JavaScript);
• Limit child Analysis Item data to fist Product in parent Analysis Item and unhide child Analysis Item (onload JavaScript);
• Code call of all onload JavaScripts.

Lets see each step in details.

Initially hide child Analysis Item

Find first Product from parent Analysis Item

Add Data Provider Info Item for DP_1 (used by 1st Analysis Item)

Define JavaScript function to read first Product.

function Get_Product() {

var s;
var xml;
xml = document.getElementById('DATA_PROVIDER_INFO_ITEM_1').innerHTML;
xmlDoc=new ActiveXObject("Microsoft.XMLDOM");
xmlDoc.async=false;

xmlDoc.loadXML(xml);

var Product = xmlDoc.getElementsByTagName("AXIS")[0].getElementsByTagName("MEMBER")[0].getAttribute("text")

return Product;

}

Select first row in parent Analysis Item

Define JavaScript function to select first row in 1st Analysis Item

function Select_Row() {
var tableModel;
var element =  document.getElementById('ANALYSIS_ITEM_1_ia_pt_a');
  if (typeof(element) != 'undefined' && element != null)  {
// BW 7.3
  tableModel = ur_Table_create('ANALYSIS_ITEM_1_ia_pt_a'); 
  }
  else {
// BW 7.0
    tableModel = ur_Table_create('ANALYSIS_ITEM_1_interactive_pivot_a'); 
  }

var oRow = tableModel.rows[ 2 ];
sapbi_acUniGrid_selectRowCellsInternal( tableModel, oRow, true, null);

}

Limit child Analysis Item data to fist Product in parent Analysis Item and unhide child Analysis Item

Define JavaScript function that executes command sequence of two commands:

• SET_SELECTION_STATE_SIMPLE(limits data in child Analysis Item);
• SET_ITEM_PARAMETERS (unhides child Analysis Item).

function Filter_N_Unhide( Product ){

//Note: information can be extracted using the parameter 'currentState'

// and 'defaultCommandSequence'. In either case create your own object

// of type 'sapbi_CommandSequence' that will be sent to the server.

// To extract specific values of parameters refer to the following

// snippet:

//  var key = currentState.getParameter( PARAM_KEY ).getValue();

//  alert( "Selected key: " + key );

//

// ('PARAM_KEY' refers to any parameter's name)

//Create a new object of type sapbi_CommandSequence

var commandSequence = new sapbi_CommandSequence();

/*

  * Create a new object of type sapbi_Command with the command named "SET_SELECTION_STATE_SIMPLE"

    */

var commandSET_SELECTION_STATE_SIMPLE_1 = new sapbi_Command( "SET_SELECTION_STATE_SIMPLE" );

/* Create parameter TARGET_DATA_PROVIDER_REF_LIST */

var paramTARGET_DATA_PROVIDER_REF_LIST = new sapbi_Parameter( "TARGET_DATA_PROVIDER_REF_LIST", "" );

var paramListTARGET_DATA_PROVIDER_REF_LIST = new sapbi_ParameterList();

// Create parameter TARGET_DATA_PROVIDER_REF

var paramTARGET_DATA_PROVIDER_REF1 = new sapbi_Parameter( "TARGET_DATA_PROVIDER_REF", "DP_2" );

paramListTARGET_DATA_PROVIDER_REF_LIST.setParameter( paramTARGET_DATA_PROVIDER_REF1, 1 );

  // End parameter TARGET_DATA_PROVIDER_REF!

paramTARGET_DATA_PROVIDER_REF_LIST.setChildList( paramListTARGET_DATA_PROVIDER_REF_LIST );

commandSET_SELECTION_STATE_SIMPLE_1.addParameter( paramTARGET_DATA_PROVIDER_REF_LIST );

/* End parameter TARGET_DATA_PROVIDER_REF_LIST */

/* Create parameter RANGE_SELECTION_OPERATOR */

var paramRANGE_SELECTION_OPERATOR = new sapbi_Parameter( "RANGE_SELECTION_OPERATOR", "EQUAL_SELECTION" );

var paramListRANGE_SELECTION_OPERATOR = new sapbi_ParameterList();

// Create parameter EQUAL_SELECTION

var paramEQUAL_SELECTION = new sapbi_Parameter( "EQUAL_SELECTION", "MEMBER_NAME" );

var paramListEQUAL_SELECTION = new sapbi_ParameterList();

// Create parameter MEMBER_NAME

var paramMEMBER_NAME = new sapbi_Parameter( "MEMBER_NAME", Product );

paramListEQUAL_SELECTION.addParameter( paramMEMBER_NAME );

  // End parameter MEMBER_NAME!

paramEQUAL_SELECTION.setChildList( paramListEQUAL_SELECTION );

paramListRANGE_SELECTION_OPERATOR.addParameter( paramEQUAL_SELECTION );

  // End parameter EQUAL_SELECTION!

paramRANGE_SELECTION_OPERATOR.setChildList( paramListRANGE_SELECTION_OPERATOR );

commandSET_SELECTION_STATE_SIMPLE_1.addParameter( paramRANGE_SELECTION_OPERATOR );

/* End parameter RANGE_SELECTION_OPERATOR */

/* Create parameter CHARACTERISTIC */

var paramCHARACTERISTIC = new sapbi_Parameter( "CHARACTERISTIC", "D_NW_PRID" );

commandSET_SELECTION_STATE_SIMPLE_1.addParameter( paramCHARACTERISTIC );

/* End parameter CHARACTERISTIC */

// Add the command to the command sequence

commandSequence.addCommand( commandSET_SELECTION_STATE_SIMPLE_1 );

/*

  * End command commandSET_SELECTION_STATE_SIMPLE_1

    */

/*

  * Create a new object of type sapbi_Command with the command named "SET_ITEM_PARAMETERS"

    */

var commandSET_ITEM_PARAMETERS_2 = new sapbi_Command( "SET_ITEM_PARAMETERS" );

/* Create parameter ITEM_TYPE */

    var paramITEM_TYPE = new sapbi_Parameter( "ITEM_TYPE", "ANALYSIS_ITEM" );commandSET_ITEM_PARAMETERS_2.addParameter( paramITEM_TYPE );

    /* End parameter ITEM_TYPE  */

/* Create parameter INIT_PARAMETERS */

var paramINIT_PARAMETERS = new sapbi_Parameter( "INIT_PARAMETERS" );

    var paramListINIT_PARAMETERS = new sapbi_ParameterList();commandSET_ITEM_PARAMETERS_2.addParameter( paramINIT_PARAMETERS );

// Create parameter VISIBILITY

var paramVISIBILITY = new sapbi_Parameter( "VISIBILITY", "VISIBLE" );

paramListINIT_PARAMETERS.addParameter( paramVISIBILITY );

  // End parameter VISIBILITY!

paramINIT_PARAMETERS.setChildList( paramListINIT_PARAMETERS );

/* End parameter INIT_PARAMETERS  */

/* Create parameter TARGET_ITEM_REF */

var paramTARGET_ITEM_REF = new sapbi_Parameter( "TARGET_ITEM_REF", "ANALYSIS_ITEM_2" );

commandSET_ITEM_PARAMETERS_2.addParameter( paramTARGET_ITEM_REF );

/* End parameter TARGET_ITEM_REF */

// Add the command to the command sequence

commandSequence.addCommand( commandSET_ITEM_PARAMETERS_2 );

/*

  * End command commandSET_ITEM_PARAMETERS_2

    */

//Send the command sequence to the server

    return sapbi_page.sendCommand( commandSequence );

}

Code call of all onload JavaScripts

Define JavaScript function to call all above and attach it to BODY onload event

function initial_selection( )  {

Select_Row();
Filter_N_Unhide(Get_Product());

};

…

        </head>

        <body onload="initial_selection();" >

            <bi:QUERY_VIEW_DATA_PROVIDERname="DP_1" >

…

See attached EPM_DEMO Web Application templete for complete implementation details (rename to EPM_DEMO.bisp before upload to WAD)

Hello BW Gurus

I am Very much new to the Open Text VIM module . I am facing issues while creating an extractor for the data available from the Output of the Standard Tracnsaction Code in ECC side /OPT/VIM_ANALYTICS.

Do we have any standard extractors available for the /OPT/VIM* tables or we need to build a custom extractor ??

Looking forward for your response.

Regards,

Sriram S

Hi,

The project is for implementing Open Text Vendor Invoice Management to obtain reports in BW.

Since I am not able to find much details on this module from technical perspective, can someone please help me with related links/documents specifically from extraction point.

I have come across table /OPT/VIM_1HEAD and /OPT/VIM_1ITEM for Header and Line item data which contains the fields relevant for reporting. Are there any standard extractors available using these tables.

It will be highly appreciated if I can also get some Tcodes and functional process of VIM in ECC and how are the below tables populated in ECC.

• /OPT/VIM_1HEAD
• /OPT/VIM_1ITEM
• /OPT/VT_KPI_SRC
• /OPT/VT_KPI_SRCE

Looking forward for your help.

Regards,

Nikhil

Hi Guys,

Due to some error we had to clean entire data from Billing DSO (DS 2LIS_13_VDKON) and have to re-init and bring worth five years data only. There are only 1.18 million records. The did 'Early Delata Initiliazation' and ran a full repair IP after deleting and filling the setup tables.

Now, in PSA the request is still yellow but in DSO its green.

Why is this happening. How can I address this issue.

Any suggestions?

Regards

Prashant

Hi friends!

Somebody tell me how to works that datasources (0GLX_01 and GLX02), and what is the source?.

Thanks for your help.

Regards.