Sending IDocs as 'control messages' to a Logical System

Hi all,
I have defined an external Logical System to where I send Idocs. The Idocs are received and processed by a SAP Java Connector on that LS.
At the moment, when for example a purchase order is created for a specific vendor, a message to that vendor is sent through ALE, and the receiver port for that Vendor is set so that it resembles/is sent to the Logical System.
My question is, is it possible, for example when you create a purchase order, to define the message control in such a way that a regular 'New Printout' (or other message) is send to the Vendor (as it normally would), as well as an IDoc message for that purchase order to the Logical System: so send 2 messages to different systems upon creation of the purchase order .
The main idea is that the IDocs are sent to the Logical System to keep track of the actions done by a user, transparant to the user, so that its actions are logged.
Hope this is clear,
David

Yes, You can do it through outbound IDoc. Create another output types and configure the same from NACE and the processing would be done through EDI.
Then you need to configure the partner profile in WE20 with that output types.
Thanks
Subhankar

Similar Messages

Sending IDOCs from an MDMP to a Unicode system

Colleagues
I have been trying to send IDOCs containing Chinese characters from an MDMP system to a Unicode system. The data is not being translated from the Chinese code page 8400 to Unicode format.
To date I have created a new IDOC segment, within the original IDOC, which contains the language dependant data preceded by a language element. I have also maintained SM59 on the receiving system (Unicode) to mark the sending system (in SM59 defined as an R/3 connection) as non-unicode, and activated the MDMP settings and mapping the language key ZH to codepage 8400. I have also checked that the language key and code page is valid in the unicode box.This still doesnt work.
I was under the impression that the RFC system would translate the IDOC line by line and if it found a language key in the segment translate it using the code page assigned to that language, but this doesnt seem to be the case. The sending system is 4.5C and the receiving system 4.7.
Is there anyway to get this to work without playing with the IDOC processing routines such as IDOC_INBOUND_ASYNCHRONOUS? Is there something Im missing?
Thanks in advance for your help.

Hi,
Perhaps you may want to try to use IDoc file interface instead of RFC.
You can use standard program RSEINB00 to process and post the IDoc file.
Regards,
Ferry Lianto

How to send IDOC with extended message type MATMAS

Hi Experts,
I am looking for a solution to send open PR & open PO related data for diffrent materials through as IDCO in XML file.
Scenario is i have to show a report in a 3rd party system for open PR & open PR that too will come after selection some materials. That means select a materials & it will show all the open PO & related data in a report.
The rough idea for the solution i got is I can save the data in XML file in the system. For this i have to send IDOC. but the problem is there is no message type for PR. IF i am not wrong i can extend the MATMAS05 for a segment that will have PR related info.
Now what to do with that how to send the IDOC do i need to create another report to send IDOC or i can send the extended one through BD10. I tried it but it shows error message "0 communication idoc sent" so I dont no y such error is coming i think i am not filling the extended idoc. But again my QUestion is how to do that.
Can i use BAPI also for such work, if then how it can be helpful.
If anyone have any other solution Please help me out of this.
Regards,
Nik

Hi Mahesh,
Thanks for your reply.
My requirement is bit different. i have to send Open PR data for diffrent materials. In a 3rd party application user will search for few materials which will generate a report that will show the PR related data for those material.
That means for few selected materials there will be few PR's which may be open, i have to show those in my report.
Eg: material A, B. are in PR 00001 & material B, C in PR 00002.
After selecting materials A to C report will show
Material                 PR No                   Item No                Quantity
A                           00001                    10                             1
B                           00001                     20                            3
B                           00002                     10                            3
C                           00002                      10                           1
Same thing i have to do for open PO & open Sales order also.
Can u please help me to provide the solution how can i proceed for it. U have given the Message type & a bapi how it will help in my issue?
I got a suggesion from someone that extend message type matmas for PR, PO, SD related data & send the idoc. but i am confused how to pass that much data ina single IDOC.
Regards,
Nik

Message Type to Logical Systems

Hi all,
in SAP PI 7.1 I have a question for you.
With transaction WE20 (into R/3 system) I find the logical system with each message type (inbound or inbound)
My question is:
Is there a transaction which is the contrary?
That is,for a specific message type , I obtain all the associated logical system?
Thank all
Davide

Hi Davide,
Do you want to see all the logical systems that are associated with a particular message type?
Then you can go to tables EDP12 (Pass MESTYP value to get the logical system in the field RCVPRN where RCVPRT = LS
Regards,
Ravi

Send Idoc flat file message in JMS receiver adapter

Hello,
I am working on a scenario where we send Delvry 03 idoc from ECC to external system. To external system, we send the whole Idoc in flat file structure through JMS queue. I have used Idoc to flat file program in my interface mapping and have configured JMS receiver adapter with just default Module configs but, I am getting an error in communication channel monitoring for the messages.
Please note that Idoc xml to flat file structure conversion is already done in the mapping, I need to just pass this idoc flat structure in the jms adapter. Hence ther eis no content conversion i nthe adapter..
Please give some inputs..Here are the modules in my receiver adapter and nothing else..
SAP XI JMS Adapter/ConvertMessageToBinary
SAP XI JMS Adapter/SendBinarytoXIJMSService
The error I get is in audit log
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: No transition found from state: ERROR, on event: process_commence for DFA: CC_JMS_R:ca336a6689f837da8bd3387140fc4447
in turn the message has this error if I open the message
Whitespace is not allowed at this location. Error processing resource 'http://host:port/mdt/messageconten...
and it shows one of the lines from idoc..flat file
Any idea is greatly appreciated..Thank you..Thanujja

The difference in what I suggest is that it is way simpler.
Maybe you did not understand this, so will try to explain it better. Its not the best thing to do, but if JMS adapter doesn't budge then you can give it a shot.
1. You continue to use the ABAP mapping in your interface mapping to map the Idoc xml to Idoc flat.
2. Write a Java Map that will take the output of the ABAP mapping ; and then create a XML output which would be something like,
<Root>
<Idoc_Flat>
<Data>ABAP Mapping Output<Data>
</Idoc_Flat>
</Root>
3. Now use the simple content conversion in the JMS adapter to convert this to flat file.
Regards
Bhavesh

Message type from Logical system

Dear All,
I need develop an inbound where the info is coming from HR system. I found Message Type HRMD_A can be utilized for the development, however im not so sure if the message type HRMD_A is originally exist in my R/3 4.7 or it was being distributed by the HR system previously via BD64.
Please comment on how can i check for it.
Below are the related info for Message type HRMD_A that i found in my R/3 4.7:
Message type - HRMD_A
Basic type - HRMD_A06 (for release 620)
Process code - HRMD
Inbound FM - IDOC_INPUT_HRMD
Thank you.

Hi Atish,
Thanks for your reply. Let me recap my scenario and please point me out if i'm wrong again.
For my case, Message type HRMD_A exist in both R/3 and HR system. Since it exist, then we do not need to distribute from HR again via BD64. Right?
IDOC can be passed from HR to R/3 without any additional config right? Assume partner profile and RFC destination has been configured correctly.
Please comment.

Cannot send or recieve text messages through Ford Sync system since latest O.S. update 10.3.1.1779

My Blackberry Classic easily connected to my Lincoln's Sync system. I was able to receive and send text messages through the Sync. Since the latest O.S. update, I can no longer connect sms services through Sync.
Should I restore to previous O.S.?

Yes my particular issue is not like yours. However, there have been many other laptop users experiencing similar problem to yours after 3.10 kernel. Mostly it seems to be bumblebee users that experience your problem with the blank screen. We do know that nvidia have yet to make their official drivers work with kernel 3.10 and up. The drivers in the Arch repository have been patched to work with 3.10. From what I have seen, this also only seem to be affecting laptops with newer nvidia gpu's. I fear there is not much to do with this problem until nvidia give official 3.10 kernel support.
My suggestion would be to stick with 3.9.9 kernel and the drivers that work with it, and don't upgrade those packages until nvidia has addressed these issues. If you have a look at the nvidia forums you will see quite a number of topics mentioning black screen when starting x on 3.10 kernel, and also a thread for the system dying. Reading some of the threads there may help you keep up to date on whether or not the issue seem to be solved.
https://devtalk.nvidia.com/default/board/98/

Send IDoc to Multiple Ports

Hi,
I have a custom IDoc message type YYY17101[Custom Type]. I need to send IDoc using this message type to 2 different rfc destination. The two RFC are
1. SAP R/3 system
2. XI system
My question is which partner profile type i have select to send IDoc using message type YYY17101.
Can i use partner profile type LS for sending IDoc to SAP R/3 and Partner pofile type US for XI system?
Thanks
aRs

Hi aRs,
Your challenge is in fact not so very difficult.
First you define both R/3 and XI as an LS-type partner in your system, since both systems need to receive a message from your target system.
Then you must use transaction BD64 to create a modelview (or choose in SALE the path Modelling and Implementing Business Processes --> Maintain Distribution Model and Distribute Views).
Create your own NEW model.
Use Add message type to add your specific message and supply your own LS system as source and the first target LS system (R/3).
Use again Add message type to add again your specific message and supply your own LS system as source and the second target LS system (XI).
If you view your model you will see ONE source system (your own) and TWO target systems (each with the same message below it).
You can add filters to the message (to prevent incorrect messages to be send) if these are defined in your own IDoc.
Now you can distribute this model to the target systems (in the menu choose: Edit --> Modelview --> Distribute.
If the partners in question can be reached this goes OK.
If all went well, go to the target systems and start transaction BD64 and select the model there. Then choose from the menu: Environment --> Generate partner profiles.
At this point your ALE customization is complete and communication has been setup.
So as you see, it is possible.
Regards,
Rob.

Difference between client system and logical system

Hi all
Can any one explain about the client system and logical system??
When this message type will comes in to picture at the time idoc processing??
Thanks and Regards
Arun Joseph

hi Arun,
I am giving the complete info on idoc.pls chk once.then ur issue will be solved.ok
and to know the diffrence between client and logical system very keenly go thru this link
https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=abouttheclientsystemandlogicalsystem&adv=false&sortby=cm_rnd_rankvalue
IDOC Administration
Step 1: Tcode: WE 46
Setting the Global Parameter for IDOC Interface
Step 2: Maintaing a Logical System
Path: From the ALE Customizing in IMG, choose Sending and Recieving Systems,
Logical Systems, Define Logical systems
Go to Spro transaction
Step 3: Allocating Logical systems to the Client
Path: From the ALE Customizing in IMG, choose Sending and Recieving Systems,
Logical Systems, Assign Client to Logical systems
Go to Spro transaction
Step 4: Setting up an RFC destination
Tcode: SM 59
Path: From the ALE Customizing in IMG, choose Communication, Define RFC
Destination
You can also do the Advanced Settings in the RFC Destination
Step 5: The PORT definition
TCode: WE 21
Path: From the ALE Customizing in IMG, choose Sending and Recieving Systems,
Systems in Network, Asynchronous Processing, Assign Ports, Define Port
Step 6: Generating Partner Profiles
TCode: BD 82
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, PArtner Profiles and Time of Processing, Generate Partner Profiles
Step 7: Distributing the Model
TCode: BD 64
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, Maintain Distribution Model and Distribute Views
Technques for Distributing the Master Data:
Technique 1: The Push Approach
Executing the Process:
TCode: BD 10
Path: from the ALE Main Menu, choose Material Data Distribution, Cross
Application, Material, Send
Technique 2: The Change Pointer Technique
Enable Change Pointers Globally
TCode: BD 61
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution, Replication of Modified Data, Activate
Change Pointers
Enable Change Pointers Globally
TCode: BD 50
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution, Replication of Modified Data, Activate
Change Pointers for Message Type
Specify the Fields for which Change Pointers are to be written
TCode: BD 52
Path: From the ALE main Menu, Choose ALE Development, IDOCs, Change , Define
Change-Relevant Fields
How the Classification system works:
Creating a Class Type
TCode: O1 CL(it is CAPITAL O)
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution,Distribution using Object Classes, Maintain Class Types
Maintaing Status for the Class Types:
TCode: O1 CL(it is CAPITAL O)
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution,Distribution using Object Classes, Maintain Class Types
Maintaing Classification Status:
TCode: O1 CL(it is CAPITAL O)
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution,Distribution using Object Classes, Maintain Class Types
Maintaing Classes:
TCode: CL 01 (it is zero)
TCode: O1 CL(it is CAPITAL O)
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution,Distribution using Object Classes, Maintain Classes
Allocating classes to the Logical Syatems
TCode: BD 68
TCode: O1 CL(it is CAPITAL O)
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution,Distribution using Object Classes, Assign classes
to Logical systems
Filering at the IDOC level:
Identify the Filter Object:
TCode: BD 59
Path: From the ALE main Menu, Choose ALE Development, IDOCs,Data Filtering, Assign Filter Objects
Type to IDOC Field
Modify the Distribution model
How Segment Filtering Works:
Configuration:
Configring the segment-filtering technique is a one-step process.Just specify the segments to be filtered
TCode: BD 56
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution,Scope of the Data for Distribution, Filter IDOC Segments
The Reduced IDOC Type:
The reduced IDOC type allows to get down to the field level and specify the fields a recieving system does not need.
The System still needs the fields, but this has no effect on the recieving system because each field has a null value,
represented by a forward slash(/) in the field.
TCode: BD 53
Path: From the ALE Customizing in IMG,choose Modeling and Implemantation Business
Process, MAster Data distribution,Scope of the Data for Distribution, Message Reduction,
Create Reduced Message Type
IDOC:
Complete Documentaion on any IDOC using TCode: WE 60
IDOC Display Tool: TCode: WE 02 or WE 05
IDOC DEfinition components:
Segment Components:
1. Segment Type (E1, Z1)
2. Segment Definition(E2, Z2)
3. Segment Documentation(E3, Z3)
E- SAP Defined
z- Custom Defined
IDOC runtime componets:
control Record:
Data Record:
Staus Record:
First Create the Segments using TCode: WE 31
and then create the IDOC using TCode: We3 30
first release the segments and then IDOC.
Creating a new Basic IDOC Type:
STEP 1: Analyze the Data:
STEP 2: Create Data Elements:
STEP 3: Create Segments:
STEP 4: Create Basic IDOC Type:
1. Execute TCode: WE 30
2. Select the Create new option and enter a description for your basic IDOC type
3. click the IDOC name, and click the create icon.
Enter the segment type and its attributes.
4. Keep on adding the segments as in step 3.
5. Save the basic IDOC type
Step 5: Release the Segment Type and Basic IDOC Type
STEP 6: Transport the Segments and Basic IDOC Type
Extending a Basic IDOC type:
STEP 1: Analyze the Data:
STEP 2: Create Custom Segments:
STEP 3: Create the IDOC Type:
STEP 4: Release the custom Segment and IDOC Extension
Develop the function module for fteching the Data and then inserting the data into IDOC using
EDIDD(for control Record) and EDIDC table(for DATA Record)
Configuring the Systen for IDOCs
Configure an Outboubd Process that uses Message Control
Step 1: Create a new Message Type
TCode: We 81
Path: From the Area menu of EDI, choose Development, IDOC Type/ Message
Step 2: link the IDOC type to the Message Type
TCode: We 82
Path: From the Area menu of EDI, choose Development, IDOC Type/ Message
Step 3: Create a new Process Code
TCode: We 41
Path: From the Area menu of EDI, choose Control,Outbound Process COde
Step 4: Create or Change a Partner Profile
TCode: We 41
Path: From the Area menu of EDI, choose IDOC,Partner Profile
Configure an Outboubd Process for Stand-Alone Programs
1. Create a new message type
2. Link the IDOC type to the Message Type
3. Add the message to the ALE Distribution Model(use BD 64)
4. Create or change the Partner Profile
go through the following site to have screen shots.
http://www.****************/Tutorials/ALE/ALEMainPage.htm
thanks
karthik
reward me points if usefull

Logical system name for acknowledgement in BPM

Hi,
I have a szenario:
IDOC --> BPM --> MAIL
Inside BPM I check the message and depending on an xml-element I stop the process or I send the message by mail.
When I stop the process the BPM sends back an acknowledgement and in SXMB_MONI I can see an error of the acknowledgement:
"Sender Test_BPM_IDOC_TO_MAIL kann nicht in ein ALE Logisches System umgeschlüsselt werden" (Sender can not convert in a ALE logical system)
What can I do?
Possible Solution 1:
I can define my BPM "Test_BPM_IDOC_TO_MAIL" as a logical system (including WE20 for ALEAUD).
Possible Solution 2:
I can enter an existing logical system name in the "adapter specific attributes".
BUT it is not use the same logical system name twice (BAD ... or is there a workaround?
Is Solution 1) a common way?
Thanx
Regards
Wolfgang Hummel

Hi,
there are many ways:
some for aleaud are described in my book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi"><b>Mastering IDoc Business Scenarios with SAP XI</b></a>
>>>>Is Solution 1) a common way?
no this is not good a good idea
BTW
you can also supress aleaud raport IDX_NOALE
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

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

ALE: Logical system

Hi
I want to send IDOCS from SAP(client100) to a non-SAP system through an RFC port.
I created 2 logical systems.
100SAP : Sending system
NONSAP : Receiving system
Am i correct to say that i need to assign LS-NONSAP to client100. or should it be LS-100SAP ?
Message was edited by: Giovanni Baumann
Message was edited by: Giovanni Baumann

Hai
Check the following Setting
ALE IDOC
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Thanks & regards
Sreenivasulu P

SLD Business System with or with out Logical System If so, which Log system

Hi
I'm in confuse with the Logical System when creating a Business System in SLD.
Our requirement is LEGACY -- PI/XI -- ECC.
When I create Business sytem in SLD, I need to give a Logical System. Which system (Is it xi/pi or ECC ) Logical System to be provided?
Thanks.

>
Pothana Yadav wrote:
> Hi
>
> I'm in confuse with the Logical System when creating a Business System in SLD.
> Our requirement is LEGACY -- PI/XI -- ECC.
>
> When I create Business sytem in SLD, I need to give a Logical System. Which system (Is it xi/pi or ECC ) Logical System to be provided?
>
> Thanks.
if you are using File to IDoc scenario then need to define logical systems for both business systems you are going to create for
i.e they will be used as sender and receiver partners in case of logical systems
if need more details check the below blog
/people/rajeshkumar.pasupula/blog/2009/03/16/unable-to-convert-the-sender-service-to-an-ale-logical-system
check the same for how logical system are used in this case...
note above will be helpful in case of only idoc scenario..else no need of creating logical systems even though target sysstem is ECC
HTH
Rajesh

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

BD54 not allowing to delete logical system

Hi,
We did system refersh from Prod to Quality and further we found that while starting BDLS it was not allowing to do so. We got message like <Target> logical system already existing . Further checks revealed that in BD54 that our quality system's logical client entry was already there which would normally come after running BDLS post DB refresh activity for System refresh). Because of this issue we are unable to dlete the quality entry in BD54 and to further start our BDLS acitivty.
Please to confirm us as we are stuck.
Thanks & Regards,
Ashish Robinson
SAP BASIS Support

Hi ,
Thanks all. I resolved my issue.
Solution:
1) Removed quality system RFC "STQCLNT002" from SM59 just to b sure nothing was blocking
2) Also entry of STQCLNT002 needs to be removed from BD97.
3) Further if you try to use ENTER when you try to delete entry inBD54 of quality it won't allow ,how many time you may try pressing enter to get away with the warning message. So solution here is to further double clieck on that warning message (in BD54) and see where its blocking . It will show you some method where its blocking .
4) To locate the method use txn BD64 and scan through the entires to get to the affected link (here it was STQCLNT002).
5) Be careful, do not delete the entry of STQCLNT002 itseld but actually the corresponding leaves of the methos needs only to be removed to over come the blocking in BD54 (where we wanted to remove the entry of STQCLNT002).
6) Now goto BD54 and and you can easily remove entry of STQCLNT002.
7)Now BDLS would easily start.
Regards,
Ashish Robinson
Please grant me point if you find the answer useful. It surely did work for me absolutely fine.

Sending IDocs as 'control messages' to a Logical System

Similar Messages

Maybe you are looking for