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

Similar Messages

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

Deletion of logical system

hi friends ,
i created a logical system long back and i have sent idocs succesfully from crm system to Tibco System , recently i have deleted this logical system and i created a new logical system , now the problem is if i trigger an idoc , two idocs are getting generated one with previous logical system and another with new logical system , but the previous logical system is not visible in SALE OR BD54 can u please suggest me how it is getting trigered or i need to delete it at some other tcode please suggest
please help me it is very urgent
with Regards
abaper

hi dilip ,
thanks for your reply ,
actually i deleted the old logical system because it is assigned to a client , and added a new one with out assigning to the client and i have changed in we20 also , and its working fine but the thing is that it triggering two idocs one for the new logical system with status 03 and with 0ld with status 29 or 37 with standard message type CRM_XIF_PARTNER_SAVE AND WITH OLD LOGICAL SYSTEM so please suggest me how can i restrict the older one , and i am unable to know where the system is picking the older logical system even thought i have deleted in SALE
PLEASE REVERT ME YOUR SUGGESTIONS
THANKS,
SRINIVAS

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 names after system copy

Hi!
I installed a new SAP system via System Copy (SAPINST) approach.
As a consequence the old logical system names have been copied.
Question:
What is the appropriate approach (tcode, report) to change the logical system names of each clients of SAP system?
Thank you very much!
regards
Jürgen

Logical System Names
When data is distributed between different systems, each system within a network has to be clearly identifiable. The u201Clogical systemu201D deals with this issue.
A logical system is an application system in which the applications work together on a common data basis. In SAP terms, the logical system is a client.
Since the logical system name is used to identify a system uniquely within the network, two systems cannot have the same name if they are connected to each other as BW systems or as source systems, or if there are plans to connect them in any way.
Although SAP does not recommend that you connect test systems to production systems, a test system can have the same name as a production system. This makes copying production systems to test systems a lot simpler.
You are only allowed to change the logical system name of a system if the system is not connected to any other systems, because changing the logical system name would render all the connections to other systems useless.
In BW, you make the settings for the logical system names in the BW Customizing Implementation Guide under Business Information Warehouse ® Connections to other Systems ® General Connection Settings. In the source system, you make the settings for the logical system in the Implementation Guide under Cross Application Components ® Distribution (ALE) ® Basic Settings.
Note SR047 lists names that cannot be given to BW systems, because they are reserved for internal use.
Logical system names must contain capital letters and numbers only. SAP recommends the following naming convention for logical system names: .

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.

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.

How to trigger EDI output type by logical system

Hi,
I am trying to propose a delivery output on delivery document based on logical system.
I have maintained partner profile by logical system. In the partner profile, i have given the delivery output type and the process code.
I have also maintained condition records for the delivery output.
I would like the system to propose the delivery output not by ship to party or sold to party but by the logical system.
Because i do not want to maintain 3000 customers in the partner profiles, instead trigger the output by logical system.
Please let me know, if anyone has gone thru this situation and resolved.
Thank you in advance.
-Naga

Hi,
First thing you should make sure that, when you create the output type , partner function should have an entry for EDI - LS combination.
Secondly , make sure you have option for EDI transmission on the output type (medium 6).
Third, when you create partner profile for LS, make sure you give partner function as LS, even though SAP gives warning that its not required.
Last but not least, i didnt create any distribution model , because when i created distribution model and generate partner profile, system was not generating the profile properly.
I am not sure, whatever i did was right, but its working for me.
-Naga

Logical System in file 2 idoc

Hi
I am developing an scenario of file to idoc.
My problem is, when it is generating the idoc in target system, the Parner Number in control record is filling with the logical system name given when creating the business system.
I tried changing the logical system name with actual partner number which I want but giving an error ' The selected integration server already has a business system with logical name "pidclnt001". Select a different integration server or change the logical name. '
Can anybody advice me, is it not possible to create two scenarios to send same Idoc to same system ?
Regards,
Shylesh

Hi Shylesh !
You need to enable the header mapping option in your receiver agreement to overwrite the Logical System name that is sent to the R/3 destination system...which now is the Logical System name linked to your sender system (info is in SLD if is a business SYSTEM or in the Adapter Specific identifier attributes if it is a business SERVICE)
You cannot have more than 1 business service/system with the same Logical System name...but you can overwrite the sender logical system name that arrives to the destination R/3 system using the header mapping section of the receiver agreement as noted above.
Regards,
Matias.

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 systems for modeldata and RFC metadata

Hi All,
I want to know how I can display the my own created logical system names under the drop-down menu when i have to select the logical system names for modeldata and rfc metadata. I don't want to them to be written instead i want them to be one of the options in the drop down menu, as we have them in the FLIGHT_LIST_INIT example found in the sample applications and examples.
Thanks in advance
Srikant

Hi,
While creating SLD for your R/3 systems give the desired name of wht u want instead of logical name.
For configuring the same refer the link below :-
http://help.sap.com/saphelp_erp2004/helpdata/en/29/e0b75c2b7d40c5bfbda82e905b701c/frameset.htm
Regards,
guru

BDLS updating logical systems in CIF models?

Hi
The BDLS tool can be used to update logical system names in systems. As I understand this tool is often used when copying systems (Production system to Q system for instance).
In a situation where you copy the productive system to the Q system:
Does anyone know if BDLS is capable of updating the logical systems in the generated CIF models that you get copied from the productive system? In this case you'd get a big chunk of models that point to the wrong logical name. If you could get the target system changed in the generated model then you could save a lot of time in generating and activating models.
Any comments much appreciated
Simon

Hi,
I am not too sure if this thread is followed. I was looking for some info where we had a similar issue recently when we did a production refersh to Quality and all our integration model variants are pointing to our production system.
Our basis team has taken all the necessary steps like BDLS etc, but we had this issue. I dropped a message to SAP and they gave a report name RCIFVARIANTCHANGE to change the logical system name from old one to the new one for CIF variants.
Thanks,
Murali

AC 5.3 Logical systems and multiple Physical systems

HI all:
We have set up a Logical System, and then have hooked up 2 Physical systems to it. Based on the documentation from SAP, the rule set (and the way we set it up) is at the Logical system level.
Physical system #1 is reporting the correct results, however, Physical system #2 results are not complete. My understanding is that both Physical systems should be drawing from the rule set based in the Logical system.
Results: Physical system #1 - correctly identifies 10 risks
Physical system #2 - incorrectly only identifies 5 of the expected 10 risks.
Role assignment to user is exactly same, authorizations are exactly the same. The User/Role/Profile Full Sync has been repeated as part of troubleshooting.
Has anyone experienced this? I'm looking for ideas/options on where to investigate why the results are different.
Thanks
Margaret

HI:
Thanks for answering!! I'm having trouble understanding the answers, sorry.
When you have a logical system...you upload the rules once to that system, and generate them. Then when you set up a physical system and hook it up to the logical system...the 1st, 2nd or 3rd physical system....they all use the same ruleset. The whole concept (as I understand) is that the use of Logical and Physical systems...and putting the rule set on the Logical system so you don't have to worry about one rule set taking precedence over another, is an advantage, if this is possible (ie: we don't have multiple rule sets).
Where should I be checking that the risks are defined properly? The rule set is the delivered one from SAP. The functions and risks match what we had (plus more) in the CC 4.0 system.
The first physical system we set up (example: Development) works fine, and all regular SoD risks are coming up as expected. When we added another system (example: Test)...the results of SoD analysis were incomplete.
Does that help clarify? Perhaps I'm just missing something?
Margaret
Edited by: Margaret Sokolov on Apr 28, 2009 4:34 PM

Reg: Table name where logical system name will store in R/3 and CRM..

Hi
We are trying to replicate the sales order from CRM 5.0 to ECC 6.0. we mainatined publication, site, subscription and rfc connections. When the sales order is created in the CRM the BDOC is getting posted but it is picking up the wrong logical system which we were using earlier. Due to this wrong logical system, out-bound queue is getting generated in CRM but In-bound queue is not getting generated in the ECC.
Can anybody tell me where (in which table) we need to modify the things for getting the correct logical system.
Regards

Hi,
In CRM: look for the table CRMMLSGUID. This should have the logical system name of the R/3 that it is connected to CRM and also the GUID. To check if the GUID is correct cross check with GUID from R/3 table CRMPRLS.
In R/3: look for the table CRMRFCPAR. This will give you all the RFC connections that R3 is connected to. If you want to check whether the CRM RFC value is defined correctly compare it with RFC destination in the Administration Console (smoeac) from CRM.
If the entries are matching then the systems are connected correctly if not you need to look at the RFC destinations from SM59 transaction.
Hope this helps.
Thanks,
Karuna.

ALE logical system to client

Hi,
Is assignment of SAP logical system to client mandatory...
I understand that we can give dummy names like SAP_A as logical systems but is it mandatory to assign them to clients..
I think Idoc can be sent to the respective SAP system through ports instead of a particular LS

this client assignment to logical system is about your sending system.
the steps for ALE config are following only:
1)     IMG > SAP NetWeaver > Application Server > IDoc Interface / Application Link Enabling (ALE) > Basic Settings > Logical systems > Define Logical System
2)     IMG > SAP NetWeaver > Application Server > IDoc Interface / Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Configure Predefined ALE Business Processes > Logistics > Logistics <-> External Systems > External Transportation Planning Systems > Maintain ALE Port Definition (Transaction WE21)
3)     IMG > SAP NetWeaver > Application Server > IDoc Interface / Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Global Organizational Units > Cross-System Company Codes (Transaction OB72, SALE, OBB5)
4)     IMG > SAP NetWeaver > Application Server > IDoc Interface / Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Maintain Distribution Model and Distribute Views (Transaction BD64)
5)     IMG > SAP NetWeaver > Application Server > IDoc Interface / Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Configure Predefined ALE Business Processes > Logistics > Master Data Distribution > Proposal for distribution model: Customer and vendor masters (Transaction WYL2)
6)     IMG > SAP NetWeaver > Application Server > IDoc Interface / Application Link Enabling (ALE) > Modelling and Implementing Business Processes > Configure Predefined ALE Business Processes > Logistics > Logistics <-> External Systems > External Transportation Planning Systems > Maintain ALE Partner Profiles (Transaction WE20)

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

Similar Messages

Maybe you are looking for