Problem while triggering IDoc

hi,
When i am triggering idoc from R/3 , it is saying idoc transferred to port,
but when i am checking the idoc in XI system idx5 , i am not able to view the idocs,
What could be the reason for this?
Also when i am creating distribution model in BD64 and then saying distribute , it is giving this message:
Model view BANK_CREAT has not been updated
Reason: Maintenance systems for model view BANK_CREAT are not identical
..... Maintenance system in sending system DMYCLNT702
..... Maintenance system in receiving system DMYCLNT100
Note:DMYCLNT702 - Testing client
DMYCLNT100 - Development
Urgent help needed,
Thanks,
Loveena

Hi,
Chk the following details which will be helpful:
A Summary of the Steps to be carried out to enable a SAP R/3 System send Idocs to SAP Exchange Infrastructure.
First - Maintain the Sender R/3 System:
SM59 : Create a RFC destination to XI
WE21 : Create a TRFC Port ->Specify the RFC Destination Created
BD54 : Create a Logical System for the Idoc Receiver
WE20 : Create Partner Profile ->Maintain Outbound and the Inbound Parameters
Second - Log on to XI System:
SM59 : RFC Destination for Sender System
IDX1 : Create the port to get Idoc Metadata from Sender System ( The Port Name must match the port name in the idoc header - Usually in format SAP<System ID>. eg. SAPID1 [Optional Step. Not mandatory]
IDX2 : Maintain the Idoc Metadata. This is needed only by XI, and not by other SAP systems. IDX2 is needed because XI needs to construct IDoc-XML from the IDoc. No other SAP system needs to do that.
Also chk the following link providing details of pushing idocs:
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi

Similar Messages

Problem while sending IDOC to File Senario

Hi Experts
 I am having problem while sending the Idoc from SAP R/3 to File
 I have done all the setting in SAP as well in XI but while pushing IDOC
 I am getting error in the transaction sm58 in SAP R/3
" The service for the client 300(My SAP R/3 client) is not present in Integration
Directory"
I can any one explain me what to done on this....all the connections are fine
Waiting for Response
Adv points and thanx
Rakesh

Reason and Prerequisites
You send IDocs from system ABC to the exchange infrastructure (XI) of system XIZ, and error messages are issued in system ABC (Transaction SM58) for the IDOC_INBOUND_ASYNCHRONOUS function module.
This note proposes solutions for the following error messages:
a) No service for system SAPABC client 123 in the integration directory
b) Transaction IDX1: Port SAPABC, client 123, RFC destination
c) ::000
d) NO_EXEC_PERMISSION: "USER" "Business_System"
e) IDoc adapter inbound: Error error ...
Solution
a) Error message: No service for system SAPABC client 123 in the integration directory
Solution:
You send IDocs from system ABC to XI. In the control record of the IDoc, the SNDPOR field contains the value "SAPABC". The client of the sending system is determined by the MANDT field of the control record. The system ID and client are then used to determine a service without party of the type (business-system/business-service):
Business system
Activities in the System Landscape Directory (SLD)(Create technical system):
Create a technical system for system ABC in the SLD, and create the client for this. Do not forget to assign an "ALE logical system" (for example, "ABCCLNT123") to this technical system.
SLD (Business system):
You can now explicitly assign a business system to this client.
For more details, refer to the SLD documentation.
Activities in system ABC (self-registration in the SLD):
Alternatively, you can register the system in the SLD in system ABC with Transaction RZ70. You will find detailed information about the SLD registration of systems on the SAP Service Marketplace for the "Exchange Infrastructure" in the document "Exchange_Installation_Guide.pdf".
In system ABC, you can check your configuration with TransactionSLDCHECK.
Activities in Integration Directory (import business system from SLD):
You will find the business systems under Services Without Party in the Integration Services. In the Service menu, you will find the system identifiers, the client, and the corresponding ALE logical system under "Objects"->"Adapter-specific identifiers".
Use the Import/Update button to copy the data from the SLD, to create business systems, or to update their identifiers.
Business service
Activities in the Integration Builder directory:
You want to create a service without party that is not part of your system infrastructure and is therefore not maintained in the SLD.
In the Integration Builder directory, you will find the "Business-Services" under Services Without Party. In the Service menu, you will find the system identifiers, the client, and the corresponding ALE logical system under "Objects"->"Adapter-specific identifiers".
Activate the change list in Integration Directory.
In system ABC, you can restart the incorrect entry from Transaction SM58 .
b) Error message: Transaction IDX1: Port SAPABC, client 123, RFC destination
Solution:
The Integration Server tries to load the IDoc metadata from the sending system. The IDoc schemas from the Integration Repository cannot be used because they are release-dependent.
The sending system is determined by the value of the "SNDPOR" field from the IDoc control record (for example, "SAPABC").
Activities in the central XI system:
In Transaction IDX1, you can assign an RFC destination to the sending system (for example, "SAPABC"). This must be created beforehand in Transaction SM59.
Note that the IDoc metadata is cross-client data. In Transaction IDX1, only one entry must be maintained for each system. Only the lowest client is used by the runtime for Idoc metadata retrieval with RFC.
Ensure that only SAPABC and not "SAPABC_123" is entered in the port name.
c) Error message: "::000"
Solution:
This error occurs if the central XI system tries to load the IDoc metadata from the sending system by RFC.
There may be several different reasons for the failure of the metadata import, the error is not transferred in full by tRFC completely, and this results in the error message above.
User cannot log onto sending system
User/password/client is not correct or the user is logged due to too many failed logons.
Activities in sender system ABC:
Transaction SM21 contains entries for failed logons.
Activities in the central XI system:
Determine the sending port from the IDoc control record of the IDoc. If the ID of the sending system has the value "ABC", the value of the sending port is "SAPABC". You will find the RFC destination used for the "SAPABC" sending port with the lowest client in Transaction IDX1. In Transaction SM59, you will find the RFC destination containing the maintained logon data .
User does not have the required authorizations
Activities in the sender system ABC:
In Transaction SM21, you will find entries relating to authorization problems and more exact details.
Contact your system administrator and, if necessary, assign the user the required roles in user administration.
IDoctyp/Cimtyp cannot be loaded
Activities in sender system ABC:
In the sender system, you can check your IDoc types in Transaction WE30 (IDoc type editor) Take note not only of the errors, but also of the warnings.
The most common errors are:
- IDoc type or segments not released
- Segments that no longer exist are listed in the IDoc type
- Data elements that do not exist in the DDIC are assigned to fields
in the segment.
Contact your system administrator and correct these errors in the IDoc type.
d) Error message: NO_EXEC_PERMISSION: "User" "Business_System"
Solution:
You created a list of users in the directory who are authorized to use the "Business_System". The user in the error message is not on the list.
Alternatively, the same error is used if you have created a sender agreement with a channel of the IDoc type for the "Business_System" and the interface used. The user in the error message is not contained in the list of all authorized users defined there.
e) Error message: IDoc adapter inbound: Error error
Solution:
You send IDocs to the central XI system, where they are received by the IDoc adapter. The IDocs are converted into IDoc XML, and a corresponding XI message is generated and transferred to the XI Runtime Engine. The Engine tries to read its own business system from the "Exchange Profile". If the Exchange Profile is currently unavailable, the message is not processed and it is returned to the sending system with an error message.
Regard's
Prabhakar.....

Problem while sending idoc over xml http

Hello all,
We have developed a scenario to send the idocs from SAP to Java(Tomcat) web server. Its was working fine. But SOMETIMES the idoc status will be set to 03(Data passede to port OK) on the SAP side, but no data(no xml string) received in the web server. is this depends on the size of the idoc? or due to some JVM settings of webserver??Could someone suggest us a way to identify the problem.
Thanks in advance
Regards,
Vishu.

Asit Purbey,
i have send 2 idocs with different number of segments. idoc with 2 segments is successfully received in the webserver, but the idoc with 100 segments didnt received in the webserver. Then i processed RBDMOIND but both the idocs remain in status 03.. Please help me to figure out the problem......
Regards,
Vishu.

Problem while creating IDOC

Hi Friends..
I have created IDOC through program.
IF Shipment = 'X'.
    perform shipment. -
>Shipment report
    perform shipping. -
>Idoc creation form
    PERFORM ftp2.
    PERFORM move_ftp_entries.
    perform shipment_display.
ELSEIF Receipt = 'X'.
    perform Receipt. -
>Receipt Report
    perform Receiving.----
>Idoc creation form
    PERFORM ftp1.
    PERFORM move_ftp_entries.
    perform receipt_display.
ELSEIF Test = 'X'.
    perform Test.    -
> Test report
    perform testdata.----
> Idoc creation form
    PERFORM ftp.
    PERFORM move_ftp_entries.
    perform test_display.
ENDIF.
if I follow the above condition Idoc created for every report perfectly.But when I come to the following logic no idoc was created...
   perform shipment. -
>Shipment report
    perform shipping. -
>Idoc creation form
    PERFORM ftp2. -
>FTP generation form
    PERFORM move_ftp_entries.
    perform shipment_display.----> Display form
    perform Receipt. -
>Receipt Report
    perform Receiving.----
>Idoc creation form
    PERFORM ftp1.
    PERFORM move_ftp_entries.
    perform receipt_display.
   perform Test.    -
> Test report
    perform testdata.----
> Idoc creation form
    PERFORM ftp.
    PERFORM move_ftp_entries.
    perform test_display.
I want to generate IDOC for all my three reports.
Thanks
Gowrishankar

Hi Gowri,
Tell me one thing. As per your logic you are displaying /generating one report and creating the responding idoc. Correct me if i am wrong. Can you please explain a bit more about your requirement.
Thanks,
Priyabrata

Partner Profile problem while creating IDOC

hi!
I have attached the Partner Profile for the Generated model by assigning the Created Sender, Receiver and message Type and Distributed too.
While checking the attached partner using the T.code WE20 the Message Type is differing from what i have given in the model. its taking SYNCH and the Basic Type as SYNCHRON but the receiver port has been attached correctly.
whats the mistake i have done
Regards
Kv

Hello Gautam,
I am 100% sure about this (anyways FYI i am in ECC5.0). If you debug the BD64 transaction, you will find that it uses some FM (i donot have the SAP system with me so cannot give you the name of the FM) to update table EDP13 directly.
once you generate the partner profile then SYNCH message will automatically be added in partner profile
Then what is the use of adding SYNCH message? In fact the SYNCH message has to be added manually in WE20 & is used by the partner profile generation program to get the port details.
The FMs which SAP uses are: MODEL_ADD_MESSAGE_TYPE_LINK & EDI_AGREE_OUT_MESSTYPE_INSERT. You can refer to the program RBDCUS15.
BR,
Suhas
Edited by: Suhas Saha on Feb 2, 2010 3:46 PM

Problem while updating IDOC MATMAS03.

Hi All,
We are creating outbound Material master IDOC with basic type as MATMAS03.Standard FM MASTERIDOC_CREATE_MATMAS is being used to create IDOCs.Field MEINH of E1MARMM segment is getting populated with ISO standard UOM value .In debugger I can see that ISO value of UOM is geeting passed , but when I display the IDOC in WE05 it doesnt show me ISO value of UOM, it show original value .
For Example, for certain UOM X ISO CODE is Y then should get updated in E1MARMM-MEINH but when see in WE05 it shows me X even though debugger shows updated value as Y.
can somebody please share thought what is the reason behind this?
Thanks
Saurabh

Hi Joshi
What Qualifier you using in E1MARMM MSGFN (Function)
Ramesh

Problem while triggering DTP

When I am triggering the DTP, job is not getting started but it automatically getting cancelled. Any help..

Hi,
There must be some Short Dump, Get into ST22 and analyze your Dump. You may find some inconsistent requests in the system. Locate them and delete them. This should allow you to run DTP smoothly.
Regards,
Suman

Problem in Triggering the Mail to SAP Inbox

Dear Experts,
                 I have a problem for triggering the Mail option to SAP Inbox.
We created a Job assigning the program RSEIDOCA,RSWUWFML2 by creating a variant for those programs. We are scheduling the job, It is showing as
24.11.2010 12:43:46 Job started                                                                     00           516          S
24.11.2010 12:43:46 Step 001 started (program RSEIDOCA, variant ZRSEIDOCA, user ID__ )        00           550          S
24.11.2010 12:43:48 Error situation found by evaluation                                             E0           596          S
24.11.2010 12:43:48 Step 002 started (program RSWUWFML2, variant ZRSWUWFML2, user ID__)      00           550          S
24.11.2010 12:43:49 Job finished                                                                    00           517          S
But while checking in SOST, we are unable to see those mails. eventhough the user is unable to get those mail in SAP INBOX.
I think, is there any authorization problem while triggering the mail for that particular user id.. Please tell me the solution, this is very high requirement for me.
Thanks in Advance.
Regards,
Srini

Hi Chandra,
          Thanks for your reply. Actually i am not workflow consultant, thats why i asking this question. Where to assign the Receipient Type and Recipient Notification.
you give Recipient Type as position and Recipient of Notification must be position of the reciepient,
Regards,
Srini

Error in workflow while triggering.

hi all .
I am facing a problem while triggering my workflow when i am changing the material no. In the SWEL it is showing only standard buisness object and not my object.
kindly help me in this matter.
thanxs in advance.

it is showing only standard buisness object and not my object
What do you mean by the above statement What is your Object
Check whether you have assigned START EVENTS in the workflow basic data or not
If you declare the start event of the workflow then you can see the Name Of the Receiver
Got to SWDD open your workflow definiton and then press CTRL+ F8 and there you can see a Start Events tab under that tab spcify the BO , BONAME and the EVENT CHANGED

Error while triggering Synchrous outbound proxy

Hi,
While triggering synchronous outbound proxy from a abap program,it is throwing an system fault message. the system fault message is "Application Integration system error".
Please help me how to avoid this error.
My code is as below.
TRY.
    CALL METHOD proxy=>execute_synchronous
      EXPORTING
        output     = op_message
      IMPORTING
        input      = ip_message.
    CATCH cx_ai_system_fault into LO_SYS_EXCEPTION.
      CALL METHOD LO_SYS_EXCEPTION->IF_MESSAGE~GET_TEXT
        RECEIVING
          RESULT = TECHNICAL_EXCP_MESSAGE.
    CATCH cx_ai_application_fault .
ENDTRY.

Hi Ashwini,
Quite possible, there is something missing in the partner profile. There are several threads already in SCN with the same problem. Please refer below and see if it is helpful:
http://scn.sap.com/thread/319852
Entry in outbound table not found: Error Status... | SCN
Idoc Error Status "Entry in outbound table not found "
Regards,
Abhishek

I face a problem while making a confirmation on portal.

Hello ,
Can anyone help me I am facing a problem while making confirmation in the portal.
the system pops up an error as mentioned below. Please help
 Folgender Fehlertext wurde im System SRP prozessiert: Speicherungsform der Produkt-ID ist im Customizing noch nicht definiert
 Der Fehler trat auf dem Applikationsserver eccprd-srp_SRP_50 und im Workprozess 3 auf.
 Die Abbruchart war: TH_RES_FREE
 Die ABAP-Aufrufhierarchie war:
Form: READ_SETTINGS of program SAPLCOM_PR_CONVERSION
Function: CONVERSION_EXIT_PRID1_INPUT of program SAPLCOM_PR_CONVERSION
Function: BBP_PDH_PRODUCT_READ_BUFFER of program SAPLBBP_PDH
Form: GET_LOCAL_PRODUCT of program SAPLBBP_ECI
Form: APPLY_OLD_MAPPING of program SAPLBBP_ECI
Function: BBP_PRODUCT_MAP of program SAPLBBP_ECI
Function: B31I_PO_GETDETAIL of program SAPLBBP_BD_DRIVER_31I
Function: META_PO_GETDETAIL of program SAPLBBP_BD_META_BAPIS
Function: BBP_BE_PO_GETHISTORY of program SAPLBBP_PDH_HISTORY
Function: BBP_PDH_SEARCH_PO_SUBLIST of program SAPLBBP_PDH_SEARCH
Best Regards,
Sairam

Hi,
Pls see if the foll notes are useful.
Note 911217 - Copy vendor product number from contract search help to PO
1047769 - No returns for search by Product ID in Monitor Shopping Cart
Note 1023012 - BBPSC: Long product ID triggers short dump
BR,
Disha.
Pls reward points for useful answers.

Error - ATTRIBUTE_IDOC_METADATA - EDI: Error while assigning IDoc number

Hi,
I'm attempting to create a simple interface which converts cutomer data from a flat file and loads it into a SAP enterprise system as an DEBMAS06 IDoc type. I am getting the error message Error - ATTRIBUTE_IDOC_METADATA - EDI: Error while assigning IDoc number in the XI message monitor.
Has anyone come accross this error before and if so, what is the resolution???
Thanks, in advance,
Pete

Hi Peter,
did you fixed it?
How did you?
got the same problem
Kind regards,
Michael

Error: EDI: Error while assigning IDoc number

Hi Everybody,
using XI 3.0 on Linux 64 bit SLES9 with Oracle I got some probleme sending messages from mq series to sap:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30"
xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>EDI: Error while assigning IDoc number</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: EDI: Error while assigning IDoc number</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
What is missing here?
Kind regards,
Michael

Hi Jayakrishnan,
thanks a lot for your answer.
SM59 is working finde. In IDX1 I got the the correct RFC destination entered and a double click works fine also.
The other way around R3 -> XI -> mq series is working fine. Here we are trying mq -> XI -> R3 and it stops sending from XI to R/3.
How to check the IDOC type?
Regards,
Michael

Problem while reading XML file from Aplication server(Al11)

Hi Experts
I am facing a problem while reading XML file from Aplication server using open data set.
OPEN DATASET v_dsn IN BINARY MODE FOR INPUT.
IF sy-subrc <> 0.
EXIT.
ENDIF.
READ DATASET v_dsn INTO v_rec.
WHILE sy-subrc <> 0.
ENDWHILE.
CLOSE DATASET v_dsn.
The XML file contains the details from an IDOC number , the expected output is XML file giving all the segments details in a single page and send the user in lotus note as an attachment, But in the present output after opening the attachment i am getting a single XML file which contains most of the segments ,but in the bottom part it is giving the below error .
- <E1EDT13 SEGMENT="1">
<QUALF>001</QUALF>
<NTANF>20110803</NTANF>
<NTANZ>080000</NTANZ>
<NTEND>20110803<The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.
Invalid at the top level of the document. Error processing resource 'file:///C:/TEMP/notesD52F4D/SHPORD_0080005842.xml'.
/SPAN></NTEND>
<NTENZ>000000</NTENZ>
for all the xml its giving the error in bottom part , but once we open the source code and if we saved in system without changing anything the file giving the xml file without any error in that .
could any one can help to solve this issue .

Hi Oliver
Thanx for your reply.
see the latest output
- <E1EDT13 SEGMENT="1">
<QUALF>003</QUALF>
<NTANF>20110803</NTANF>
<NTANZ>080000</NTANZ>
<NTEND>20110803</NTEND>
<NTENZ>000000</NTENZ>
<ISDD>00000000</ISDD>
<ISDZ>000000</ISDZ>
<IEDD>00000000</IEDD>
<IEDZ>000000</IEDZ>
</E1EDT13>
- <E1EDT13 SEGMENT="1">
<QUALF>001</QUALF>
<NTANF>20110803</NTANF>
<NTANZ>080000</NTANZ>
<NTEND>20110803<The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.
Invalid at the top level of the document. Error processing resource 'file:///C:/TEMP/notesD52F4D/~1922011.xml'.
/SPAN></NTEND>
<NTENZ>000000</NTENZ>
E1EDT13 with QUALF>003 and <E1EDT13 SEGMENT="1">
with <QUALF>001 having almost same segment data . but E1EDT13 with QUALF>003 is populating all segment data
properly ,but E1EDT13 with QUALF>001 is giving in between.

Problem while dowloading the file from Application Server

Dear Experts,
I am facing the Problem while downloading the file from Application server.
We done the automatic function while saving the invoice, this will create an idoc, and this idoc is written in the Application Server.
I am running the Transaction AL11 and select the record, and from menu --> List, i am downloading into TXT format.
But for some segments, the length is long, and so the last 3 to 4 fields values are not appearing in the File. Even though i am unable to view the values in the file before downloading. But i can view in IDOC.
Please help me to solve this issue.
Thanks & Regards,
Srini

but our user will use the Txn. AL11 and they will download from there
Educate the user On a serious note, tell him this is not how data from app server should be downloaded. You can ask him to talk to the basis team to provide him access to the app server folder where the file is being stored.
I can set the Variant and put this in background, But always the file name will be change, Like we use Time stamp in the File name.
You can't automate this process by scheduling in BG mode. This is because the in BG mode you can't dwld the file to presentation server.
Hope i'm clear.
BR,
Suhas

Problem while triggering IDoc

Similar Messages

Maybe you are looking for