Sending IDOC through INOT

I want to create IDOC for transaction IW29( display notifications) . For this i am using transaction INOT (send notification). But when i am executing INOT ( using notification no , user status field, and target system fields ) its showing -- No IDOCs created. Kindly help in solving the issue.
Thanks.

Ferry,
I think this may be what you are suggesting, but in different words. Either way, it would likely solve the problem, though not as cleanly as I'd like since now I've got to make changes to the MB_CREATE_GOODS_MOVEMENT BAPI.
(1) create a new segment called ZZSDATA1
(2) make this segment a child of the E1BP2107_GM_ITEM_CREATE segment
(3) put the overflow information in the new segment
I can't just add another field to the segment, with 1 byte or 1000 bytes. All of the data for the segment has to fit within one 1000 byte sdata field.

Similar Messages

Sending IDOCS through transaction PFAL

Hi,
We have a requirement to send idocs through transaction PFAL for a set of PERNRs for all infotypes.What is the way to go about this?
Thanks ain Advance!
Regards,
Nejuma Iqbal

hi
you cannot send IDocs thru PFAL transaction.
you can send HR Master Data thru PFAL.
yes you can send the Pernrs as they are Components of Organizational Elements.
Here is the Procedure to send Personal Numbers:
1.Execute the transaction PFAL.
2.Give the object type as P.
3.Give the Pernr values in Object ID field
4.Select the transfer mode as Update
5.In the Receiving Partner give your receiver name
6.Give the message type as HRMD_A in the Message Type field.
7.Dont change the remaining values.Keep it as such.
8.Execute the Program.
Also keep in mind that while sending the HR data you need to follow the certain sequence
unless otherwise your data wont be replicated successfully.
Here is the sequence O,S,P and C.
Means before sending P you should send O and S.
Cheers,
Abdul Hakim
Mark all useful answers..

Send IDoc through adapter IDoc_AAE

Hi, guys!
We have SAP PO version 7.4
We need to setup the unloading of the IDoc from BI in PO
I used the following sources:
http://scn.sap.com/docs/DOC-31398
http://help.sap.com/saphelp_nw74/helpdata/en/34/66c81241874285851e2497aa6f0573/content.htm?frameset=/en/c2/91865252c84716b3b8be394851c9c0/frameset.htm
http://scn.sap.com/docs/DOC-34155
http://scn.sap.com/people/william.li/blog/2011/05/04/configuring-pi-730-java-idoc-adapter
http://scn.sap.com/community/pi-and-soa-middleware/blog/2013/08/05/connect-multiple-sap-ecc-clients-from-java-idoc-sender-adapter-by-resource-adapter-cloning
http://scn.sap.com/community/pi-and-soa-middleware/blog/2010/10/21/pixi-pi-73-new-java-based-idoc-adapters-configuration-sender-receiver--teaser
but it doesn’t work.
I created Jco provider xi_idoc_default_pid (where PID replaced the SID BI system)
I created the RFC in PO for BI xi_idoc_default_ destination _pid (ping successful)
in inboundRA have in ProgrammID: xi_idoc_default_pid
in destination - xi_idoc_default_ destination _pid
I created Sender channel (manual and default)
I created in BI in sm59 RFC T
I input the program xi_idoc_default_pid , which was created in the first step, in field, and input
gateway and host - my PO
but the test does not pass the RFC.
Could you please tell me, what the problem is?
I configured IDoc_AAE receiver. data arrives in BI, help me to setup up send IDoc from BI in PO
Thanks.

Hi,
We also faced same issue for the RFC created from our ECC to SAP PO (netwaever 7.4 ) system. It is TCP/IP connection.
there are 2 solutions:
1) set gw/acl_mode parameter to 0 in ECC system resolved the issue. Ofcourse you need restart of Source(ECC) system. But it is not recommended in Prod systems
2) Regenerated Reg info and sec info files in Source system(ECC) and created them in target system also and kept them in /usr/sap/SID/SYS/SCS01/data.
The created files are given below for reference.
Reginfo file:
P TP=* HOST=*
P TP=* HOST=*
Secinfo file:
P TP=* USER=* USER-HOST=* HOST=*
P TP=* USER=* USER-HOST=* HOST=*
BR
Ravikiran

Sending IDoc through FunctMod - what if edidd-sdata size 1000

There are several function modules to which we can send formatted IDoc data, and I am using one of them just fine (IDOC_INBOUND_SINGLE, if it matters). However, one thing all of these FMs have in common is that they use the EDI_DD40 structure (or it's equivalent), which has an SDATA field of 1000 bytes.
My problem comes from the need to use a standard SAP-delivered IDoc (MBGMCR01) that has a length of 1061 bytes. This wouldn't necessarily be an issue as long as all of the data I needed was within the first 1000 bytes, but it's not.
Any ideas on how to handle this?

Ferry,
I think this may be what you are suggesting, but in different words. Either way, it would likely solve the problem, though not as cleanly as I'd like since now I've got to make changes to the MB_CREATE_GOODS_MOVEMENT BAPI.
(1) create a new segment called ZZSDATA1
(2) make this segment a child of the E1BP2107_GM_ITEM_CREATE segment
(3) put the overflow information in the new segment
I can't just add another field to the segment, with 1 byte or 1000 bytes. All of the data for the segment has to fit within one 1000 byte sdata field.

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 through Proxies ABAP-PI ports

HI,
Please suggest what are the pros and cons of sending IDOCS through proxies.
When should we design like this ?
Thanks,
Harsha

First of all why u want to send IDOC through proxy as SAP provided all std IDOCs and IDOC approach to send data to XI,only u have to configure the things in R3 as well as XI.
Cons will be u have to write the abap code for sending IDOCs and difficult to IDOC monitor.
Just have a look at the below blog:-
/people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems
chirag

SEND IDOC using JCO(Priorty -HIGH)

Hi, all
I am facing to send IDOC through JCO(Java Connector Object). if some body have idea then reply me.
In previous dovelopment i was using BAPI for save data . Now my requirement is IDOC.
Regards,
Sandeep
Edited by: sandeep verma on Jan 2, 2009 2:41 PM
Edited by: sandeep verma on Jan 2, 2009 2:41 PM

hi sandeep,
check this thread this will give the idea
Re: Send an IDoc over JCo
Sending Idoc to a java application
Sending IDoc to java
let me know uneed any further info
bvr

Creating sales order through BAPI - do not want to send idoc confirmation

Hi guys!
I'm creating a sales order using BAPI BAPI_SALESORDER_CREATEFROMDAT1. The system was cuztomized to send an idoc through an output type, so whenever this BAPI is executed an idoc is sent.
My problem is that I do not want the Idoc to be created when using this BAPI.
Is there a way not to use an output type when using the BAPI?
Thanks in advance for your help!

Use an output requirement that stops the proposal of the output. You'll want to make sure that it works in both immediate and delayed modes, e.g., you can't use a field-symbol (or the KOMKBV1 user exit) for access to T180-TCODE or to the CALL_BAPI value in memory. You might want to try the VBAK-ERNAM value, since you probably use a specific (non-dialog) user for the call. Otherwise, use another field to identify a BAPI call and check that field in the requirement.

ALE Error while sending PO IDOC through EDI

Hi Experts,
                  I am sending one PO IDOC through EDI but I am getting the following error:-
                  Message no. B1130.
                  "Too many recipients found for message type ORDERS in the ALE model"
                  How can I solve this error ? Please guide me in this regards as this is an
                  important issue with urgency.
Thanks & Regards
Jitendra Gujarathi

Please check this discussion thread
Re: Too many recipients found for message type in the ALE model

Unable to send PO through IDOC

Hello!!
Good Evening.
I have a problem, while sending PO through idoc orders03, some idocs are going fine and some are stucking and i cross checked the succesful and failed idocs and came to know that, one segment is missing.
How this has happened.
Actually, E1EDKA1 is the segment.
How to track this issue and rectify the mistake.
Reply ASAP...!!

It is the case that from sender system, you are sending data in a segment(we31) which you have not maintained in the idoc type(we30) in the receiver system.there may be an extension which you have to add in the message type in the patner profile.
doing this will completely resolve the issue.
you may reprocess your i/b idoc from BD87 after maintainng the extension(we30)
let me know if you have any doubt

How to send Outbound IDocs through an RFC-enabled FM

Good day to all;
A partner system (AS/400) wants to use a Java Connection to execute a RFC Function Module, in SAP, that will then return a collection of IDocs.
Currently, the Function Module builds the IDocs, but I'm not exactly sure how to simply send those IDocs back to the AS/400.
If anyone can help in this regard, that would be great.
My current thoughts are to use Master_IDoc_Distribute, but then I imagine that requires a port configuration for the AS/400. And if this is the case, does that mean that SAP will send the IDocs back itself instead of using the RFC interface?

Hi Tavares,
If you want to send outbound IDoc to AS/400 (external system), you need to setup file port (t/code WE21).
For RFC interface, you need to setup RFC file port with RFC Destination (t/code SM59). In this case, SAP will send IDoc (individually or batch) to receiver system (AS/400). Perhaps you need a middleware for data transformation, if AS/400 does not perform data mapping for outbound IDoc.
For FTP interface, you need to setup flat/XML file port for outbound. then you can FTP the file to AS/400 later on.
In addition to file port configuration, you also need to setup partner profile for outbound parameter (t/code WE20) and the distribution model (t/code BD64).
Hope this will help.
Regards,
Ferry Lianto

Creation of IDOC through abap program.

hello all,
I hav created idoc through abap program. I hav used FM 'Master_idoc _distrribute'.this program creates an idoc but giving status 30. can any one tell me how to get status 03. I hav already created port, Logical sys,partner no.,distribution model.
My Program is as follows:
ABLES : CRMD_ORDERADM_I,CRMD_ORDERADM_H,CRMD_SCHEDLIN.
DATA : S_CTRL_REC LIKE EDIDC OCCURS 0 WITH HEADER LINE,"Idoc Control Record
       ORDER_NO TYPE CRMT_OBJECT_ID VALUE '5000000032'," SEGMENT ORDER DATA
       PRODUCT TYPE CRMT_ORDERED_PROD VALUE 'SRV_01',
       QUANTITY TYPE CRMT_SCHEDLIN_QUAN VALUE '1.000'.
DATA : ZORDER LIKE ZORDER_NUM OCCURS 0 WITH HEADER LINE.
DATA : T_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE.     "Data Records
DATA : T_COMM_IDOC LIKE EDIDC OCCURS 0 WITH HEADER LINE. "Generated Communication IDOc
CONSTANTS :
C_ZRZSEG1 LIKE EDIDD-SEGNAM VALUE 'ZORDER_NUM'.
PARAMETERS : C_MESTYP LIKE EDIDC-MESTYP DEFAULT 'ZORDER_IDOC2', "Message Type
              C_RCVPRT LIKE EDIDC-RCVPRT DEFAULT 'LS',          "Partner type of receiver
              C_LOGSYS LIKE EDIDC-RCVPRN DEFAULT 'BSNL_OUT',
              C_RCVPOR LIKE EDIDC-RCVPOR DEFAULT 'A000000006',
              C_SNDPOR LIKE EDIDC-SNDPOR DEFAULT 'SAPBCD0000',
              C_SNDPRN LIKE EDIDC-SNDPRN DEFAULT 'BCDCLNT100',
              C_IDOCTP LIKE EDIDC-IDOCTP DEFAULT 'ZORDER2',
              C_SNDPRT LIKE EDIDC-SNDPRT DEFAULT 'LS'.          "Destination System
***START-OF-SELECTION
START-OF-SELECTION.
PERFORM GENERATE_CONTROL_RECORD.
PERFORM SEND_IDOC.
*&      Form generate_control_record
FORM GENERATE_CONTROL_RECORD .
S_CTRL_REC-RCVPOR = C_RCVPOR. "Receiver Port
S_CTRL_REC-MESTYP = C_MESTYP. "Message type
S_CTRL_REC-IDOCTP = C_IDOCTP. "Basic IDOC type
S_CTRL_REC-RCVPRT = C_RCVPRT. "Partner type of receiver
S_CTRL_REC-SNDPOR = C_SNDPOR. "SENDER PORT
S_CTRL_REC-RCVPRN = C_LOGSYS. "Partner number of receiver
S_CTRL_REC-SNDPRT = C_SNDPRT. "Sender Partner type
S_CTRL_REC-SNDPRN = C_SNDPRN. "Sender Partner Number
APPEND S_CTRL_REC.
ENDFORM.                    " generate_control_record
*&      Form send_idoc
FORM SEND_IDOC.
ZORDER-ORDER_NO = ORDER_NO.
ZORDER-PRODUCT = PRODUCT.
ZORDER-QUANTITY = QUANTITY.
APPEND ZORDER.
T_EDIDD-SEGNAM = C_ZRZSEG1.
T_EDIDD-SDATA = ZORDER.
APPEND T_EDIDD.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
    EXPORTING
      MASTER_IDOC_CONTROL            = S_CTRL_REC
    TABLES
      COMMUNICATION_IDOC_CONTROL     = T_COMM_IDOC
      MASTER_IDOC_DATA               = T_EDIDD
    EXCEPTIONS
      ERROR_IN_IDOC_CONTROL          = 1
      ERROR_WRITING_IDOC_STATUS      = 2
      ERROR_IN_IDOC_DATA             = 3
      SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
      OTHERS                         = 5.
IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ELSE.
    COMMIT WORK.
    LOOP AT T_COMM_IDOC.
      WRITE:/ 'IDoc Generated - ', T_COMM_IDOC-DOCNUM.
    ENDLOOP.
ENDIF.
ENDFORM.                    " send_idoc
I hav created segment , basic type,message typealso and release also .I also linked them.
Plz help me.
Hemlata

Hi Hemalatha,
Just call this Progream RSEOUT00 from your Zprogram and pass the basic parameters like IDOC number, Basic type,Partner number etc.
You can check the parameters by executing the Program RSEOUT00.
This Program will change the status of your IDOC 30 to 03.
Thanks.
Note:Reward Points if you find useful.

Idoc to file scenaro ( sending IDOC as it is to NON-SAP)

Hi Experts,
I am doing idoc to file scenario.
I am having SAP R/3 system with 3 clients(100, 200 & 300), IDOC is comming from SAP R/3( any one of the client)
In this is scenario, I am sending IDOC-XML as it is to the NON-SAP system.
I heard that, i can do in 3 ways. those are
1. Without any repository objects: you can go ahead with No interface mechanism on the target side.
2. Without message type: create a message interface whose message type would be idoc itself
3. With message type: export the IDOC as xsd file and re import the xsd file as an external definition.
If i go without IR objects,Please tell me whether i need to create Interface objects(i.e. DT,MT & MI) & Mapping objects (MM & IM) or not for the reciever.
MY ASSUPTION:
step1: I will import the IDOC into IR.
step2: Directly i will go to the ID without desiging any object in IR ( is it ok).
Is my assuption or correct or not?, please tell me.
So please tell me the entire scenario how to achieve this.
Please help in this issue.

Hi Laxmi
1. Without any repository objects: you can go ahead with No interface mechanism on the target side.
-- Not Possible
2. Without message type: create a message interface whose message type would be idoc itself
-- No need for the Message Interface for IDOC. You will directly import the IDOC and do the Mapping
3. With message type: export the IDOC as xsd file and re import the xsd file as an external definition.
-- This is Possible. you are export the IDOC as XSD File and reimport the same. so there is no difference. If you are going to change the IDOC Structure then this is possible.
Here I am sending some links which are useful for IDOC to File Scenario. Please go thru the links given below..
While doing an IDOC -> XI -> File scenario, The Points to noted are:
1. You dont need a DT, MT or a message interface for the IDOC as it itself acts as the Message Interface.
2. You import the IDOC and use the same in your mapping.
3. In this configuration note that you dont have a sender agreement as you dont have a sender IDOC adapter.
If it is that you wanted to send an IDOC from XI (File to IDOC) , then in this case:
points 1 and 2 will remain, but the 3 will not. You will need a sender agreement for the file and a receiver agreement for the IDOC.
IDOC -> File scenario ref:
IDoc-XI-File scenario
File -> IDOC ref:
File to IDOC
To be able to trigger your IDOC from the SAP ISU system, you will have to set the partner profile in we20. Select your Business System (mostly under Logical system) and then create Outbound entries for whichever IDOC you want to trigger.
You define your basic type also in your partner profile settings, Please go thru the following links to get a better idea about partner profile:
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b833243d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7cd343d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/32/692037b1f10709e10000009b38f839/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5e/b8f8bf356dc84096e4fedc2cd71426/frameset.htm
Also, I would suggest that you go through this blog by michal if any issue arises,
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
I hope this answers your query.
Award the POINTS if it is useful **
Cheers
Vasu

Error in Sending IDoc to XI

Hi Gurus,
We are not being able to send Idocs from one of our Back-end SAP system. The Idoc status in we05 is successful but it doesn't reach XI. So we checked in SM58 in the Back-end R/3 system and there it shows the error:
No Service For System SAP*** , Client *** in Integration Directory
We tried almost every possible setup
-The System is defined in SLD and has the logical system name.
-The Adapter Specific Identifiers are correct for the corresponding business system in ID
-The RFC destination in R/3 system is defined.
- Read through other similar threads in SDN about the similar problem.
Do anyone have a more definite solution for this particular problem? The other R/3 systems are connected to XI system and all IDocs from those systems are arriving at XI.
Waiting for your valuable advices!
Regards,
Suddha

Hi All,
We had eventually found the solution to this problem we were facing in sending IDoc, though I couldn't manage to update the thread with the solution. I think this would be a very helpful information for those who face similar problems.
Let me describe the scenario first briefly,
We are sending an IDoc (Idoc extension), from SAP system to XI and then send the XML payload as mail attachment to the receiver via receiver mail adapter. Since this is a cross company transaction, hence we have configured the scenario as a B2B in ID, which means we use Parties for both the sender and receiver.
Now in the ID we had done all necessary configurations and used parties and services under Party. For the sender SAP system we assigned a Business System to Sender Partner, configured the Party Alternative Identifiers correctly. The ports were created in IDX1.
On the other hand the SAP system was also configured successfully - including Partner Profile, Distribution List, RFC destinations and ports.
In SLD we created Business System for the SAP system and in ID the Business System under party had the correct logical system name as Adapter Specific Identifiers.
But after all these, the IDoc was not arriving at XI, though in R/3 the status of the IDoc was 03 in we02. When we checked in sm58 in R/3, it showed us the error message that "No Service For System SAP*** , Client *** in Integration Directory".
The cause to this problem was:
We created (assigned from SLD) Business System only under Party (Sender), as this was a B2B scenario, and didn't create (assign) a Business System without Party, as we didn't need one at all in the scenario configuration. And this the reason behind this error. When an Idoc arrives at XI, before the Inbound IDoc adapter converts the IDoc to IDoc XML using IDoc metadata............it checks in Configuarion to see if any Service without Party (Busniess System) is defined for the Sender SAP System and Client (The SNDPOR and MANDT field values from IDoc Control header are taken as the SAP SID and Client). If it finds one it accepts the IDoc and starts the Normalization (Sender Party, Service......in the message header) and IDoc to XML conversion. If it cannot find an Service without Party in ID for sender system, it rejects the Idoc with the error message that we saw in sm58 in backend R/3 system.
In this step the Service under Party doesn't help, because at this point the Inbound IDoc adapter can not deterimine the sender party.
Hence for sending an IDoc from an SAP system to XI, we need to have an Service Without Party in ID, whether or not we require it in our actual Scenario Configuration, which is ofcourse not a case for the Reverse Scenario, ie Sending an IDoc into SAP system from XI.
This is the similar with BC adapter as well. I was already aware about this behaviour of BC adapter from my past experience and this actually helped to troubleshoot this IDoc adapter problem.
This was ofcourse a useful and new learning for me and hope would be helpful to others as well. Let me know if anyone has any doubts on this.
Regards,
Suddha
Edited by: Suddhasatta Guha on Aug 28, 2008 1:03 PM

Error in Sending IDOC

Hi,
i am working with the Scenario IDOC to IDOC using middleware PI.
Done with Whole Process .
But when i Sending an IDOC through WE19 it went Succesfully(i checked it in WE05).
But when i checked in SM58. then there is an error in sending my IDOC.
Transaction IDX1: Port SAPETS, client 800, RFC destination contain error.
Please let me know where might me the problem ??
Thanks
Deepthi

Hi,
Check the RFC destination connection from PI to ECC... looks like there is connection from PI to ECC to retrieve the metadata....
HTH
Rajesh

Sending IDOC through INOT

Similar Messages

Maybe you are looking for