Transporting Problem in Sap Erec .

[Former Member]

Hello Experts,

I am having a general question .

Customising Settings got stored in Customising Request and Abap Devlopment , WDA, got stored in Workbench Request .

Now i have to move SAP E-REC DEV TO SAP E-REC QUALITY, well i have transported those request .

But there are lot of things which didn't moved to Quality . I am facing lot of troubles in QUALITY PORTAL as well .

For Ex :

1 . TREX CONFIGURATION , Search Engine Service Configuration .

2 . Changes done in Workflows, ex : tcode : HRASR_CHK_PROC_CUST , i changed those workflows and other settings in DEV , now i have to change that again in Quality .

3 . Switches in Table T77s0 , also not transported .

this is happening coz these things are not stored in any request .

These were the few  .

Now for Production, there will be no authorisation to manually change these things or do any configuration .

So, pls tell me the concept of this ? how it will be possible or i have to make manually configs for few things even at Prodction .

I am not able to view Recruiter Dashboard and MSS Requisition Monitor .

But i have crossed check their services are activated .

So, guys please Advise .

[Former Member · Accepted solution]

All except TREX configuration should be possible to transport as requests (workbench or customization). Basis can do the TREX configuration in the target system. If workflow task agent assignments are used, for example marking one or more tasks as General, those might have to be done in the target system also. You can transport changes in table T77S0 as well, use the menu entry Transport while in Change mode in transaction SM30. If the Switch Framework is used, relevant switches need to be activated in the target system as well. It sounds like not all changes were documented so you don't exactly know which changes to transport or adapt manually in the target system. You should go back to the persons involved in the implementation and make sure the entire implementation is documented so that you can have a succesfull go-live.

[Former Member · Accepted solution]

Hi Samuli .

Thanx for replying .

Yeah u r right, the problem is "DOCUMENTATION " .

That means that We have to do Trex Configuration At Production Server .

One more thing i need to know, please .

Do we have to need Different Trex Server for Devlopment, Quality and Production Or one Trex server is enough .

Actully basis told that we need different servers for efficient search .

But can't we have different RFC registered at single trex server like TREX_ED, TREX_EQ, TREX_EP .

Yeah , well its basis tension . But i am eager to know it, what should be best .

[Former Member · Accepted solution]

I agree with your basis. Having different RFC isn't the question, scalability and availability is. One more thing I forgot to mention are ICF services that you need to activate in the target system. There might be others, that is why having documentation is vital.

[Former Member · Accepted solution]

Yeah, you are right ICF services,even they are also not activated, i forgot to ask .

Well, thanx so much Samuli for your valuable inputs . Let me Discuss with Concerned people .

Thanx and Regards

Pankaj