Help !!! - Webservices not accessible in target systems after transport

Hi
We have a ECC 5.0 box ( WAS 640 ) and have created Webservice definitions and released it to SOAP runtime. We were able to make calls to the this Webservice from external SOAP clients and looks ok. We had this webservice definition ( and its associated objects like - virtual interface,server proxy implementation etc ) moved to our QA system. In the QA system - we had to release the WS for runtime using t.code WSCONFIG and the service shows up in SICF transaction under /default_host/sap/bc/srt/xip/sap/ as active . But we are unable to access the service in our QA system http://xxxxxx:8625/sap/bc/srt/xip/sap/SVCNAME?sap-client=080&wsdl=1.1 ?
We checked the icm monitor from SMICM and everything looks ok in QA and the very same as in development. Can anybody out there help me with this ? Any pointers/similar experiences /known problems with transport webservices- and how you resolved it would be extremely helpful and appreciated.
This is the first time we are trying out this mode and we are under time-pressure to get this working. Please help !!!

http://xxxxxx:8625/sap/bc/srt/xip/sap/SVCNAME?sap-client=080&wsdl=1.1 ?
ICF requires you to use Fully qualified domain name.
xxxx.domain.com:port
amy be this is an issue

Similar Messages

BADI not found in QA System after transporting from DEV system

Hi,
I had created a new implementation ZHR_IN_CALC_PTX_AMT to the BADI: HR_IN_CALC_PTX_AMT in the DEV system with Request ID. But when i had transported that request, i am not able to find that BADI implementation in SE18 and SE19 respectively in Quality system.
Please suggest me on this, as this is urgent.
Regards.
Ravi

Hi,
Can you pls repeat the BADI Definition name? I couldn't find HR_IN_CALC_PTX_AMT in SAP versions 4.7, 5.0 and 6.0. Which is the version you use for development?
Regards,
Renjith Michael.

Test System (BQ1) Objects showing up wrong Source System after Transport.

Hi Experts,
We are working on IS-U BI7.0 Project. We have finished with our Development and have transported the DataSources, Transformations and DTPs from Development (BD1) into Test (BQ1) Systems.
We have entered values in the Conversion of Logical Source Systems correctly.
When we select the DataSource and Click Object Directory Entry from the Extras Menu, we found that the Original Source System is defined as BQ1 instead of BD1 (Development System), which is where the Object is getting Transported from.
We have implemented an SAP Note:1008633 (Incorrect Source System after Transport (RSTRAN 514) but couldn't resolve the issue.
We basically want all the Objects in the BQ1 (Test System) showing the Original Source System as BD1 (Development System) but only the DataSources and it's connected Transformations and DTPs are originating from the BQ1 (Test) System itself (The Transformations when Transported from BD1 to BQ1 are Transported with a different Technical Name which is very strange).
Had anyone faced similar problem and if so, what was the effective solution implemented.
Any help in this regard is very much appreciated.
Thanks in Advance.
Best Regards,
Chandu.

It is resolved by our Basis.
Thanks,
Chandu

Solution Import Failure Message: Cannot add a Root Component 'GUID' of type 29 because it is not in the target system

Hi all,
Please refer to the error:
Root Components import: FAILURE
[2015-04-10 17:04:48.126] Process: w3wp |Organization:0937f109-45df-e411-80cf-0050560100db |Thread: 43 |Category: Exception |User: ac011cf7-ad36-405b-91cf-2155ca15efb1 |Level: Error |ReqId: d3924c06-ad4b-4d5e-a204-70f8170016e1 | CrmException..ctor
ilOffset = 0x30
at CrmException..ctor(String formattedErrorMessage, Int32 errorCode, Object[] arguments) ilOffset = 0x30
at ImportRootComponentsHandler.GetSolutionRootsCollection(Boolean throwIfMissing, Boolean skipRibbonCustomization) ilOffset = 0x209
at ImportRootComponentsHandler.ImportItem() ilOffset = 0x8
at ImportHandler.Import() ilOffset = 0x43
at RootImportHandler.ImportAndUpdateProgress(ImportHandler ih) ilOffset = 0x7
at RootImportHandler.HandleNonMetadataHandlers(String[] ImportEntities, ImportHandler& ihForCurrentPath) ilOffset = 0x33
at RootImportHandler.RunImport(String[] ImportEntities) ilOffset = 0x1D8
at ImportXml.RunImport(String[] ImportEntities) ilOffset = 0xE
at ImportXml.RunImport() ilOffset = 0x5BF
at ImportXmlService.ImportSolutionSkipCapable(Boolean overwriteUnmanagedCustomizations, Boolean publishWorkflows, Byte[] customizationFile, Guid importJobId, Boolean convertToManaged, Boolean skipProductUpdateDependencies,
ExecutionContext context) ilOffset = 0x46
at RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) ilOffset = 0xFFFFFFFF
at RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments) ilOffset = 0x25
at RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) ilOffset = 0xCF
at LogicalMethodInfo.Invoke(Object target, Object[] values) ilOffset = 0x4F
at InternalOperationPlugin.Execute(IServiceProvider serviceProvider) ilOffset = 0x57
at V5PluginProxyStep.ExecuteInternal(PipelineExecutionContext context) ilOffset = 0x200
at VersionedPluginProxyStepBase.Execute(PipelineExecutionContext context) ilOffset = 0x65
at Pipeline.Execute(PipelineExecutionContext context) ilOffset = 0x65
at MessageProcessor.Execute(PipelineExecutionContext context) ilOffset = 0x1C5
at InternalMessageDispatcher.Execute(PipelineExecutionContext context) ilOffset = 0xE4
at ExternalMessageDispatcher.ExecuteInternal(IInProcessOrganizationServiceFactory serviceFactory, IPlatformMessageDispatcherFactory dispatcherFactory, String messageName, String requestName, Int32 primaryObjectTypeCode,
Int32 secondaryObjectTypeCode, ParameterCollection fields, CorrelationToken correlationToken, CallerOriginToken originToken, UserAuth userAuth, Guid callerId, Guid transactionContextId, Int32 invocationSource, Nullable`1 requestId, Version endpointVersion)
ilOffset = 0x16E
at OrganizationSdkServiceInternal.ExecuteRequest(OrganizationRequest request, CorrelationToken correlationToken, CallerOriginToken callerOriginToken, WebServiceType serviceType, UserAuth userAuth, Guid targetUserId,
OrganizationContext context, Boolean returnResponse, Boolean checkAdminMode) ilOffset = 0x1F1
at OrganizationSdkServiceInternal.ExecuteRequest(OrganizationRequest request, CorrelationToken correlationToken, CallerOriginToken callerOriginToken, WebServiceType serviceType, Boolean checkAdminMode) ilOffset
= 0x2D
at OrganizationSdkServiceInternal.Execute(OrganizationRequest request, CorrelationToken correlationToken, CallerOriginToken callerOriginToken, WebServiceType serviceType, Boolean checkAdminMode) ilOffset = 0x26
at InprocessServiceProxy.ExecuteCore(OrganizationRequest request) ilOffset = 0x34
at PlatformCommand.XrmExecuteInternal() ilOffset = 0xF6
at ImportSolutionCommand.Execute() ilOffset = 0x20
at DataSource.ImportSolution(Byte[] customizationFile, Boolean overwriteUnmanagedCustomizations, Boolean publishWorkflows, Guid importJobId, Boolean convertToManaged, Boolean skipProductUpdateDependencies, IOrganizationContext
context) ilOffset = 0x0
at SolutionImportProcessPage.ImportSolution() ilOffset = 0x123
at SolutionImportProcessPage.ProcessRequestData() ilOffset = 0x4A
at SolutionImportProcessPage.ProcessAction(String action) ilOffset = 0x92
at AppUIPage.OnPreRender(EventArgs e) ilOffset = 0xD
at Control.PreRenderRecursiveInternal() ilOffset = 0x54
at Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) ilOffset = 0x6D3
at Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) ilOffset = 0x3C
at Page.ProcessRequest() ilOffset = 0x14
at Page.ProcessRequest(HttpContext context) ilOffset = 0x33
at CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() ilOffset = 0x18D
at HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) ilOffset = 0x15
at ApplicationStepManager.ResumeSteps(Exception error) ilOffset = 0x10A
at HttpApplication.System.Web.IHttpAsyncHandler.BeginProcessRequest(HttpContext context, AsyncCallback cb, Object extraData) ilOffset = 0x5C
at HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) ilOffset = 0x16A
at ISAPIRuntime.ProcessRequest(IntPtr ecb, Int32 iWRType) ilOffset = 0x4B
>Crm Exception: Message: Cannot add a Root Component 0ffbcde4-61c1-4355-aa89-aa1d7b2b8792 of type 29 because it is not in the target system., ErrorCode: -2147188705
[2015-04-10 17:04:48.126] Process: w3wp |Organization:0937f109-45df-e411-80cf-0050560100db |Thread: 43 |Category: Platform.Sql |User: ac011cf7-ad36-405b-91cf-2155ca15efb1 |Level: Info |ReqId: d3924c06-ad4b-4d5e-a204-70f8170016e1 | BusinessProcessObject.ExecuteNonQuery
ilOffset = 0x28
I am getting this coming up in the error log when I attempt to import an unmanaged solution.
After searching on google Type 29 refers to a workflow.
I go into the source system and query the database by the GUID and discover that it is actually a Business Process Flow called 'Phone to Case Process'.
I do not have this process in my target system as I deleted it.
Looks like this is one of the out of the box ones. I don't think we we have changed this one much.
What does this mean and what should I be looking for??
Anyway how do I remove this offending process from the unmanaged solution xml file and attempt to re-import it?
It doesn't look like I can generate the solution again without the offending workflow/process..

I managed to resolve this issue after looking at this thread:
https://social.microsoft.com/Forums/en-US/fddff17f-1cca-4d33-a666-60c08ad76b0c/crm-2011-import-failure?forum=crmdevelopment
Just modify both solution and customizations xml by searching for the guid and removing the root component

CUA roles sometimes do not match the target system

Hi,
We are using CUA on Solution manager to assign roles to our different systems. Every now and then what is in CUA does not match the target System.
I know that you can look at the idocs using WE05 and see what the root cause was, fix it and then re-assign the role.
The problem is that when you assign the role using CUA, it doesn't warn you that the transmission failed on the target system.
We just went live last week, so I am added and removing roles from many different users using SU01 and SU10 and I do not think it is a valuable use of time to sift through the idoc logs every time I make a change. Especially, since most of the time it works.
Is there a better way to monitor the Idoc logs? Can you have it send a notification (email for example) when there is an error? Is there a better process then WE05?
Thank you in advance for the help!
Neil

Neil. It was a long time I played around with CUA. But I am remembering some transaction where you had the logs. Think it is SCUL.
I searched saphelp and got the following hits for you:
http://help.sap.com/saphelp_nw70/helpdata/EN/c1/db4063fd3111d5997a00508b6b8b11/frameset.htm
http://help.sap.com/saphelp_nw70/helpdata/EN/cc/50b43be7492354e10000000a114084/frameset.htm
Best of luck to you!
Regards Fredrik

Term of payment does not exist in target system

Hi Gurus,
Scenario: Classic, Self service procurment.
I made a shopping cart with my requirements.
PR and PO created in the backend system.
Posted the GR in SRM....and got the message of posted in the backend.
Posted the invoice in the SRM and message creation completed and found that it has not been posted in the backend (checked the PO history).
The message found in SRM SLG1...."Term of payment does not exist in target system" for that.
Checked the vendor conditions and found that terms of payment exist in the backend system for that vendor.
What could be the problem and how to resolve this issue?
Thanks in advance
SG
Message was edited by:
SRMGUY

Hi,
I am new to SRM.
We have created new payment term in ECC and replicated to SRM using BBP_UPLOAD_PAYMENT_TERMS. We are able to see in table BBP_PAYTERM and BBP_PAYMENT_TEXT.
But the non of the payment terms are reflecting into PO in SRM after this.
I am able to see the payment term in backend in BBP_PD. I am getting the below warning message when I click on Check Button.
'Term of payment does not exist in the target system'.
What could be the problem and how to resolve it?
Thanks in advance.
Best Regards,
Siddappa

** File to IDoc scenario - IDoc not created in target system

Hi friends,
We are doing File to IDoc scenario. We made required setting in both application as well as XI system. While test the scenario, the file is picked up and successfully processed in SXMB_MONI, but the inbound IDoc is not created in target system. What could be the problem?
We are using DEBMAS message type DEBMAS06 IDoc type. We checked the following.
1) SM59 - Connections are OK both application and XI system
2) IDX1 - In XI System, we have assigned SAP<R/3> port.
3) IDX2 - IDoc is imported.
4) In ID - Sender File - Business Service - Adapter-Specific Identifier - Logical System name is given.
5) In application system. - Partner Profile maintained correctly.
6) SM58 - There is no error.
So, what could be the reason ?
Kindly reply, friends,
Thanking you.
Kind Regards,
Jeg P.

Hi,
Check all the steps ..
File to IDOC
Do these configurations in R/3 and in XI...
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
Thanks,
Satya

Help is not working in Hyperion System 9 WebAnalysis

two months back we have installed Hyperion System 9.2.0.3 BI+ server and is working fine. however recently one user complained that WebAnalysis help is not working. we are getting "page cannot be displayed" when clicking on Help --> contents and index from WebAnalysis -- <a target=_blank class=ftalternatingbarlinklarge href="http://hostname:19000/WenAnalysis">http://hostname:19000/WenAnalysis</a> this is the direct link to the webanalysis help <a target=_blank class=ftalternatingbarlinklarge href="http://hostname:19000/workspace/docs/en/wa_user/frameset.htm?/workspace/docs/en/wa_user/launch.html">http://hostname:19000/workspac...n/wa_user/launch.html</a> Do you know how to fix this?

Hi Friends,
I am working on Sandbox Server, in that Help (F1) is not working. When i try to click F1 system is opening the popup and showing the following message-
The page cannot be displayed
Plz help
Regards
Goutham

IDOC status on 03 but not recieved on target system

Hi,
We are recieving inbound idoc from external system and processing Inbound IDOC on SAP system, after processing inbound idoc on SAP we are sending status outbound idoc to external system.
The above functionality was working fine before upgradation.
after upgradation we have recreated RFC (TCP/IP) connection, updated at port level and also configured the new SAP system details ( sid, Hostname, service programsname...) on external system correctly.
Now we are recieving inbound idoc from external system on upgraded system,after processing inbound idoc details on SAP system, generating outbound idoc from SAP and it reaching the outbound prot sucessfully on 03 status with green light.
But external system is not recieving the IDOC. How to find why idoc is not reaching external system even though it is sucessfully passed at outbound port level with green light status 03.
We have also checked the SM58 for TRFC entries but we didn't identified any entries on SM58. Please help us on this issue
Thanks,
Raju

Hi Raju,
As mentioned by The specified item was not found., the one common problem for the IDocs not being sent might be a missing COMMIT WORK. I.e. when using the standard SAP API's for sending outbound IDocs, SAP actually creates the IDoc and registers an update function for sending the IDoc out. So without the COMMIT WORK, the IDoc usually exists on the database (implicit or database commmits), is in status 03, but hasn't been sent out and cannot be found in the outbound RFC queue (because SAP never tried to send it).
If you're convinced that a COMMIT WORK is happening (and after trying to send the outbound IDoc) then I'd try the following: Replace the used RFC destination (or re-define it temporarily) with one that points to the same system from where you're sending. If you don't see the IDocs as inbound IDocs or in the outbound RFC queue, the sending never happens. (Ok, might be a moot point if you completely trust your external system, but usually it's good to even rule out the most unlikely causes - if it's simple.)
So if this didn't help, maybe you can provide some further insight into how you're creating/sending the outbound IDocs. This could help us in trying to get some answer, but for a starter the COMMIT WORK mentioned by The specified item was not found. is in my opinion the best candidate.
Cheers, harald
p.s.: Even if you're using ALE, I don't think it could be due to anything in your distribution model as mentioned by The specified item was not found.. If you wouldn't have setup the distribution model, the SAP API's should create a master IDoc in memory and then no communication IDocs (since there's no recipients or due to filtering) and thus there should be no outbound IDocs on the database.

JDBC-RFC no errors at XI BOX still records were not update at Target system

hi
am doing jdbc to rfc scenario
tested rfc at target R/3 and its working fine,but records were not being updated in jdbc-rfc scenario.
i can see the audit log as success but no record is inserted at the target system
think problem is at FM.
please look at my FM code.
FUNCTION zscp_fm_inb_task_act_eff_updat .
""Local Interface:
*" TABLES
*" IT_TASK_DATA STRUCTURE ZSCP_S_TASK_EFFORT
DATA : v_taskguid TYPE bapi_ts_guid-task_guid,
 is_task TYPE bapi_ts_task,
 is_task_upd TYPE bapi_ts_task_upd,
 is_return TYPE TABLE OF bapiret2 WITH HEADER LINE.
*DATA : BEGIN OF it_data OCCURS 0,
 project TYPE zspr_project_id,
 task_id TYPE cgpl_entity-external_id,
 act_work TYPE dpr_tv_act_work,
 guid TYPE dpr_task-guid,
 END OF it_data.
DATA : BEGIN OF it_task_eff OCCURS 0,
 project TYPE zspr_project_id,
 guid TYPE dpr_task-guid,
 act_work TYPE dpr_tv_act_work,
 END OF it_task_eff.
DATA : BEGIN OF it_report OCCURS 0,
 msgtype(1),
 project TYPE zspr_project_id,
 task_id(24),
 msg(250),
 END OF it_report.
DATA : l_taskguid TYPE dpr_task-guid.
DATA : v_begintmstamp(20) TYPE c,
 v_endtmstamp(20) TYPE c.
*ranges : r_taskguid for l_taskguid.
DATA : v_tabix TYPE sy-tabix.
DATA : it_dpr_task TYPE STANDARD TABLE OF dpr_task,
 wa_dpr_task TYPE dpr_task.
*data : l_taskguid type BAPI_TS_GUID-TASK_GUID.
DATA : flg_no_flg TYPE c.
DATA : l_task(24),
 flg_error TYPE c.
DATA : l_taskdetail TYPE bapi_ts_task_detail,
 l_retdetail TYPE STANDARD TABLE OF bapiret2 WITH HEADER LINE.
DATA : v_count TYPE i.
DATA curr_date TYPE sy-datum.
DATA curr_time TYPE sy-uzeit.
CONCATENATE sy-datum sy-uzeit INTO v_begintmstamp.
DELETE it_data WHERE act_work < 0.
DELETE it_task_data WHERE act_work_effort < 0.
IF it_task_data IS NOT INITIAL.
LOOP AT it_task_data.
 v_tabix = sy-tabix.
 CALL FUNCTION 'CONVERSION_EXIT_DPRCE_INPUT'
 EXPORTING
 input = it_task_data-task_id
 IMPORTING
 output = it_task_eff-guid.
 it_task_eff-guid = it_task_data-task_id.
 it_task_eff-project = it_task_data-project_id.
 it_task_eff-act_work = it_task_data-act_work_effort * 60 * 60.
 MODIFY it_data INDEX v_tabix.
 APPEND it_task_eff.
 CLEAR: it_task_eff, it_task_data.
ENDLOOP.
 LOOP AT it_task_data.
 it_task_data-act_work_effort = it_task_data-act_work_effort * 60 * 60.
 MODIFY it_task_data.
 CLEAR it_task_data.
 ENDLOOP.
 SELECT *
 FROM dpr_task
 INTO TABLE it_dpr_task
 FOR ALL ENTRIES IN it_task_data
 WHERE guid = it_task_data-guid.
*Begin Commented by Aparna/25/01/2007 so that all the tasks are updated irrespective the planned efforts are filled or not.
 and
 work_effort > 0.
*End
IF sy-subrc <> 0.
 MESSAGE e000 WITH 'No data selected to update'.
ENDIF.
 IF sy-subrc = 0.
 curr_date = sy-datum.
 curr_time = sy-uzeit.
 LOOP AT it_dpr_task INTO wa_dpr_task.
 CLEAR it_task_eff.
 READ TABLE it_task_data WITH KEY guid = wa_dpr_task-guid.
 IF sy-subrc = 0.
 wa_dpr_task-act_work_effort = it_task_data-act_work_effort.
 wa_dpr_task-act_work_unit = 'S'.
 wa_dpr_task-zzupdated_date = curr_date.
 wa_dpr_task-zzupdated_time = curr_time.
 CLEAR wa_dpr_task-flg_man_rem_work.
 MODIFY it_dpr_task FROM wa_dpr_task TRANSPORTING act_work_effort act_work_unit flg_man_rem_work zzupdated_date zzupdated_time.
 ENDIF.
 CLEAR wa_dpr_task.
 ENDLOOP.
 DESCRIBE TABLE it_dpr_task LINES v_count.
 ENDIF.
ENDIF.
IF it_dpr_task IS NOT INITIAL.
*{17Sep2007 Refresh all tasks before updating the efforts
 UPDATE dpr_task SET act_work_effort = 0
 WHERE version_number EQ space.
*}17Sep2007 Refresh all tasks before updating the efforts
 UPDATE dpr_task FROM TABLE it_dpr_task.
ENDIF.
ENDFUNCTION.

Not exactly an ABAPer but I dont see a commit work in the FM. Maybe this is an issue
Regards
Bhavesh

Target System in transport request is blank

Hi
I set the transport system in a scenario DEV, QAS and PRD.
When I create an order request, the field target system is blank.
Where should I set it for me automatically display the system QAS as a system target ?
Thanks,
Enrique

Hi,
just adding my solution for future references..
I had similar problem but when I checked our transport package it was showing wrong transport layer..
Make sure your present transport package transport layer attribute is correct or not by using se21 or se80.
we have entered correct transport layer under our package and all working fine.

Wrong conversion of source system after transport

Hello,
We ve got a a transport problem in our 3-3 Landscape. Connections for extraction are only between same systems ( f.e. dev to dev)
BI Dev BI Test BI Prod
R3 Dev R3 Test R3 Prod
The conversion of source systems is on the BI test:
BI Dev becomes BI Test
R3 Dev becomes R3 Test
The conversion of source systems is on the BI Prod:
BI Test becomes BI Prod
R3 Test becomes R3 Prod.
With this it tells me the after transport (BI Test to BI Prod) of objects with source system assignement that the R3 Dev System is not known.
The transport before from the BI Dev to BI Test worked well without any problems.
We`ve got the BI Test and the BI DEV on the same host.
Has anybody got an idea what is wrong?
Thank you folks.

It must be R3D (dev system)
Something like following should be maintained in production
R3DCLNT100 R3PCLNT100 [Assuming R3PCLNT100 is your production system]
Don't forget to assign points,
-jayant

Last changed date different between two systems after transport

Hi, first of all, I am not from basis background and just want to make sure whether is this something correct or not.
I found that the "Last changed date" and "username" are not same between the original system and the target system. Is this something configurable?
And the "username" field is totally empty. However, the program code's version is identical in both systems.

I think I misunderstood your question. You are referring to the system Transports not the connections between systems. If the Transports are not transferring all the contents, you really should talk to your basis folks and tell them which items are not being reproduced correctly.
Regards,
Mike

One SLD means rename of SAP system after transport?

On development got the situation of having naming conventions for SAP boxes like R3DCLNT100 within the configuration directory. Do I have to rename manually my systems after a transport to Q into R3QCLNT100?

Hi Yuki
Does it matter what transport system you are using? File transport system or the CMS?
Normally, you define a business system as transport target, which is different from the business system the transport target is being defined for.
If we have the requirement to have the following transport targets:
BS_MJD (Dev) -> BS_MJQ (Tst) -> BS_MJP (Prd)
we should always define a target for that system?
Best regards,
Marco

Web Interfaces can be displayed incorrectly in QA system after transported

Dears,
I transported Web Interfaces for BPS from D system to Q system. I activate the BSP application in transation SE80 and activate the service node in transaction SICF in Q system. However, the BSP can't be displayed correctly with NO_METADATA_AVAILABE error.Also, I test the HTTP service in Q system, it works well. The transport steps I followed:
1) change the package of BSP application (SE80 D system)
2) write transport entry to new request (SE80 D system)
3) switch the correspoding service node to new object directory entry (SICF D system)
4) transport the request to Q system
5) activate BSP application (SE80 Q system)
6) activate BSP service node (SICF Q system)
Am I missing configuring something? or completely wrong steps? Any suggestions are appreciated.
Best regards,
Gerald

I resolved it myself

Help !!! - Webservices not accessible in target systems after transport

Similar Messages

Maybe you are looking for