Run CLEAN_REQREQ_UP withou logical system

Dear Experts,
1) I created some POs from the SOCO.
2) I deleted the POs and the SC items didn't come back to the SOCO.
3) I run the CLEAN_REQREQ_UP report with a logical sysem and nothing happened.
4) I run the CLEAN_REQREQ_UP report without a logical sysem and the SC items came back to the SOCO.
Do you see some problem to run this report without a logical system?
We work with SRM 5 and extended classic scenario.
Best Regards,
Eyal Weinreb
HP

Hi Jay.
We have the same issue in this moment between our SRM 7.0 EHP 1 y the back-end system SAP ERP ECC 6.0.
Is the only solution running the report CLEAN_REQREQ_UP without "logical system" ?.
Regards,
Martín.

Similar Messages

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

Logical System is not appearing in Informer tab to check SOD's

Hi GRC Experts,
I have an issue with logical system to run risk analysis.
I created logical system by following the Config guide, added physical system and generated rules (RAR Configuration>>Logical Systems>>Generate Rule) for that logical system.
I haven't generated rules for the physical system (RAR Config>>Rule Upload>>Generate Rules) since I dont want more rules to be displayed in the reports.
However I do not see logical system as an option in Risk Analysis (informer Tab) and Config>>Schedule background job for BAtch Risk Analysis>> under system as well.
It would be great if any one advice me on this.
Regards,

Thanks Chinmaya,
Yes you are right, I confirmed with a friend (my ex-GRC colleague) of mine as well.
can't execute sod checks on a logical system - logical systems are only intended to eliminate the need to add the same rule set over and over for the same types of systems
Regards,
Ramesh K

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

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 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.

Can there be more than one port for the same logical system

Can we have more than one TRFC port for tranferring data from one logical system to another?
The requirement is to transfer same basic idoc type from one logical system to another through two different ports. Is it possible?
For eg. some specific data (country specific) for the same basic idoc type can be sent through a separate port and the other data through a different port inorder to distinguish between the two.

Hi Shital,
I don't think so. Because of that what i told you. There would be a dirty trick (back routing) to solve your issue. But its quite difficult and not standard. You create two http receiver services and two http sender services. You route your message depending on payload to the one or the other http receiver channel. The receiver is in both cases: THE XI! Now you have a second message, which you can route to IDoc adapter. But in this case you have different sender and in the receiver determination you can put the sender, so you will be able to use different communication channnels and so different ports / destinations.
Advantage: Your task would run, no performance problem (http: very good, asynchron)
Handicap: You see every message double in the monitoring, the scenario is not easy to understand and it is a big task 4 other people to change it.
Regards,
Udo

PLEASE HELP ME TO FIND THE SOLUTION REGARDING "LOGICAL SYSTEM CHANGED"

HAI EVERYBODY,
PLEASE HELP ME TO FIND THE SOLUTION REGARDING "LOGICAL SYSTEM CHANGED" during the material master replication by using middleware parameters.
step1 : i have taken SRM client 810 and named it as CHINNISRM
step2 : i have taken r3 client 810 and named it as CHINNIR3
step3: During material master replication i maintained tables like crmconsum,crmrfcpar,crmparoltp in r3 and smofparsfa in srm client and filtered the objects and loaded the objects through r3ac3,r3ac1,r3as.
step4 : And later i have checked in r3 queues to activate the objects,but i have seen a message like "LOGICAL SYSTEM CHANGED:SEE 588701".according to the oss instructions i have checked in CRMPRLS table in se16 in R3 .there i found out there is one logical client named with T90CLNT810.
oss :588701
Solution
There are different cases in which different forms of processing are
required or where several options exist:
- The logical system name of an R/3 Backend client was changed in
current operation. In this case, the data hangs in the outbound
queues of the R/3 Backend system as specified under point 1 of
the symptom. In this case, the logical system name must be
changed back to the original value. Then the outbound queues
can be reactivated. If no data was transferred to the EBP/CRM
server before the change, also a correctioin of the check table
is possible.
- The same logical system name was used again in a new client of
an R/3 Backend system that was linked to the EBP/CRM server. In
this case, the data is in the inbound queue of the EBP/CRM
server with the exception GUID_FOR_LOGSYS_CHANGED. In this
case, the queue entries which have status SYSFAIL must be rejected, however, not the entire queues. If the new client of the R/3 Backend system you have linked has exactly the same
data as the old client and if it is meant to replace the old
client (that is, this was deactivated), also a correction of
the check tables is possible. In this case, the inbound queues
can be reactivated after the correction.
oss:765018
1. If the situation in your system corresponds to the situation described
under "Reason and Prerequisites" and if symptom 1 occurs, you can
delete the table entry from table CRMPRLS table (there is just one
entry). Since there is no maintenance dialog for this table and you
cannot maintain it using transaction SE16, you must use a report to
delete it. This report is attached to this note as correction
instructions.
Create the report ZZ_DELETE_CRMPRLS in your system and copy the source
code from the correction instructions. You cannot implement this
source code using transaction SNOTE.
You can use the report in every plug-in or plug-in basis system, even
if it is not specified in the validity section.
After you have run the report, you can trigger existing queues again
in transaction SMQ1.
2. If the situation in your system corresponds to the situation described
under "Reason and prerequisite" and if symptom 2 occurs, you can
delete the entry from table CRMMLSGUID (there is just one entry).
Since there is no maintenance entry for this table and you cannot
maintain it using transaction SE16, you must use a report to delete
it. This report is attached to this note as correction instructions.
If they do not yet exist, add the following messages to message class SMOF in your logon language:
Message Message short text
303 User &1 is not allowed to change table &2.
304 User &1 IS not allowed to display table &2.
305 Logical system &1 was not found in table &2.
306 System error! The current client was not
found in table T000.
Create the report ZZ_DELETE_CRMMLSGUID in your system and copy the
source code from the correction instructions. You cannot implement
this source code using transaction SNOTE.
You can use the report for every release of the CRM system, even if it
is not specified in the validity section. The only exceptions are CRM
releases with Support Package versions that are too low such as CRM
Release 3.0 with Support Package 12.
After you have run the report, you can trigger existing queues again
in transaction SMQ1 of the R/3 back-end system or transaction SMQ2 of
the CRM system.
so what should i do to do the replication.please suggest me .untill and unless i solve my problem i cant move to the further activity.i hope you people can solve my problem.thanks in advance.
thanks and best regards,
n.chakradhar

Hi chakradhar,
Did you find a solution to your issue? We are facing a similar issue and looking to figure out how this can be resolved.
BR// 420

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

RPM_FIN02 - Receiver of IDoc is its own logical system

For one particular portfolio item, I run the RPM program RPM_FIN02.
This results in an IDoc creation.
Next, I checked the status of the IDoc (RPM > Base System Interfaces > SAP Financial and Controlling Integration > Data Distribution From SAP FI-CO to SAP xRPM > Check Inbound Processing).
This shows the status "29 - Receiver of IDoc is its own logical system".
As a result, the Internal Order costs (including the ones posted from cProjects) do not get pulled into RPM Financial Planning.
Please advise.
I do not have the technical understanding of this issue, and would therefore need a little more than the mere technical jargons and terms to be able to resolve this.
Thanks for understanding.

Hi,
Very briefly,
-Assuming your RPM system is independent of your ECC box. But RFC connected.
-RPM_FIN02 is for pulling in financial data onto RPM item from (object linked) Internal Order(IO)/PS Project(PSP).
-RPM_FIN02 do not recognize/goto cProjects for financials.
-cProjects can have its own account assigned IO/PSP
-cProjects Dashboard, (if all is well incl. evaluation) should display costs from assigned IO/PSP
-This cost does not reach RPM item
-Source of cProjects- if it is created within cProjects or from RPM Item, does not matter.
thanks,Mathavan

Create Logical System in R/3 system

Hi all,
I am trying to define logical system for xMII server in R/3 system using SALE transaction. But the logical system for xMII server doesn't already exist. So I have chosen to create one. Seems there is format like <sys_id>'CLNT'<client>.
1) How to create logical system for xMII server in this format?
2) How does R/3 know in which host xMII server is running? Do we specify that somewhere? Is there any other configurations for linking xMII host and logical system?
I am new to xMII and so not aware of the steps. Please help me out.
Points will be rewarded for helpful answers.
Regards,
Harini S

Harini
Welcome to xMII.
Though i nvr used such things from the SAP R/3 system side, i think the logical system name format must be something like SAPSYS<Number> for SAP Connection BUSCON<Number> for Business Connector. After hving defined the Logical System in R/3 System, u need to configure the SAP Business Connector Interface Action in xMII-based Business Logic Services.
In additional to this, hope this following links will help u to understand more
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3861e693-0e01-0010-e791-9b44d2693e6c
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/201769e0-3174-2910-e287-baa58d198246
Wait till there comes other some suggestions/solutions for ur quieries
Best Regards
Som

Logical system not updated in the business system adapter specific data par

Hello Guys,
I changed a logical system name in the sld for a business system and that that is not reflected in the Integration directory adapter specific data tab.
I did a cache refresh using :
1) sxi_cache --- Full cache refresh, delta cache refresh
2) Hard cache refresh
3) In ID "Cleared SLD data cahe "
4) Refreshed the exchange profile
But no use
Can you please tell how i can get the logical system name for the business system updated in the Integration Directory.

When you change it in SLD and if not getting replected in the ID...make sure you run the cache again, perofmr the comeplete cache....
there is an option under the adapter specific mesage attributes compare with SLD you can click that, is nthing happening after clicking it?
Run the cache in the ID are there any errors there?
check the RWB cache monitoring is everything green there?

Logical System Error

Hi AlL
I am working on the JDBC TO IDOC Scenario and when testing I get error:
Unable to convert the sender service ABC_Service to an ALE logical system
I check on the SLD under the Business System and what I find is that there is no LOGICAL SYSTEM NAME.
How to make the PI System to keep up the LS, on the TCode BD54 I created it
Role:
Pipeline URL:
Group:
Technical System: PI1 on saptrain1 Change...
Client: 001 of PI1
Logical System Name: #######
Thanks
Yonela

Hi Guys
On my JDBC TO IDOC Scenario when testing on the MONI I get the below error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="XICACHE">BUSINESS_SYSTEM</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>NO INTEGRATION SERVER</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error while refreshing the XI runtime cache</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
but on the SLD my Business System looks like this:
Role: Integration Server
Pipeline URL: http://saptrain1:8000/sap/xi/engine?type=entry
Group: No group assigned
Technical System: PI1 on saptrain1 Change...
Client: 001 of PI1
Logical System Name: LSJDBC
I have done
with this user : PIDIRUSER i have done the full cache
http://saptrain1:8000/CPACache/refresh?mode=full
CPA cache refresh (mode=full) successfully executed in 30937 milliseconds.
but when running
http://saptrain1:8000/sap/xi/engine?type=entry on the browser i get :
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Header />
- <SOAP:Body>
- <SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<faultcode>SOAP:Client</faultcode>
<faultstring>Empty HTTP request received</faultstring>
<faultactor>http://sap.com/xi/XI/Message/30</faultactor>
- <detail>
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="MESSAGE">EMPTY_HTTP_REQUEST_RECEIVED</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Empty HTTP query received; message processing not possible</SAP:Stack>
</SAP:Error>
</detail>
</SOAP:Fault>
</SOAP:Body>
</SOAP:Envelope
What I am I missing out
Thanks,
Yonela

ALE logical system - File -- XI -- R/3 scenario

Hi
I have the following scenario which I'm trying to run.
File --> XI --> R/3 scenario.
I have created a sender agreement XID|ASN_out|NBD where XID is my XI 3.0 system and NBD is my R/3 system. I have also created an interface determination and receiver determination.
The following error is in transaction SXMB_MONI in my XID system:
"Unable to convert the sender service to an ALE logical system"
Both XID and NBD are business systems defined in SLD and they have both a logical system assigned.
Why do I get this error and how can I fix it?
Best regards
Göran
Message was edited by: Göran Westin
Message was edited by: Göran Westin

Ok. I fixed the problem.
In the Integration Builder - Configuration > Select business system of choice > Menu > Service > Adapter specific identifiers > IDOC Adapter > Logical system - got a value after reading/refreshing it from the SLD.

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

Run CLEAN_REQREQ_UP withou logical system

Similar Messages

Maybe you are looking for