SEM BCS Transport Request

Dear Experts,
Kindly let me know, WHile configuring BCS , saving any Request
i) Whole configuration gets saved to the Transpoprt Request or It understand the discrimination between Data Model, Master Data Consolidation Fucntion etc ?
OR/And
ii) While creating Consolidation Task, Can required task be saved in Transport request and unwanted task can be ignored in the same request ?
Regards
Ritesh M

Hi Alvin,
Here is a link (and more detailed info is in the link INSIDE this thread))):
http://scn.sap.com/thread/839812
Additionally:
look at te OSS Note #627924 - 'Restrictions with transport in BW-based SEM-BCS'
and also at 773178 - 'Overview of consulting notes in SEM-BCS'.

Similar Messages

BCS Release Request Short dump

Hello,
I'm trying to release my costumizing request, that contains the SEM-BCS configuration, although i'm getting a short-dump.
The description is as follows:
Short text
    Access via 'NULL' object reference not possible.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "CL_UG_MD_TR_METHOD_EXPORT=====CP" had to be
     terminated because it has
    come across a statement that unfortunately cannot be executed.
Error analysis
    You attempted to use a 'NULL' object reference (points to 'nothing')
    access a component (variable: " ").
    An object reference must point to an object (an instance of a class)
    before it can be used to access components.
    Either the reference was never set or it was set to 'NULL' using the
    CLEAR statement.
How to correct the error
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "OBJECTS_OBJREF_NOT_ASSIGNED" " "
    "CL_UG_MD_TR_METHOD_EXPORT=====CP" or "CL_UG_MD_TR_METHOD_EXPORT=====CM003"
    "UGMD_EXTRACT_SID_2"
Information on where terminated
    Termination occurred in the ABAP program "CL_UG_MD_TR_METHOD_EXPORT=====CP" -
     in "UGMD_EXTRACT_SID_2".
    The main program was "RDDM0001 ".
    In the source code you have the termination point in line 62
    of the (Include) program "CL_UG_MD_TR_METHOD_EXPORT=====CM003".
Source Code Extract
Line SourceCde
   32   FIELD-SYMBOLS <lt_table> TYPE INDEX TABLE.
   33   FIELD-SYMBOLS <ld_fsid> TYPE ug_sid.
   34   FIELD-SYMBOLS <ld_vsid> TYPE ug_sid.
   35 * FIELD-SYMBOLS <lt_target> TYPE ANY TABLE.
   36
   37   ASSIGN io_itab->rd_wa->* TO <ls_wa>.
   38   IF i_value_sid IS NOT INITIAL.
   39     ASSIGN COMPONENT i_value_sid
   40            OF STRUCTURE <ls_wa>
   41            TO <ld_vsid>.
   42     CHECK sy-subrc = 0.
   43   ELSE.
   44     CREATE DATA lr_sid.
   45     ASSIGN lr_sid->* TO <ld_vsid>.
   46     CLEAR <ld_vsid>.
   47   ENDIF.
   48
   49   IF NOT i_fieldname_sid IS INITIAL.                  "Start hah160603.1
   50     ASSIGN COMPONENT i_fieldname_sid
   51            OF STRUCTURE <ls_wa>
   52            TO <ld_fsid>.
   53     CHECK sy-subrc = 0.
   54   ELSE.
   55     CALL METHOD ugmd_get_fieldname_to_table
   56       EXPORTING
   57         i_tabname = i_datainfo-tabname
   58       IMPORTING
   59         e_fieldname = ld_fieldname.
   60     lo_fieldname = cl_ug_md_fieldname=>if_ug_md_fieldname~get_instance(
   61       ld_fieldname ).
   62 >>>>>     ld_fieldname_sid_fix = lo_fieldname->ds_data-sid.
   63     ASSIGN ld_fieldname_sid_fix TO <ld_fsid>.
   64   ENDIF.                                                "End hah160603.1
   65
Contents of system fields
Name     Val.
SY-SUBRC 0
SY-INDEX 1
SY-TABIX 0
SY-DBCNT 0
SY-FDPOS 0
SY-LSIND 1
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY TDR_FULL
SY-UCOMM REFR
SY-TITLE Transport organizer: ordens
SY-MSGTY I
SY-MSGID FINB_TR
SY-MSGNO 009
SY-MSGV1 &
SY-MSGV2 &
SY-MSGV3
SY-MSGV4
SY-MODNO 0
SY-DATUM 20080904
SY-UZEIT 200112
SY-XPROG SAPLSYST
SY-XFORM SYSTEM_HOOK_OPEN_DATASET
If someone have gone trough a similar experience, or have any tip of how to solve this issue, i'd apreciate a comment.
Will award points for valuable help.
Thank you

Hi Ricardo,
You tried to transport the BCS' configuration, right?
If in the request was the full set of settings from the start of the project, the it will definitely fail.
There are some restrictions in BCS transport. See, for example the OSS Note #627924 - 'Restrictions with transport in BW-based SEM-BCS'. It particularly says:
"For the initial system setup, and after substantial changes in the data model, you should transport the Customizing by means of manually created transport requests. We advise you not to use the automatic recording of all Customizing settings during the first implementation phase in the development system and not to use this request for the structure of the test and productive systems.
During the transport of a new consolidation area, the following settings should be transported in the following sequence:
1. Data basis
2. Consolidation area
3. Special versions
After the import of the data basis and the consolidation area, these settings should be checked in the target system. In particular, the RFC destination, the InfoCubes and ODS objects, as well as the InfoObjects. Note that RFC destinations, InfoCubes, ODS objects, virtual cubes and InfoObjects cannot be transported from the consolidation workbench with the transport functions. For instance, you have to transport and activate the InfoCubes and InfoObjects using the BW."
I usually transport the BCS setting in a little transport requests in this order:
- all BW objects and settings
- data basis (with source DB)
- cons area
- special versions
- versions
- master data
...etc.
Hope this helps.

Transport Request Ended with return code: === 12 ===

Hi
Good day to you.
We are able to move Transport Request from Development BW Client (with respect to an SEM-BCS Configuration) to Quality BW Client smoothly.
But when we move the same TR to Production client, we are getting the following error message. I would be very grateful if somebody could throw light on why it is happening, what could be its implications and what to do to avoid the same
Execution of programs after import (XPRA)
Transport request   : DBWK901288
System              : PBW
tp path             : tp
Version and release: 340.16.37 640
Post-import methods for change/transport request: DBWK901288
     on the application server: sapbwpd
Post-import method FINB_TR_AFTER_IMP_METHOD started for UCREPGROUP T, date and time: 20081029144344
Post-processing taking place in client 300
Import carried out using RFC destination PBWCLNT300
Communication error: Destination PBWCLNT300 -> long text
Errors occurred during post-handling FINB_TR_AFTER_IMP_METHOD for UCREPGROUP T
FINB_TR_AFTER_IMP_METHOD belongs to package FINB_TRANSPORT_TOOL
The errors affect the following components:
     FIN-FB (Financials Basis)
Post-import method FINB_TR_AFTER_IMP_METHOD completed for UCREPGROUP T, date and time: 20081029144351
Post-import methods of change/transport request DBWK901288 completed
       Start of subsequent processing ... 20081029144344
       End of subsequent processing... 20081029144351
Execute reports for change/transport request: DBWK901288
     on the application server: sapbwpd
There are no reports to execute
Execution of programs after import (XPRA)
End date and time : 20081029144351
Ended with return code: ===> 12 <===
Regards
Siddique

Hi Siddique,
Looks like your RFC destination is wrong. The proper syntax is FINBTR@<system>CLNT <client>.
See also the note 644610.

Bcs transport

Hi,
I understand that transport process for SEM BCS is divided into 2 category which is BW request( workbench) and BCS request(customizing).
For total records infocube, document infocube, goodwill data infocube, equity data infocube, investment data infocube and all other generated infocube should we transport it manually through bw request(workbench) or it will be transported automatically when we transport data basis in bcs through bcs request(customizing)?
Need your advice.
Points will be awarded.
Regards,
Shahrul

Hi,
Thanks for the input.
Sekar,
You said you transport all those infoproviders first before transporting the bcs configuration.
Is this means that you transport all the virtual cubes also before transporting the bcs configuration?
Hi Eugene,
Referring to your previous posting :
"I usually transport the BCS setting in a little transport requests in this order:
    * all BW objects and settings
    * data basis (with source DB)
    * cons area
    * special versions
    * versions
    * master data"
for "all BW objects and settings" , is this include all the virtual cubes and generated objects?
Thanks a lot guys.. Appreciate your inputs.
Regards,
Shahrul

General Questions about SEM-BCS Data Transfer

Please help me guys ! I need a clearer picture as to how exactly the loading of data should be done to SAP SEM-Busines Consolidation
Q1) Can I specify the Basic Cubes in my Data Basis Streams that I use for FI & CO in BCS-Workbench ? Or do I need to switch these cubes to Transactional, so it can be used in SEM-BCS ?
Q2) or Do I have to export the data out of my FI & CO cubes in BW to a FLAT FILE, and then load the Flat File into custom Transactional Cubes ?
Q3) Usually, for SEM-BCS would there be any direct connection to SAP R/3 or it`s via BW ?
Please help me with these initial issues guys ! Very much appreciated!

Hi Eugene,
   Great man! You`re back!...Nice to hear from yourself
   Anyways, I still am struggling to understand the Intergration from SEM-BCS with BW and/or R/3. If you have any material that can help me understand the intergration would be helpful.
   So, I had a look into the SAP Note 689229
   It says, all changes of master data nad hierarchies have to be made via the application layer by means of application SEM-BCS :-
a) By Flexible Upload
b) Manually in Consolidation Workbench
c) In Subordinate systems from transports
Hence, am I correct to assume that the only 2 options are permitted: Option (a) Flat File (b) Manually define the master data in BCS-Workbench ?
    So, now assuming that I need to define Consolidation Items into SEM-BCS.
Because there's too many, I would go with option (b) Flat File.
So, I create a Flat File containing the Consolidation Items. Next, how do I get this loaded into BCS-Console ?
Do I have to create a Transactional Info Cube and then load this Consolidation Items Flat File into it? Then following from there, I specify this Transactional Info Cube in my Data Stream ? or
Is there a way, I can directly read the Flat File from SEM-BCS ?
I use the following Info Cubes as source to my Data Basis:-
                   <b>Data Target | Virtual InfoProvider</b>
TOTAL RECORDS =   0BCS_C50    |     0ECCS_C05
DOCUMENTS     =   0BCS_DS12   |     0BCS_VC12
   P/S: We don`t use the SAP R/3 ECCS Module
Message was edited by: John Mcluskey

Transport request -repair status

Hi All
I have transport request in repair status...yellow in colour
Why does this happen? ( reasons; Did I do anything wrong?)
How to make the transport into normal status?
Thanks in advance

Hi Venkata,
It is showing 'Repair' status, as you are trying to make modifications to
either 1) a standard object using Access Key or 2) a semi-standard object which will not ask for a Access Key.
In case 1 & 2, the object / application would be developed by SAP.
In the 2nd case, you can do the customizing change provided you are sure that the application is used only for 1 purpose.
If it is used across projects, then the changes you are making will be affecting other's outputs also.
In that case, what you can do is copy the standard / semi-standard application and make the changes in your new custom application.
In some cases you will have to make some customizing changes to direct the control to the custom application rather than standard application.
It is always recommended to avoid any repairs being transported.
While SAP applies any patches, your changes to the object might get overwritten.
Please let us know if it answers your query.
Thanks,
Nisha Vengal.

PPOME - taking away transport request

Hello,
I was hoping someone with PPOME / workflow knowledge could help me here... Currently, are company locks down the transaction code PPOME, meaning you have to submit a transport request any time making a change to the struture, when a user...
THe way we have it setup is we have an organization unit at the highest level, followed by a position, and then a user assigned to the position.
What we would like to do is anytime we want to change a user (add/remove from a position), we would like for it to NOT ask for a transport request, but anytime some tries to change a position or organization unit, it does...
I hear this may be possible... cna someone tell me how/if it is?

Hi,
I assume you can find a test environment where you can change table T77S0 Group TRSP Sem.abbr. CORR value to X that should stop transport request window popping up when saving data in PPOME.
Then to demonstrate how we can control PPOME access using authorisations I would create a test user (SU01) and test role (PFCG).
In PFCG assign tcodes PPOME, PPOSE and SU53 to the test role. Since you have tcode PPOSE assigned it will bring authorisation object PLOG with required display values (PLOG: 1000, 1001 | * | C, O, P, S, T, US | 01 | DISP, LISD | * ).
Then you need to change the maintenance PLOG value to limit access to create relationships between S and US and specifically relationships A008 and B008. Some background for PLOG object fields:
Infotype and object type concept in HR works like object model. Infotype 1000 holds the name of the object. There are numerous different object types but PPOME displays mainly Jobs (C), organisational units (O), positions (S), persons (P), tasks (T) and users (US).
Infotype 1001 hold the relationship information between objects. When you assign user to a position you actually create a relationship (intoype 1001) between objects S and US. Relationships have different codes to describe the relationsip. In infotype 1001 the code is a subtype of the relationship. You can see all available values per infotype from table T778U.
So our second PLOG object should have authorisation to create infotype 1001 for object type S with subtype A008 and since relationships need to be created both ways I also need authorisation to create infotype 1001 for object type US with subtype B008. (PLOG: 1001 | * | S, US | 01 | * | A008, B008). If you want to restrict more specifically who can create and delimit relationships you can use different function codes (INSE, CUTI etc).
Play around and eventually HR object type and infotype concept is very straight forward. It's so different to other modules of SAP that it may first look bit weird...
Cheers, s

Unable to capture the Data Source into a Transport Request

Hi All,
We have a product hierarchy and we are using the data source :4R_PRODH_D_LGEN_HIER for the hierarchy.
Now we need to transport this structure to the quality environment but we were not able to capture the datasource:4R_PRODH_D_LGEN_HIER into a transport request.
When ever we activate the data source:4R_PRODH_D_LGEN_HIER it is asking for the Package and the Transport Request Number.If we give these details and save it, data source is not getting captured in the request, only the "bject Directory Entry" is getting captured.
Can someone please guide me on how to capture the datasource under "Data Sources in BW" in a transport request.
Regards,
Sachin Dehey.

Hi Sachin,
Hierarachy datasource is not captured as Attributes and Text Datasource. So what ever you have done is correct.
What ever is captured in Object Directory Entry is correct. So go ahead with your transports, once transport is done check the Hierarchy Infopackage with Available OLTP hierarchies and load the data.
Most important thing first see that the all Master & Transactional Datasources are transported in R/3 Dev to QA to PRD
In BW, datasources are not transported, only their replica is transported.
Transportation of Datasource is done in R/3. Only their replica is transported in BW.
So wht ever you have done till now is correct. So go ahead.
While attaching Hierarchy Datasource it is captured only in "Object Directory Entry"
Regards,
Vishnu.

Error while assigning objects to Transport Request

Hi All,
while assigning a Transfromation to a Treq i am getting an error saying
Object '7KU37C7IG3T7AQ5NHSLEZVC91' (ROUT) of type 'Routine' is not available in version 'A'
Message no. RSO252
Diagnosis
You wanted to generate an object with the name '7KU37C7IG3T7AQ5NHSLEZVC91' (in transport request ROUT) of type 'Routine' (TLOGO). This is, however, not available in the BW Repository database. It does not exist in the requested version A. If the version is 'D' then it is possible that an error arose during the delivery or installation. If the version is 'A' then the Object was either not created or not activated.
System Response
The object was not taken into account in the next stage of processing.
Kindly advice how to rectify this error

Hi,
You see the which infoobejct contains that routine and first collect that infoobejct and transport it then transport Transfromation. I hope you are missing some Routines while collecting the Transformations into request.
See OSS Notes:
Note 613581 - Transfer structure does not exist in version 'D'
Note 508921 - P11:Content transfer:RSO 252 or RSO 296:InfoObject
Note 1157873 - BI7.0(SP18) Message RSO 252 using transport connection
Thanks
Reddy

Error while Transporting Request

Hi All,
we have ECC 6.0 on Unix environment.
we had copied a production client with group selection, as we wanted all the three system PRD,DEV,QLT in sync.
the export was succesfully done.i copied Cofiles & Datafiles which are generated in DEV & Quality server,then i add request no in transport queue. the time when i copied transport request was not releasing from development.we checked the destination it was full so we removed the old request. then req is releasing.
after that i deleted the Cofile & datafile from OS level of DEV & QLT & trying to delete the reques from request queue. it is deleted but when im refreshing the queue its coming back in the queue.
while transporting other request its giving me error.
please help out me.

Hi Aasmi Gawas,
Please could you post the error?
We don't have a crystal ball to see the errors in your system...
Best Regards,
Erick ILarraza

Error while importing a transport request

Hi,
I installed two SAP ECC6 EHP6 IDES sytems and created a transport route between them.
When I try to import a Transport request I get the following error:
HALT: inconsistent preview tables E071K_STR (size=344) and E071KS_PREVIEW (size=128)
Please help me find a solution to this problem.

Hello Occoro,
There are multiple steps you need to do, I am not sure if the following note is applicable to your version of SAP.
1730009 - Import queue does not work
Downloading R3trans and tp is similar to downloading kernel.
Download the versions relevant to your SAP Kernel 7.20, the latest patch should be available at http://service.sap.com/swdc
In the same area where you get SAP Kernels, you should be able to get files such as:
R3trans_xxx-xxxxxx.SAR
tp_xxx-xxxx.SAR
Download these files, uncar them to your kernel directory typically /sapmnt/<SID>/exe
Refer to the following note for more details:
19466 - Downloading SAP kernel patches
Good luck.
Regards,
Siddhesh

Error while releasing Transport request number

Hi Friends,
Whenever i release the Transport request from SE01 i am getting the following error. Please view the attached image . Could you please explain about that error ? and how can i prevent it in future ?

At starting it shows warning like " Your object contains error continue or cancel " but if i proceed with continue after completion of the releasing process it shows (0) successfully completed but not with an error message. As Krishna Chaitanya said i might have used any dependent object. by reading all of your answer i could understand that this is not sever problem. But i would like to understand this process very clearly . All i want to know is
how to release the request without any inconsistencies?
and which is the best way, ?
is there any requisition before i initiate releasing ?

Error while releasing transport request

Hi,
When i tried to release the transport request, it returning with code = 8 (error) so transport has not done. When I digged into the transport request, error message is
'unimplemented function REPC_OR_DELETE DOCUMENTATION'.
Thanks in advance.
Arvind...

Hi,
This is more related to the BASIS side,
still have found one solution in one of the thread. Still contact you BASIS administrator for it.
Solution.
Is the error pointing at TP or R3trans?
In this phase, we get error coz of r3trans.
Please try following the note 206168. which tells you to change the r3trans.
If you have changed the r3trans earlier, then try using the same r3trans as provided in the kernel CD.
Jayant Sahu

Unable to release Transport request in CHARM

Hi all,
After Setting up CHARM,created a Transport request,while releasing it thru CHARM gives error:"Release of system Q11 Could not be determined"
rgds,
rajesh
Message was edited by: rajesh
Rajesh M

Dear Rajesh,
1.Did you released the Task of the request in satellite system?
2.What error you get when you check inside the task list of that correction.
Please give inputs,which will help us in solving the issue faster.
Thanks and Regards,
Avinash.

Error while Releasing a transport request - DSO 0SD_O03: Active version

Hi all,
I am getting below error when I am trying to release a transport request.
Object ODSO 0SD_O03: Active version differs from modified version.
I activated DSO again,but I was not successful to correct the error.Please help me correcting this error.
Regards,
Bob

check
match and copy while installing the business content
Match (X) or Copy
If the SAP delivery version and the active version can be matched, a checkbox is displayed in this column.With the most important object types, the active version and the SAP delivery version can be matched.
When a match is performed, particular properties of the object are compared in the A version and the D version. First it has to be decided whether these properties can be matched automatically or whether this has to be done manually.
A match can be performed automatically for properties if you can be sure that the object is to be used in the same way as before it was transferred from Business Content.
When performing matches manually you have to decide whether the characteristics of a property from the active version are to be retained, or whether the characteristics are to be transferred from the delivery version.
The Match indicator is set as default in order to prevent the customer version being unintentionally overwritten. If the Content of the SAP delivery version is to be matched to the active version, you have to set the Installindicator separately.
The active version is overwritten with the delivery version if
 the match indicator is not set and
 the install indicator is set.
check following thread
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/102906a4-f13d-2e10-7199-ce316ff254b8?QuickLink=index&overridelayout=true
Thanks and regards
Kiran

SEM BCS Transport Request

Similar Messages

Maybe you are looking for