Logical Systems & SRM Customizing

Dear Experts,
I would like to guarantee BDLS won't be executed within our SRM Productive environment. Unfortunately, according to the functional team and because of customizing requirements, it appears logical systems cannot be generic enough to guarantee the process. For instance, the organizational structure refers to <SID>CLNT<MANDT> instead of alias like 'ECC'.
Any advice to ensure to the infrastructure team they will never run BDLS after transports?
Thanks and Regards,
Ludovic

Hi,
thanks for your prompt answer. Unfortunately, the issue is a bit more complex.
1) We have defined a backend RFC in SRM : <DEV>CLNT100
2) We have define a distribution model in BD64 referencing this RFC connection
3) We tried to define R3 and SRM as alias within the customizing : "master data/ALE Options/logical sytem", SMOEAC, etc... (refering <DEV>CLNT100)
4) We have changed the organizational structure PPOMA_BBP in order to reference R3
5) Under "Master Data>Determining financial system for product type", we have defined (source = R3 / target = SRM) and so on, and so on...
6) We have launched the replication and then tried to retrieve products categories from PPOMA_BBP
Unfortunately, there is no existing product type under logical system R3 but under <DEV>CLNT100 and the shopping cart doesn't work => missing logical system
However, when naming the logical system <DEV>CLNT100 (instead of R3), everything is working ...
Unfortunately, when we will transport additional customizing to another system, this customizing will refer <DEV>CLNT100 instead of <PRD>CLNT100.
On site, SRM experts use to launch BDLS after customizing transports in productive systems in order to modify the SID. We cannot afford to launch BDLS in a productive environment which will probably take several hours to run.
Thanks for your recommandations,
Sincerly,
Ludovic

Similar Messages

Logical systems assignment when SRM and ECC are on 2 different servers

Hi SRM guru's,
What is the standard practice for Logical system creation and assignment when ECC and SRM are on 2 different servers.
I could not able to find which i created a logical system in SRM server which i created in ECC
Same for the ECC also.
how do i assign logical system of SRM to ECC
vice versa.
your prompt response is appreciated.
Regards

Hi Sai,
Logical System Naming/Creation procedure is not dependent on the servers but it is just a logical representation of a system.
As you are trying to name logical systems for ECC & SRM, please follow the below procedure which is usually recommeded by SAP and followed.
Logical System : <SID>CLNT<Client Number>
For Example if you have a client 300 in system DE0 (also called SID), the logical system name will be DE0CLNT300. And it will be same for SRM system.
You can refer the below document which eplains the creation of logical system and RFC destinations etc
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
Note: Only while configuring the RFC Destination, the servers will play a crucial role.
Regards
Kathirvel

Logical System is not in Customizing

Hi all,
For a specific Supplier, the users below it cannot buy the itens. For example, once they choose the catalog, the item and then finish the purschase it comes up a pop up message "Logical System is not in Customizing. Inform System administrator". I already check every custo here but did not find yet a clue...
does anyone could possibly now what is going on?
Kind regards
Oliver F

Hi,
If possible , could you buy without catalogue just to eliminate a business case.
If for non catalogue purchase , the error still occurs thne you probably have a customizing error.
If it works, then we have to focus on the catalog flow side.
Kind regards,
Yann

Logical system name in SRM system

We are into SRM version 5.(SRM server 5.5) with the backend system as SAP ECC 6.0 .
The logical system is defined as '0000000050' for backend SAP system . All the systems like CRM and BW uses this as the logical system name for backend system . Recently SRM is implemented in our organization and we have no other choice and have to use the logical system name as '0000000050'
When product categories are assigned in the org attributes , the system stores the back end system as 50 and this is the issue. SAP support mentions that this is issue with logical system naming convention and that need to be fixed . But they fail to understand that the same name works fine in all other systems and also in SRM system except product categories .
Is there any OSS note for this fix. I would like to hear your experiences in this scenario.
Thanks
Mani

Hi Mani,
Logical System names are system specific, hence you have a different name in SRM system which will represent your backend system and this is not at all an issue. As suggested by SAP; '0000000050' is not the best name as per best practices.
You should have a name which should be of the pattern: <SID>CLNT<Client Number>.
Now here is the solution/work around. But be very careful and try this in sandbox system before being carried out in Dev/QA/PRD systems. Please make sure no other users are performing any activity while these tasks are being carried out.
In addition, please read through the ["Set up and system copy of SRM server 5.5";|https://websmp204.sap-ag.de/~sapidb/011000358700000310782007E/SRM50_SetupTranspCopy.pdf] guide before you carry out this activity:
The below activities are to be carried out only in SRM system
I assume SRM & Backend are separate instances
1. Create a new logical system name for the backend system in SRM system as per the standard suggested above.
2. Then use the transaction BDLS, to convert the old logical system name to new logical system name in all the tables.
3. Now, the step 2 ensure the logical system name is converted appropriately in all tables except SRM Org Structure related table.
4. Use the report RHOMATTRIBUTES_REPLACE, for replacing all the old logical system value with new logical system value. Please note while providing the inputs in the screen, there will be a Checkbox field called "Sub-String", you must check this one for all attributes you enter in the report. Then when you execute the report, a list will be display, here you have to select all the rows and click the first button on the toolbar. Only then the attributes will be updated.
Please let me know, if further inputs are required.
Regards, Kathirvel

Generate WP_PLUXX to a logical system(LS) instead of store customer(KU)

Hi Guys,
Is is possible to generate an WP_PLUXX idoc to a partner profile of logical system without having store created as a partner profile?
We have a situation wherein the messages(new articles, price changes etc) belonging to different stores (from SAP) are received in a central hub and then transmitted to the individual stores from the central hub.
Regards,
Selvakumar

Hi Venu, Thanks for your reply but still the problem exists.
1) Are you saying that the partner profile of type KU is to be created for Reference store(R110) that is assigned in the client level configuration "Logistics General - Basic data retail - General control, retail master data"?
I tried with this option, but it is still not recognizing the partner profile of ref store (R110) as it used to recognize the individual store as partner profile. So as a result I getting the error as "29 - Error in ALE service" with message as "Entry in outbound table not found".
I did couple of analysis in the programs associated with WPMA and WPMU and understood that the system picks up the customer number from the T001W table and it is looking for existence of partner profile for the same customer number in EDP13 table (which is not in our case). Can someone correct me if I'm wrong.
Also is there any standard option to trigger the idocs WP_PLUXX or WBBDLDXX to a logical system partner type without having to create the individual partner profile for each stores?
Let me know if you need any further clarifications.
Regards,
Selvakumar
+91 96770 73827

Cannot change PO's in SRM due to system copy/ logical system error

Hi All-
We are running SRM extended classic scenario. We would like to change PO's that have been created in our production system, but copied to another environment. We are trying to change these PO's in the copied system but are getting error messages in the process purchase orders transaction in SRM, and are not allowed to change the PO's. The message reads "purchase order contains items with different logical systems". Our basis team changes the logical systems as part of our system copies. Has anyone experienced this? I this part of standard SAP functionality? Are their logical systems in any of the transactional data(PO) tables that we need to change?
Also, we are deleting the material group/product hierarchy in comm_hierarchy as part of our system copy tasks because the material groups each have a GUI ID that is system dependent. Could this have something to do with our issue? Any feedback is greatly appreciated.
Thanks.

Hey John,
Yes I'm still at CA. How are you?
I checked bbp_pd and the logical systems are changed correctly to the copied system, not set to production. Am I missing something here? Should they be set to production logical system names even though I am trying to change the PO in the copied system?
Thanks!

In CIF customer exit there is no information about the logical system

Dear All,
we have a SAP R3 system (ver 4.7) connected to 2 SAP APO systems.
we need to differentiate the UE code in R3 by APO TARGET SYSTEM.
In the CIF userexit used:
EXIT_SAPLCLOC_001
EXIT_SAPLCSRS_003
EXIT_SAPLPGS1_001
EXIT_SAPLCSTK_001
EXIT_SAPLMEAP_001
there is no information about the logical system (source, destination
etc.) The control parameters are not provided to the user exit.
I found a note 1060634 where the parameter have been added to
EXIT_SAPLCSLS_002 , but not to all other exits.... do you have any clue on how we can proceed?
Thank you !!
Best Regards , Barbara

Found the answer, to bad i cannot give points to myself :-P
In the ABAP i use the E_T_RANGE output structure.
That structure has several fields (sign, opt, low, high).
In my ABAP i stored the same value in the low and high field.
This should work fine for normal (flat) characteristic values.
However, because i use a hierachy i should enter the 0HIER_NODE value in the high field.
For details see: SAP NOTE: 912473
Regards

Logical system name to be updated while client copy--URGENT HELP REQUIRED

Hello All,
I have a query regarding the "Logical System name" updation during Client copy.
When we make a client copy(SRM Masters) for the Production system(SRM),the Old Logical system name for backend(which is attached to the SRM masters) gets copied to the new Client (Copy) which needs to be updated.
There is a std transaction BDLS through whcih w e can change the current Logical system name to a new one but this seems to work fine for System copy but not for Client copy.
So when i make a client copy of SRM masters for Production system,is there any other std way wherein i can change the "Logical system name " for the backend or do i have to write a CUSTOM program wherein entries for the Backend Logical system name in tables like CRMMLSGUID will be updated with the new Logical system name?
Any help on this is appreciated.
Thanks & Regards,
Disha.

Disha,
Yes, I did it twice and it worked fine.
The R/3 GUID is sent by the OLTP system (R/3) in R/3 message header.
SRM checks this GUID in CRMMLSGUID table.
If is not the same one, then replication process fails.
The only solution I found was to delete this entry. It is automatically recreated with the new GUID with the next replication, with FM CRMT_OLTP_LOGSYS1, called in BAPI_CRM_SAVE.
Look at OSS note 588701 & 765018 for deletion of CRMMLSGUID.
The issue is exactly ours: around system/client copy.
In an CRM environment, this is more critical, because we make a huge use of the middleware. But in our case, and especially after system/client copies, we can go, even if SAP does not guaranty anything, because we don't care about "old" replicated data (I don't care about old BDOCs, that should even be deleted after processing).
We have to take some risks sometimes...
Rgds
Christophe

It is possible to transpor the logical system definition and the RFC

Hello,
To define the back-end logical system we need to link the RFC destination SM59. If it is not possible to TRANSPORT the RFC destination from the development system to the quality one, I need to create the quality back-end logical system without transport.
In SRM there is a lot customizing in which we need to assing the back-end logical system. If I can not transport the back-end logical system definition from development to quality I must "re-create" a lot of customizing ditectly in quality (and later in production!)
This is the normal way to work in SRM? Do I have to create the RFC destination, the back-end logical system, etc. in each eviroment (development / quality / training / acceptance / production) or there is a way to transport this?
Cheers,
Marta

Hi Marta,
transporting in SRM is different from the other SAP areas. There are several
objects, which are normally customizing, but in SRM not part of the transportable
objects. You have to do quite a lot of settings manually in QA as well in PROD.
Start the discussion early to get the needed authorizations for doing the settings.
The following doc gives an overview and explains:
https://websmp201.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=011000358700000310782007E
Cheers,
Claudia

Create logical system

Hello everibody
I am starting the configurations of the SRM 5.0 I have a doubt, In the customizing create logical system in SRM I must to create only a SRM logical system or I need to add the logical system of my backend too?
Thanks
Nilson

Hi
<u>Here are further links to help you out.</u>
<b>http://help.sap.com/saphelp_srm50/helpdata/en/82/cf7b3c5dc1b160e10000000a114084/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/ed/f2044115fbee6fe10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/74/ec7b3c91c1eb1ee10000000a114084/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/94/70b64115f2e034e10000000a1550b0/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/bb/6c0e3b02616a42e10000000a11402f/frameset.htm</b>
Hope this will help.
Please reward incase it suits your requirement.
Regards
- Atul

An RFC destination could not be specified for the logical system

Hello Experts,
I am trying post goods receipt in EWM system in a simple inbound delivery process. It is not getting posted back in ECC. I have my RFC connection setup properly(I assume since I was able to transfer inbound delivery to EWM in first place).It seems some setting related to Outbound queue in EWM is missing.Can anyone tell me in detail what settings are required?Is it something to do with WE20 transaction?I am not sure what settings should be done there.The error log is as below-
An RFC destination could not be specified for the logical system
SB3CLNT011
Message No. B1550
Diagnosis
An RFC destination should be specified for the logical system SB3CLNT011.
This could not be done in this case. SB3CLNT011 is not your local logical system
and this system is not included in the relevant Customizing tables.
Procedure
Check:
RFC
destination
Port
definitions
oubound partner profile of
message type SYNCH for this logical system
Regards,
Khushboo

Hi Oritra and Suraj,
I have checked remote connection in SM59 for both the logical system.It works fine.I understand this is more of a technical issue,but I don't have A local basis team to help me so reaching out to experts here.Can you guide me what technical settings could be checked for EWM-->ECC connection?When I execute BD82 for SB3CLNT011 it shows me green status with message "No messages have been defined for the selection conditions in the model".
Although when I do this for EWM logical system SB3CLNT012 it shows me this with all green status-
System SB3CLNT011 as a partner type already exists
System SB3CLNT012 as a partner type already exists
Port A000000018 with RFC destination SB3CLNT011 already exists
Outbound parameters for message type SHP_IBDLV_CHANGE SHP_IBDLV_CHANGE01 already
Outbound parameters for message type SHP_IBDLV_SAVE_REPLICA SHP_IBDLV_SAVE_REPLI
Outbound parameters for message type SYNCH SYNCHRON already exist
Am I missing something in WE20?
Regards,
Khushboo

Logical System is not defined in table SMOF_ERPSH!

Hi,
When i am replicating a material group to SRM system, in SMQ2, the error message appears as 'Logical System is not defined in table SMOF_ERPSH!'.
can any one please let me know why this comes up, i have checked the SMOEAC settings, its fine and the logical system entries are already present in the tabe

Hi,
Can you verify all your settings as per note 720819?
Also under SMOEAC transaction, site attributes for your site type 'CRM' may not have any value. Please define attributes for your SRM RFC destination. Select the correct RFC destination, then click on button 'Get Values'.After doing this, table SMOF_ERPSH should be populated correctly.
Regards,
Nikhil

Accessing XI logical system in message mapping

Hi All,
How can I retrieve the current PI logical system name in my mapping. I need to map it as part of the payload.
Is there a java api that I can use?
Thanks,
Harsh

Hi
Glad to know that it helped you..
we used this in one of our scenarios earlier.. but I dont know if there is any good doc on this.
check if this helps
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/72e26432-0701-0010-19ba-abc05de7360b
Our scenario was something like this.
The customer had only Two systems (one Prod + other for dev/test/QA etc). since we cannot adjust mappings other than Dev, we used the above way & looked up values to generate the exact target location.
I shall update this link for better doc, if I find any. (also for client info)
- just try "SAPSYSTEM" if it works
Cheers
Regards
Vishnu

Logical system in CLEAN_REQREQ_UP and BBP_GET_STATUS

Hi experts,
Just a very simple question : do you confirm the logical system we have to put in CLEAN_REQREQ_UP and BBP_GET_STATUS variants are that of SRM?
Thanks in advance.

Hi,
CLEAN_REQREQ_UP:
It checks whether the backend documents (namely-PR/PO/RES) have been created in the backend systems. Deletes obsolete table entries in SRM as well as updates document numbers in the Shopping Cart. You can't process the SC in SRM until this update is complete.
BBP_GET_STATUS_2:
It ensures that the information on the back-end documents is up-to-date. Retrieves the updated information from the Back-end systems (for example PO number after it was converted from a PR)
since both the reports checks and picks up data from backend system, we need to specify RFC for backend systems only.
-rgds,
Ravi

An SLD system has not been assigned to logical system TEC101

Hello all
We are trying to send an message RFC or IDOC from our SRM (5.0) system to the XI (7.0). But we allways get the error
"An SLD system has not been assigned to logical system TEC101". In the SLD the system is visible, sldcheck works.
Does anyone know this problem and can give me a hint how to fix this problem?
Thanks a lot
Stefan

Hi Stefan,
Is there a technical & Business System for SRM5.0 in SLD? If entry exists then confirm if the logical system name mentioned in Business System is TEC101.
If entry does not exist in SLD for SRM, then in SRM run t-code
1) SLDAPICUST .. Enter relevant details
2) RZ70 : Give XI Server details , activate and then Execute.
Once you do that you can see entry for SRM in SLD.
After that try running the schenario again.
Regards,
Sumit

Logical Systems & SRM Customizing

Similar Messages

Maybe you are looking for