WE20 - post processing: permitted agent tab. 957 Views. Follow RSS Feed Hi , I need to create a inbound ...

I m transfering some data from client 800 to 100 on the same server . I have created rfc destination by sm59. logs log800 , log 100 , port zport. in we20 i have created patnter no log 800 with type ls . in outbound parameters i crated meassage tpye matmas (standard ), idoc matmas05. also i created message synch .

2010年6月16日 · Currently, WE20 is set up in the Post Processing: Partner type LI (Vendor), permitted agent tab with Type 'O' and an Agent group. We would eventually like for one person to be able to work one type of document for a vendor. To avoid coding changes, we are now testing with setting WE20 Type to User and the Agent to a specific user.

2009年4月8日 · WE20 OUTMOD issue. 184 Views. Follow RSS Feed Hi, I have set OUTMOD = 1, in oubound parametrs of the ...

2. WE20 (output type ZABC, configured with process code SD11, for receiving system or partner system) 3. VT01N/VT02N ( output type ZABC, configured with receiving system or partner system ) After that, in both cases ( create or change ) the IDOC created successfully. But the problem is i have to stop the process before triggering IDOC, for ...

2012年11月8日 · Therefore we already maintain back the rfc destination BIDCLNT220 in SAP QA's. We maintain it in RFC destinations (SM59), in partner profile (WE20) and in logical system (BD54). But we forget the RFCUSER password in SM59, then our basis reset the RFC password to a new password. We change the password in SM59 in SAP BW and in SAP ECC 6.0 QA's.

Hi experts, I have a question how to upload IDOC content to ERP system. We have a customized an IDOC structure which we designed with transaction WE30 and a new message type created with WE81 and WE82

2007年1月3日 · the new scenario has some selfmade IDoc and i already checked EVERYTHING (we20, we21, sm58, sm59, idx1, idx2, idx5, sm21) Following i give some hints what kind of problems i see. perhaps u can help me?! in the sender-system: sm58: IDOC_INBOUND_ASYNCHRONOUS, some mistake in IDX1 saying RFC-Destination is corrupt.