Creation of new logical systems in IS Retail

Hi All,
"For every new store opened, create one Logical System"...i have come across this sentence in 1 of the documents which spaeks about creation of logical systems
So should i create one Logical System for every store and if i am sending Gift Vouchers to POS so should i create Logical systems for it
Regards

Hi,
Logical system is a System in which applications sharing a common data basis run. In SAP terms, a logical system is a client in a database. Messages are exchanged between logical systems.
Now the context you are talking about is not clear. Can you point out the specific information about the statement
"For every new store opened, create one Logical System"
It depesnds upon the background discription in that document.
Thanks
swarup

Similar Messages

Can we add new logical system in Entitlement tab in SAP Authentication.

Hi ,
We already Installed and configured sap integration kit and every thing works fine. My question is as of now we connected our sap BW Dev system to BOBJ but we would like to connect to BW Prod System to same BOBJ System. What are the steps we need to follow to do this.
Can we just add the new logical system in entitlement tab of sap authentication in BOBJ 3.1? and import the roles and login to BOBJ USING THE Newly added SYSTEM Credentials. Thanks in Advance.
Thanks,
SK.

Hi Ingo,
Thanks for the information.
Are there any specific steps you need to follow when you are adding one more system to sap authentication. can you please give the steps we need to follow to setup this in right way. Thanks in advance.
Is there any thing we need to configure on sap side other than sap logon ticket parametre. If you can please provide the steps it will be great. Thankyou very much In advance.
Thanks,
SK.
Edited by: Vallabhaneni SK on Jul 14, 2009 8:53 AM

New Logical System for every BPM in R3?

Do I need to set up a new Logical System in my R3 system for every BPM in XI that sends IDOC to it?
I need several BPM to split messages which I want to send to a R3 system. When I configure the scenario, the BMP is imported to the Configurator and the Adapter-Specific Identifiers need be added. A Logical System must be entered for the IDOC adapter. This Logcial System must be unique.
Is it possible to have several BPM without setting up a logical system in R3 for each of them?

Hi Elling,
You can overwrite the logical system name in the receiver agreement. If you select a different system (from the SLD) as Sender Service, the IDOC will be send using the logical system name of this sender service.
What we normally do is, set the sender service for a BPM to the original sender service.
Regards,
Christiaan Schaake

Trouble to add new logical system

Hi,
I'm having trouble with my script, as I'm getting this error msg:
S00348 Field V_TBDLS-LOGSYS(1) input value is longer than screen field
I tried removing the error-triggering value, but without it the eCATT won't add the new Logical System (BW in this case)
Please help.
Many thanks,
Siluris
Edited by: Siluris on Feb 16, 2012 1:49 PM

If you have recently updated any of the IM apps (windows live, yahoo messenger, gtalk) delete these and reboot your phone - there is an issue with the recent updates.

Runtime error (syntax error) when defining a new logical system

Hi!
I get a short dump when trying to define a logical system, the field clidep does is not defined in function module SCPR_BCSET_PROT_GET_TABKEYS:
CALL FUNCTION 'SCPR_HI_DB_SCPRACTR_READ'
 EXPORTING
 TABLENAME = wa_tabnames-low
 VIEWNAME = viewname
 CLIDEP = clidep
 IMPORTING
 ACTKEYS = actkeys
 EXCEPTIONS
 NO_DATA_FOUND = 1
 OTHERS = 2.
I have searched for notes, but I haven't fiund anything to correct the error. Does anyone one how to correct this?
- Mari Virik

Hi!
I get a short dump when trying to define a logical system, the field clidep does is not defined in function module SCPR_BCSET_PROT_GET_TABKEYS:
CALL FUNCTION 'SCPR_HI_DB_SCPRACTR_READ'
 EXPORTING
 TABLENAME = wa_tabnames-low
 VIEWNAME = viewname
 CLIDEP = clidep
 IMPORTING
 ACTKEYS = actkeys
 EXCEPTIONS
 NO_DATA_FOUND = 1
 OTHERS = 2.
I have searched for notes, but I haven't fiund anything to correct the error. Does anyone one how to correct this?
- Mari Virik

New outputs generated when changing logical system in output master record

Hi!
We are sending documents from ECC 5 to a legacy system via XI/PI. We are about to move from an old XI installation to a new PI installation. The output record used (for example in a billing document) is set up based on logical system. When moving from the old to the new platform, we need to change the output records from the old logical syste to the new logical system. However this leads to generation of new outputs in all billing docs when opened in change mode. This goes also for billing docs where we already generated outputs via lthe old logical system in the past. Is there any solution to prevent the automatic generation of outputs for documents where the condition type already was successfully processed (as it works when the logical system is not changed)?
Best regards
/Björn

Normally the same output is not supposed to be generated, unless 'Multiple issuing' checkbox is checked in the output type configuration.
Also you can probably add a requirement in the output determination procedure and check if output record already exists. Take a look at the standard 'Reprint' routine, kind of the opposite is needed in this case.

Logical System and Client copy

Hi Gurus ,
             I just now finished ECC 6.0 successfully , I want to take the client copy . But i hacve one doubt , In client creation one TAB logical system is there , Kindly advice me how to create Logical system and steps .
Regards
Selvan

Hi Manjula ,
              Below i mentioned the full detail about the error .
    RFC destination for client copy in systems with Financials Basis     (FINBASIS) component.
The system could not find any suitable RFC destination for processing     for client 000.     This note also appears if an RFC destination was found but this does not     work.     o   RFC destination: FINBTR@ID3CLNT000     o   Error text: Error during the retrieval of the logon data     Proceed as follows to eliminate this error:
1. Start the wizard to create a new RFC connection     or perform the following steps manually:     1. Create an RFC destination with the target ZK>source client of client         copy (in this case 000).
2. Check whether the RFC destination works in transaction SM59.         To avoid errors when assigning the password or the authorizations of         the RFC user, use the authorization test Test -> Authorization.
3. Enter the RFC destination:         -   Transaction: FINB_TR_DEST (Destinations for Transport Methods of             the Financials Basis)         -   Client: 000
4. Start the client copy again.
Kindly advice me
selvan

GRC 10.0 SP14 - Poblems when generating rules for logical systems

Hello Experts!
We recently updated a DEV system to SP14 and we're having issues regarding the rule set generation. I'd like to know if you have faced a similar problem after installing SP14. The details are described below:
Create a test function ZTEST_F1
The action PFCG is associated to a Physical System (Test Connector SP14) and to a Logical System (Sistema Logico Retail)
The logical system contains D05 among other connectors:
And it’s defined as a logical group:
The connector “test connector Sp14” points to the same system as D05.
Now I create another function, let’s say ZTEST_F2
Now let’s define a SoD Risk ZTSTSP14
Generate rules and after that we check GRACSYSRULE table for such risk and we get:
Let’s add more transactions:
Generate rules:
Now in the table we get:
The logical system has been added to the GRACSYSRULE table for the new combination and also the physical system TST_D05, but there's no combinations for the system D05 for example.
Now if we run SoD analysis:
We have four combinations for the physical system TST_D05 but only two for D05 that belongs to the logical system:
Do you have any clue? have you faced a similar problem?
Thanks in advance.
Cheers,
Diego.

Hello Collen!
First of all I want to thank you because after aplying the note the rules generated fine and now the Risk Analysis is OK for the example described above:
I've also tested with a huge number of risks and made a comparison between the results of the Physical conector and the Connector that belongs to a logical group and I got the same results as action level as well as Permission Level as expected.
Regarding the note itself, we usually check for notes and we have implemented many notes in advance related to rule generation issues.
The point is that, as my point of view is just not acceptable to get a new SP with this kind of issue. Rule generation is a core functionality and SAP must test such functionalities before releasing a SP and these checks cannot rely on the customer. For me, rule generation issues in GRC are just unnaceptable. I can accept issues with other modules or new functionalities, but with role generation they must guarantee that it works properly and perform the requiered tests before releasing an SP.
Well... bottom line the issue has been resolved and I really appreciate the help you provided!!!!
Many Thanks!!!
Diego.

Setup Logical System from blank

the default logical system of client 100 is blank
now we have to set a logical system for ALE and BW data transfer
but we found that some documents will not be transfer and some document cound not be found
eg: we cant found the FI documents from material document as MB53
debug the program we found that the programe check the logical system
is there any way to change the old documents logical system to new?
i found there is a sap note to describe how to change the logical system from a old value to new
but it not suit the situation of set new logical system from blank value.

HI ,
You need to create the logical system name and assign that to that client.
This can be done in Transaction :SALE.
Have a look at the t-code SALE and its options....
SALE->Basic settings->Logical system---- we have three options.
one is for creation ,assigning itto client ,other one is coversion.:Last one is only called BDLS .(little critical)
Thanks.

Logical Systems vs Cross Systems

Dear all,
I have two physical SAP ERP systems grouped under one logical system.
Now I want to connect to a third SAP ERP system in order to execute Cross System analysis between the systems under the logical system and the new third system.
I understand that I cannot do a Cross System RA on systems of the same logical system so that´s the reason why I need to set up the third system as a single new ERP system.
Anyhow the new ERP system should use the same rule set than the two systems of the logical system.
So I´d just like to set up the new system connector for the GRC 5.3 but I do not want to load the same rules again for the new ERP system, etc.
Is this possible? I tried to create a new logical system containing the new ERP system and regenerate the rules for the logical systems. But after that no simple RA is possible for the new ERP system.
Thanks for any advice and regards,
Markus Richter

Hello Markus,
Yes, you are right that you can not include the third system in the same logical group if you wish to use it for cross-system analysis. If you choose to have this as a stand alone system in RAR then first you will have to upload the rules for this stand alone system in RAR. The rules loaded for logical system will not work for this system as it is not part of the logical system group.
Regards, Varun

Creating logical systems in EP7

hello,
We have created a logical system that conects to a backend. All portal iviews point to this logical system.
We have to change the properties of the logical system but before do this step we need to proove that works correctly without changing the final users preview.
So we should create a new logical system and duplicate all iviews to point to this new logical system and to prove them.
But We prefer not to duplicate all portal content... Is other way to do this????
Thanks!
Marta.

HI ,
try these links.
https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=creatinglogicalsystemsinEP7+++&adv=true&sdn_author_name=&sortby=cm_rnd_rankvalue
http://help.sap.com/saphelp_bw21c/helpdata/en/cd/16b0cb100711d295750000e82de14a/content.htm
http://help.sap.com/saphelp_sm40/helpdata/en/a2/9b576a334144698f7938507b09b28c/content.htm
thanks
karthik

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

Logical System Conversion after system refresh failed

Hello,
Logical System Conversion after system refresh couldn't complete as the printer was locked. This job was run in the background. In SM37, the job log of RBDLSMAP shows as job finished, but it took only 40 seconds. Now I see that the logical system got changed(Converted) in the client settings scc4 but I know that this client being a production client and would run for couple of hours. Here is the job log information.
02/18/2009 16:09:33 Job started                                                                     00           516          S
02/18/2009 16:09:33 Step 001 started (program RBDLSMAP, variant &0000000000000, user ID ABCD)      00           550          S
02/18/2009 16:09:33 Output device PRN1 is locked in the SAP system                                  PO           349          I
02/18/2009 16:10:19 Job finished                                                                    00           517          S
When try to rerun bdls again, it shows that it is already available and it says "The new logical system name is already assigned to the current client".
Any suggestions on this?
Thanks,
Mahesh

Hi ,
Rerun the BDLS again as this took very little time.
When you try to run again it popsup message saying it already exists just delete that and again put the Logical system name and run it will run that time.
May be while scheduling the job you gave for spool I am not sure why is it looking for Printer which is locked.
Thanks.

Could not determine BW release of logical system 'BWPCLNT100

after a BI systemcopy (production to development) we get the following
error when we run load jobs of type "delta load". full loads work fine
"Could not determine BW release of logical system 'BWPCLNT100'"
even if i start the deltaload from the R/3 system with transaction RSA3
with update mode "C" i get the same error . when i use update mode "F"
it works fine , but that's not the thing we want.
BWPCLNT100 is the logical system of the productive system .
we have changed all the logical system setting to BWDCLNT100 using
transaction BDLS and we have also changed all entries in RSBASIDOC,
RSISOSMAP, RSOSFIELDMAP,.... .
we have done several systemcopies in the past , they all worked fine
and without this error. this is the first copy in BI 7.00 .
are there any loadmodules which have to be regenerated with the new logical system name?
thank you for your help and kind regards hannes toefferl

Hi,
As you said you are getting error after system copy when you are doing the delta load and full load is working fine for you.
This mainly happens due to init disturbance in the source system.
I would suggest you to delete the init and rerun the Init from BW once again.
This should solve your problem.
Thanks
Mayank

Logical system on QAS after remote client copy from PRD to QAS

I wander after remote client copy from PRD to QAS do I have to change Logical system on QAS. Do I have to run some postprocessing program?
Thank you in advance

Hi Branko,
After the system copy, go to transaction SALE -> Sending and receiving Systems -> Logical systems -> Define Logical System , click New Entries and create a new logical system for your QAS; then go to SALE -> Sending and receiving Systems -> Logical systems -> Assign Client to Logical System, click on the client, click change and assign the new Logical system.
Other activities, check Jobs, RFC's, etc...
Regards
Juan
Please reward with points if helpful

Creation of new logical systems in IS Retail

Similar Messages

Maybe you are looking for