SAP WE20 Transaction Code: Partner Profiles

This check determines whether the message flow from and to the specified partners is unambiguous. It also checks whether the partner profiles have been maintained for each message flow.

"You can go to the transactions Maintain Distribution Model (transaction code BD64), Assign RFC Dest. to Log. Systems (BD97), and Partner Profiles (WE20)."

https://help.sap.com/docs/SAP_NETWEAVER_740/8f3819b0c24149b5959ab31070b64058/4abb4b70479926c4e10000000a42189b.html

You can remove Central User Administration (CUA) again, simply by performing the reverse of the set up first in the central system and then in all child systems. The first three steps (transactions SCUG, SCUM, and SCUA) are combined in report RSDELCUA, which you can start by choosing the Delete button in transaction SCUA. You then cancel settings in transactions WE20 and BD64, and if necessary also in transaction SM59.

https://help.sap.com/docs/SAP_NETWEAVER_740/c6e6d078ab99452db94ed7b3b7bbcccf/ea9abf3b4f995f1ce10000000a114084.html

This topic describes the handling of IDocs with partner function LS (logical system) in the IDoc control header. IDocs with other partner functions like LI or KU are described in a separate topic.

"Use ALE customizing transaction WE20 to maintain the partner profile and partner number, for example of type logical system : RCVCLNT089/LS."

https://help.sap.com/docs/SAP_NETWEAVER_731/6dbe2ddcde6a4087858c533f8032445b/48a9bcca7e28674be10000000a421937.html

To optimize the ALE distribution of Central User Administration, you can execute the outbound processing and inbound processing of IDocs in the background (see Background Processing: Concepts and Functions).

"When testing, it may be useful to temporarily set Pass IDocs Immediately. If, however, you have a large number of parallel dialog processes for IDocs in the central system and in the child system for mass processing in transactions SU10, PFCG, and PFUD, use the following settings in transaction WE20 for the outbound processing:"

https://help.sap.com/docs/SAP_NETWEAVER_740/c6e6d078ab99452db94ed7b3b7bbcccf/4da56ceaf5da1f69e10000000a42189b.html

This check tests transaction BD82 ( Generate Partner Profiles) and can also start the generation.

https://help.sap.com/docs/SAP_NETWEAVER_740/8f3819b0c24149b5959ab31070b64058/4ab38cc3549a6d8ce10000000a42189c.html

If a system is no longer required in the system landscape, or the central system is inactive and a user must be maintained, remove the child system from Central User Administration (CUA) with report RSDELCUA, which you can start in transaction SCUA by choosing Delete .

"In transaction WE20, under Partner profiles for Partner Type LS , delete the message types CCLONE and USERCLONE for the receiving system (child system)."

https://help.sap.com/docs/SAP_ERP/142f8559883b4c11966ebfb99dd61164/ea9abf3b4f995f1ce10000000a114084.html

In an active CUA landscape, you want to maintain users or company addresses in a child system or redistribute users and company addresses from the central system to the child systems. However, the corresponding users or company addresses in the child system remain unchanged. The entries in the log of transaction SCUL have the status Distribution unconfrimed. In the central system, although transaction BD87 shows that all USERCLONE or CCLONE IDocs were sucessfully sent to the child system, transaction BD87 in the child system shows that none of the send IDocs was received. This can occur if the...

"Call transaction WE20 in the central system."

https://help.sap.com/docs/SAP_NETWEAVER_740/c6e6d078ab99452db94ed7b3b7bbcccf/b3e54d2de29a36419845e0d6c6a803ee.html

Um die ALE -Verteilung der Zentralen Benutzerverwaltung zu optimieren, können Sie die Ausgangs- und Eingangsverarbeitung der IDocs im Hintergrund ausführen (siehe Hintergrundverarbeitung: Konzepte und Funktionen ).

"Whrend der Tests ist es u.U. sinnvoll, temporr IDOCs sofort bergeben einzustellen. Falls Sie jedoch viele parallele Dialogprozesse zu IDocs im Zentral- und im Tochtersystem bei der Massenverarbeitung in den Transaktionen SU10, PFCG und PFUD haben, verwenden Sie in Transaktion WE20 folgende Einstellungen fr die Ausgangsverarbeitung:"

https://help.sap.com/docs/SAP_NETWEAVER_701/6f323fd26c4b1014996399b1f02898ae/4da56ceaf5da1f69e10000000a42189b.html?locale=de-DE

Mit dieser Prüfung können Sie den Testlauf der Transaktion BD82 ( Partnervereinbarungen generieren) durchführen und ggf. auch die Generierung starten.

https://help.sap.com/docs/SAP_NETWEAVER_731_BW_ABAP/8f3819b0c24149b5959ab31070b64058/4ab38cc3549a6d8ce10000000a42189c.html?locale=de-DE

Gültige Quelle Der Eintrag im Orderbuch erfüllt die notwendigen Voraussetzungen. ...

"Geben Sie den Namen des logischen Systems ein, an das die generierten IDocs bermittelt werden. Es handelt sich hierbei normalerweise um den logischen Namen des EDI-Subsystems. Die Partnervereinbarungen beziehen sich auf dieses logische System (siehe Partnerart LS in der Partnervereinbarung, Transaktion WE20)."

https://help.sap.com/viewer/5217586808064011af1167fefdc21919/7.0.4/de-DE/72d28c51c6dbdd0de10000000a441470.html

View the full list of resources, SAP Help/Wiki pages and Q&A for WE20