PLNSHP IDOC distribution through R3 system

Hi Experts!
I have a requirement to distribute data from APO through the standard PLNSHP IDOC to an external system. The problem is that I cannot distribute IDOCS directly from the APO system as the message broker (IBM MQ) is only set up in the R3 system and we are not allowed to set it up in the APO system.
Now I'n trying to use the R3 system as a gateway, but the problem here is that the standard IDOC PLNSHP does not exist in the R3 system. I created this IDOC in the R3 system and renamed the segments to start with a Z so it would fall in the customer namespace (I of course get error messages otherwise) and now the communication between the 2 systems to send the IDOC from APO to R3 works fine. However, R3 cannot process the incoming IDOC as the segment names and basic type differs...
So my question: Is there another way to do this? If not, is there a way to change the incoming IDOC data in the R3 system so the correct segment names and basic type (the ones in the customer namespace in R3) are used?
Thank you in advance!
Iwan Ferreira

Hi Raynald LaGuerre ,
Moslty IDoc Filtering will be done in Outbound Side & not in Inbound Side.
Though the System received IDoc from Different R/3 systems, it has to be filtered in Sending Systems itself and not by Receving Systems.
There wont be any use in filetering the IDoc at Receving side, since it utilises the Network traffic and reached the destination system.
Regards,
Anbalagan

Similar Messages

Error while posting idoc in the receiving system.

i have processed idoc in the same system( sending and receiving idoc in the same system ) by creating a dummy logical sys and uploading a text file for customer details.The outbound processing is succesful and it shows a status message 3. But duriing the inbound processing it shows status as 51 with error as 'ENTER VALID VALUE'. but when testing using we19 it is posted sucessfully without any error..is there anything that i have to configure to process inbound idoc sucessfully?? can any suggest me the correct method for doing this.. suggestions please..
thanks
vidya sagar

Hi,
you need to make sure that in WE20 inbound processing parameters for you LS is maintained propperly. You need to give correct function module and enter whether IDoc should be processed immediately or IDocs should be collected and processed as batch. Also you may check whether the distribution model (BD64) is maintained correctly for the specific message type in the system for inbound processing.
Regards,
Kai

Change Business Partner in CRM to trigger OutBound IDOC in R/3 system

Hi Team,
I am stuck on a requirement, We have a scenario were the Business Partner is created in CRM system
which creates a BDOC and is passed to R/3 system through an Inbound IDOC which triggers the Outbound IDOC to PI system. So far good.
The scenario we are getting stuck is when a Business partner is changed in CRM an IDOC triggered in R/3 system but this being a change the Change pointers are not called hence the IDOC which is supposed to be triggered for the PI system is not getting triggered.
Can you please tell me what steps should I take to trigger this Outbound IDOC from R/3 system?
I did some anlyasis and found a table which COM_BUPA_CALL_FU which contains a set of function module which is triggered in the sequence. Is this the solution or if you have any different do let me know.
Thanks,
Imran

Hi,
Did you add the entry for your new custom 'Z' long text inPITX Tcode in R3 side. Every long texts in CRM should be linked to R3 long text here. If there is no entry please add one and try changing the text in CRM.
Hope this helps,
Karuna.

IDOC's to external system in different queues.

Our external system( non sap ) can accept IDOC's HRMD_A, I wanted to know is there a way I can send
1.)Create
2.)Change
3.) Delete
in three different queues from my SAP system. I have setup the distribution model where i have defined the sender and receiver and message type but I wanted to know is there a way if this can be achieved.
Points will be awarded.
Ankur

Hi ankur,
u can send the idoc to non-sap system
when u execute an outbound process an ALE or EDI is processed
using ALE u can send the idoc to non-sap system also
Continued data exchange after a release upgrade without requiring special maintenance
regards,
sindhu

IDOCs in R/3 system

Hi,
Please provide me the frequently used transactions in R/3 system about the IDOCS and how to monitor the IDOCS in R/3 system and how to resend the IDOC and cancel the IDOCS in R/3 system.
Thanks & Regards,
Y.raj.

Hi
Please check some of the following tcodes of idoc.
WE19- Test tool of IDOC processing
WE02-Idoc list
WE05
SM58-Transaction RFC
WE21-IDOC processing ports
WE20-Partner profiles
SM59-RFC destination
BD64-Model View distribution
WE81-Message Types
WE30-Develop Idoc types
WE31-Segments
Thanks
Prasad Nemalikanti

XI system idoc transfer to SAP system.

hi ,
this is parthasarathi,i am using ALE/IDOC.basically i need to transfer idoc from XI system to SAP system.
can any one help me out in this case.
my system is SAP system ie inbound system.
i am using message type HRMD_A and idoc type is HRMD_A04.
1)what are the steps i need to take in the inbound system..?
2)what is the function module i need to use?
how this is reflecting SAP system.
3) idoc will be generated in XI system with employee master data and the same idoc generated in XI system ,that idoc should be send to SAP system ie inbound system.
can any help me out ..
thanks.
partha.

Hi parthasarathy,
To connect the two systems u need a connection called as RFC.(sm59)
medium of transaction is port (we21)
IDOC Intermediate document - travelling (or) data carrying from 1 - 2
create partner profiles for sharing the appln. (we20)
application linking and enabling (ALE)--used to generate an idoc in sender side and post it in the receiver side.
r3 - r3 -use ALE - transactional rfc
r3 - non r3 - use EDI (electronic data interchange) - file port
bridge (bd64) - distribution model view
to view idoc's (we05,we02)
types of data
1. master data -- ale -- eg. send materail(bd10),customer(bd12),vendor(bd14)
2.transactional data -- ale
3.control data -- cts(correction and transport systems)
Hope this gives u overall idea of how to use idoc's.
Regards,
Nagarajan.

ALE/Idocs Distribution Model

Hi
I am facing one problem in distribution model. Im trying to send idocs from one system to another. The distribution model has been created and been distributed to the other system. so no error comes in the source system. Even the idocs are generated without error.
Now in the receiving system,
1) after the distribution model is created in this system by distribution option from the source system and when i try to generate the partner profile in this system. It gives the error that " No messages have been defined for the selection conditions in the model". Though everything is created here.
2) the idocs reaches in this system but in error state. Again the error says partner not found.
Now am not able to understand how to rectify this problem. when the model is distributed why this partner is not being created automatically.
can anybody help???
regds
sanjeev

This is the error that comes when I run the FM (FM is active) contrary to the error:
Runtime Errors         CALL_FUNCTION_NOT_ACTIVE
Except.                CX_SY_DYN_CALL_ILLEGAL_FUNC
Date and Time          20.11.2007 12:13:39
Short text
     The function module is not active or contains no code.
What happened?
     The function module "ZIDOC_INPUT_ZADR_MESSAGETYPE" is called, but
     cannot be found in its function group.
     Error in the ABAP Application Program
     The current ABAP program "ZIDOC_INPUT_ZADR_MESSAGETYPE==FT" had to be
      terminated because it has
     come across a statement that unfortunately cannot be executed.
Error analysis
     An exception occurred that is explained in detail below.
     The exception, which is assigned to class 'CX_SY_DYN_CALL_ILLEGAL_FUNC', was
      not caught in
     procedure "FUNCTION_CALL" "(FORM)", nor was it propagated by a RAISING clause.
     Since the caller of the procedure could not have anticipated that the
     exception would occur, the current program is terminated.
     The reason for the exception is:
     The program "ZIDOC_INPUT_ZADR_MESSAGETYPE==FT" contains the CALL FUNCTION
      statement.
     The name of the function module to be called is "ZIDOC_INPUT_ZADR_MESSAGETYPE".
   but "ZIDOC_INPUT_ZADR_MESSAGETYPE" cannot be found in its function group.
   Possible reasons:
   a) The function module "ZIDOC_INPUT_ZADR_MESSAGETYPE" has not been activated.
    Therefore,
      it cannot be found at runtime.
   b) The Function Library contains an incorrect entry for
    "ZIDOC_INPUT_ZADR_MESSAGETYPE".
   c) The function module contains no code, even FUNCTION ... ENDFUNCTION
      is missing.
Missing RAISING Clause in Interface
    Program                                 ZIDOC_INPUT_ZADR_MESSAGETYPE==FT
    Include                                 ZIDOC_INPUT_ZADR_MESSAGETYPE==FT
    Row                                     69
    Module type                             (FORM)
    Module Name                             FUNCTION_CALL
Trigger Location of Exception
    Program                                 ZIDOC_INPUT_ZADR_MESSAGETYPE==FT
    Include                                 ZIDOC_INPUT_ZADR_MESSAGETYPE==FT
    Row                                     93
    Module type                             (FORM)
    Module Name                             FUNCTION_CALL
Source Code Extract
Line SourceCde
   63 *
   64 DATA: OTHERS(1).
   65 *
   66 FORM EXISTENCE_CHECK CHANGING VARIA.
   67   VARIA = 1.
   68 ENDFORM.
   69 FORM FUNCTION_CALL.
   70   CLEAR %_OWORKFLOW_RESULT.
   71   CLEAR %_OAPPLICATION_VARIABLE.
   72   CLEAR %_OIN_UPDATE_TASK.
   73   CLEAR %_OCALL_TRANSACTION_DONE.
   74   CLEAR %_OIDOC_CONTRL.
   75 %_OIDOC_CONTRL = %_IIDOC_CONTRL.
   76   CLEAR %_OIDOC_DATA.
   77 %_OIDOC_DATA = %_IIDOC_DATA.
   78   CLEAR %_OIDOC_STATUS.
   79 %_OIDOC_STATUS = %_IIDOC_STATUS.
   80   CLEAR %_ORETURN_VARIABLES.
   81 %_ORETURN_VARIABLES = %_IRETURN_VARIABLES.
   82   CLEAR %_OSERIALIZATION_INFO.
   83 %_OSERIALIZATION_INFO = %_ISERIALIZATION_INFO.
   84 * TRANSAKTION = 'Repo', PROGRAM = REPORT
   85   IF ATRA = '1'.
   86     SET RUN TIME ANALYZER ON %_INTERNAL.
   87   ENDIF.
   88 IF DESTI IS INITIAL.
   89 IF DEBUG = '1'. BREAK-POINT AT NEXT APPLICATION STATEMENT.
   90 ENDIF.
   91 DEBUG = SPACE.
   92 GET RUN TIME FIELD TIME1.
>>>>> CALL FUNCTION 'ZIDOC_INPUT_ZADR_MESSAGETYPE'
   94 EXPORTING
   95 INPUT_METHOD = %_IINPUT_METHOD
   96 MASS_PROCESSING = %_IMASS_PROCESSING
   97 IMPORTING
   98 WORKFLOW_RESULT = %_OWORKFLOW_RESULT
   99 APPLICATION_VARIABLE = %_OAPPLICATION_VARIABLE
100 IN_UPDATE_TASK = %_OIN_UPDATE_TASK
101 CALL_TRANSACTION_DONE = %_OCALL_TRANSACTION_DONE
102 CHANGING
103 IDOC_CONTRL = %_OIDOC_CONTRL
104 IDOC_DATA = %_OIDOC_DATA
105 IDOC_STATUS = %_OIDOC_STATUS
106 RETURN_VARIABLES = %_ORETURN_VARIABLES
107 SERIALIZATION_INFO = %_OSERIALIZATION_INFO
108 EXCEPTIONS
109 WRONG_FUNCTION_CALLED = 001
110 ERROR_MESSAGE = 002
111 OTHERS = 003.
112   IF ATRA = '1'.

Non-updated Idocs found in Source System

Hi Experts,
I am getting an error Non-updated Idocs found in Source System
Plz help me to resolve this issue.

Hi
BD87 Update Idocs manually.
1. When you look in the Monitor screen for the first time on a day you mostly will see some Loads that have yellow traffic lights. When you click on the lowest line of the Load (with the time of Load start) you will get the next popup screen:
2. Here you can click on the "Yes" button. The Load specification window (right side of the screen) will now be filled with data.
3. You can now start the manual processing of the IDocs. You go to the "Details" tabpage of the right window. You right click on the line with the red traffic light stating "Request IDoc : IDoc ready to be transferred to application" on the "Details" tab page of the Load. In the option menu that appears choose the option "Update manually in OLTP" (click it).
4. You will get to the next screen (which is in fact a transaction in the source system (SAP R/3) where you can update the IDoc that is send by the source system)
5. Now click the "Excecute" button on the left of the screen (or press the F8 button on your keyboard). You will get to the next screen:
6. This states that the IDoc has been passed through to BW. You return to BW by clicking the "Back" button (or pressing the F3 button on your keyboard) twice. After the first time you will see the previous screen and after that the Monitor screen again.
7. You will now see that the Status of the Load has turned to yellow or green. When it is yellow you will have to wait a little time (the execution of the Load in BW is still running) and by clicking "Refresh Details" button on the left upper side of the screen (or pressing the F8 button on your keyboard) you will see the Load turn green.
Hope it helps

IDOCs Distribution Model: filter whitout Filter group

Hi guys!
In my IDOCs distribution model of IDOCs with Message Type "Z", when i try to add a Filter, in the popup dialog to enter the Filter group i canot see nothing...only a line with a "Dependent on class membership: Requires classes to be defined in the sending system"
but not show the expected fields like Sales organization, or the Account group
¿this is a custonizing problem?
Best Regards,
Antonio

Hi,
First, create ALE Filter objects via BD95 (if they do not exist yet)
Secondly, assign ALE Filter objects to your message type for the appropriate segment: BD59
Then, run bd64 ...
Regards,
Jakub

Sending Idocs/tRFC through saprouter ?

Hello,
I understand that it is technically possible to send Idocs (tRFC) through a saprouter.
But I couln't find any post/blog/articleof people who tried this setup.
Anyone has tried to send Idocs through a saprouter ?
Anything I should consider (besides adjusting the tRFC connexions) ?
Thanks
Raoul

Hi Raoul,
SAPROUTER allows or establishes a cross landscape/network communications. Eg: from your SAP system to SAP AG servers for remote support.
As far as I know, there is not method/procedure to process IDOCs through saprouter.
Thanks,
Siva Kumar

IDoc distribution

Hi,
I have one query while dealing with ALE configuration. Suppose I have to distribute IDoc in multiple system i.e. one sending say client 100 & receiver say client 200, 500, 700.
How to deal if we have to distribute Idoc's to multiple systems.
Plese tell me step by step starting from configuration.

hi neha
yes i think its possible.
u go to transaction BD87.
there u can select range of partner system to which the idoc is to be send
and then select the idoc to be send in that
but i suppose u will have to create the distribution model for them.
please try using this option
regards
ravish
<b>plz reward if useful</b>
Message was edited by:
ravish goyal

Package distribution through a bit torrent network

make pacman a bittorrent client, and servers seeders.
would this be too complicated and not worth the trouble? im sure someone already thought of this.
if noone is seeding, servers would offload traffic from each other.
and if users choose to seed, well, we all know how fast movies download, right?
any downsides of this package distribution topology? after all, this was the reason bt got created in the first place.
im sure package signing would be a requirement..

Xyne wrote:
karol wrote:What is the use case for this? Who needs it?
A full p2p package network would allow anyone to distribute binary packages on par with the official packages. Users wishing to share their own binary repos would no longer need (access to) a dedicated server. Basically, everything on the AUR would be available in binary format somewhere, which would be very useful for packages with long compilation times and/or many build dependencies. It would open the doors for architecture-optimized binary package distribution through some sort of tagging system. With time all architectures would be represented. It would also make the entire package distribution system far more robust, as everything currently relies on a single server to distribute new packages to the mirrors.
There are advantages to not providing packages via bittorrent. Primarily, I ofter release packages, close my laptop and go to work. So the signle server at leasts guarantees seeds. Many of the AUR packages would have ~0 seeds, making that not very useful.
Xyne wrote:It would also eliminated the arbitrariness of the current "Trusted Users" and even the devs, not all of whom are equally trusted. It would be easier for users to decide whom to trust on an individual basis, including others who are not officially associated with the distro. The current trust system would remain, but it would not be "imposed" to the same degree.
I already disable some Trusted User's keys in my pacman keyring.
Xyne wrote:Instead of ordering repos, it would be possible to order packagers (with a matching dependency graph), which would make it easier to do things such as pull in all the Haskell packages from arch-haskell without having to give arch-haskell priority over everything in the community repo.
Until I package something haskell as part of a rebuild and then someone at Arch Haskell decides to provide a glibc build. Crappy example I know, but there is a point there!
If bittorrent were to be used, I recommend it using web seeds with our mirrors and only used to spread the load for large downloads.

RSAR2318 : IDoc type for source system T90CLNT090 is not available

Hi all,
I am working on BI + ECC 6.0. Have created a ODS object using RSA1OLD. While activating the ODS, am getting this error:
1. Error:
R7I028
Object could not be activated
2. Error:
RSAR238
IDoc type for source system T90CLNT090 is not available
Error when creating the export datasource and dependent objects
Error RSAR238 : IDoc type for source system T90CLNT090 is not available
I have already checked trx & dtps, but could not find resolution.
Kindly help me with this error.
Thanks and regards,
MS

M Sharma wrote:
But how exactly can I create when T90CLNT is not active? Help please.
Yes, you would need to check with BASIS team how they have created an alternate source system (for debugging) & prepare a RFC b/n these systems. Can you just check the settings in the source system and BI source system...and check the source system for the same BI system. Right click > Check and then do a restore or take the help of basis to fix it. What I think is a possible solution is : RSA1 > Source system > Search System > Right Click > Activate

RSAR238 : IDoc type for source system T90CLNT090 is not available

Hi all,
I am working on ECC 6.0. Have created a ODS object using RSA1OLD. While activating the ODS, am getting this error:
1. Error:
R7I028
Object could not be activated
2. Error:
RSAR238
IDoc type for source system T90CLNT090 is not available
Error when creating the export datasource and dependent objects
Kindly help me with this error.
Thanks and regards,
Dhanapal

Hi,
Check the same in SDN..
Object ZDUMMY could not be activatedMessage no. R7I028
Re: DSO Activation problem
http://sap.ittoolbox.com/groups/technical-functional/sap-bw/test-cases-for-module-human-capital-management-1425016
http://sap.ittoolbox.com/groups/technical-functional/sap-bw/idoc-type-for-source-system-t90clnt090-is-not-available-message-no-rsar238-1431565
Thanks
Reddy

Receiving IDocs from non-SAP system ...

Hello guys,
I have problem with implementing IDoc-XI-IDoc scenario. The sender system is a subsystem (non-SAP system) sending IDocs but XI is not able to receive them. I thing the IDoc metadata can not be found.
Logical system name of the sender is IF6020DEV. I registered the system in SLD. In Integration Directory I imported the Bussines System IF6020DEV to my scenario and I created communication channel of type Sender IDoc Adapter in it.
In IDX2 I created new port called IF6020DEV and I copied needed metadata into the port. But it doesn't work. Probably I don't do it right because I'm beginner with SAP XI.
Could you give me any advice how to configure XI for receiving IDocs from non-SAP system?
Thank you in advance!
Regards
Zbynek

Thank you very much. The issue described in refered discussion is almost same issue what I'm solving. Unfortunetally the described solution dosn't work for me.
The sender system still returns following error. I know you probably won't understand it because you don't know the subsystem, but maybe you could get some idea what is wrong.
05/29/09 16:09:19.482 idoup2 Logon...
05/29/09 16:09:19.482 idoup2 RfcOpenEx (TRACE=1 CLIENT=110 USER=xxxxxx LANG=D LCHECK=1 GWHOST=xxxxxx GWSERV=3361 ASHOST=xxxxxxx SYSNR=61 PASSWD=<password>)
05/29/09 16:09:19.529 idoup2 Logon RfcOpenEx result=1
05/29/09 16:09:19.607 idoup2 Call to (IDOC_INBOUND_ASYNCHRONOUS) failed (3)
05/29/09 16:09:19.607 idoup2 Handle=1
05/29/09 16:09:19.607 idoup2 key............:
05/29/09 16:09:19.607 idoup2 status.........:
05/29/09 16:09:19.607 idoup2 message........:IDoc-Adapter Eingang: Der Absenderport ist initial
05/29/09 16:09:19.607 idoup2 internal status:
05/29/09 16:09:19.607 idoup2 idoc_upload failed with rc=(3), try(2)
05/29/09 16:09:20.607 idoup2 key............:IDoc-Adapter Eingang: Der Absend
05/29/09 16:09:20.607 idoup2 status.........:EXCEPTION SYSTEM_FAILURE RAISED
05/29/09 16:09:20.607 idoup2 message........:IDoc-Adapter Eingang: Der Absenderport ist initial
05/29/09 16:09:20.607 idoup2 internal status:
05/29/09 16:09:20.607 idoup2 idoc_upload failed with rc=(18), try(1)
05/29/09 16:09:21.607 idoup2 Logoff...

PLNSHP IDOC distribution through R3 system

Similar Messages

Maybe you are looking for