Question in idoc from madhav

what is the message type?
pls send me good answer imm.

Hi,
The messages exchanged between systems are of various message types. The message type depends on the data contained and the process involved. It determines the technical structure of the message, the IDoc type. For example, the FIDCMT message type is used for journal messages.
The IDoc type indicates the SAP format that is to be used to interpret the data of a business transaction.
Hope this helps.
Regards,
Richa

Similar Messages

Sending IDoc from Non-SAP system to XI

Dear all,
We have a non sap system which needs to send IDoc to XI, Please could you answer my following four questions
1. What should be the values for the following fields in the IDoc control record
e.g. RCVPRN = <logical system name of XI>
SNDPOR
SNDPRT
SNDPRN
RCVPRT
RCVPOR
2. How does XI decide which port(idx1) to be used when it receives an idoc
3. The third party system is a non sap one, so it does not have a client no, so I would assume, I need to use another SAP system as a meta data provider, in that case, how would i tell XI to use that port when it receives IDocs from the non-SAP system ?
4. In what step does XI use the logical system name of the Business system(in SLD)?
Thanks in advance
cheers
danus
Edited by: Chidambaram Danus on Jan 25, 2008 2:21 PM

Hi
there is bit wrong interpretation of the statement
If the sender system is a non-SAP system, the sender service is identified from the logical system name of the sender port.
If the sender system is nonSAP it indicates taht the data is coming to XI from non sap systems such as file, database, webservice etc. to XI and from XI it will pass to sap as IDOC inbound.
For this you need to create the logical system in SAP (receiver) and pass on that value to IDOC header.
You could maintain it in the Business service used for Sender system (nonSAP). here it will be available in the tabs ---> History.
note : IDOC is the concept of data container in SAP, you will not be able to have the IDOCs in non sap systems...
Thanks
Swarup
Edited by: Swarup Sawant on Jan 25, 2008 2:54 PM

How to create Inbound Idoc from XML file-Need help urgently

Hi,
can any one tell how to create inbound Idoc from XML file.
we have xml file in application server Ex. /usr/INT/SMS/PAYTEXT.xml' we want to generate inbound idoc from this file.we are successfully able to generate outbound XML file from outbound Idoc by using the XML port. But not able to generate idoc from XML file by using we19 or we16.
Please let me know the process to trigger inbound Idoc with out using XI and any other components.
Thanks in advance
Dora Reddy

Hi .. Did either of you get a result on this?
My question is the same really .. I am testing with WE19 and it seems SAP cannot accept an XML inbound file as standard.
I see lots of mention of using a Function Module.
Am I correct in saying therefore that ABAP development is required to create a program to run the FM and process the idoc?
Or is there something tht can be done with Standard SAP?
Thanks
Lee

Party-based IDOC from external SAP sender

Hello experts.
I have PI 7.0
I have a scenario where I receive an IDOC from an external SAP system - that has SID=PRD and client=400
I also have an SAP system in my landscape with SID=PRD and client=400.
when I tried to define a service and edit it's adapter specific identifiers - i received the following error:
Check Result for Object EXT_SRV
SAP system ID PRD and client 400 already exist in service | PRD400
I understood that the PI will not be able to identify the sender if an it will receive an IDOC with SNDPRN=PRD400
When trying to figure out a way to overcome this and be able to receive the IDOC I came across the term:
party-based communication. I understood that I should define a party an in it a service for the external SAP system.
can some one please show me a detailed step by step example of such scenario?
All I found was this: [Java IDoc Adapter Partner Conversion |http://help.sap.com/saphelp_nw73/helpdata/en/7b/ebc8b9e34b434d9f3e80ef6776d77a/content.htm] and it is only valid for PI 7.3
Thank you very much.

Hi ,
In idoc communication few fields play a vital role SNDPRN,SNDPRT,RCVPRN,RCVPRT,SNDPOR and RCVPOR in EDI_DC40 segment. These fields actually identify the sender and receiver systems and ports.
Now in your case as I understood that a new sender SAP system is sending the same idoc to PI server along with an existing one. In this case you need to alter SNDPRN value to a new value, when you are sending the idoc. All other values will retain same values for same idoc (basic type and message type). In ID add a new party in object list with the new SNDPRN value.
In the ID scenario create a copy of each entry in interface determination,receiver determination,sender agreement and receiver agreement. In each of the copy add the new sender/receiver party information SNDPRN value.
This should take care of your problem. No need to do any changes in IR as IR will be common for both the senders, what differs will be the ID. PI server will run different instances of the scenario for different SNDPRN value.
Finally one small request, please kindly if possible close down your threads, in case you got proper and correct solutions to your questions. I noted you closed only one of last five threads you have opened. If you close threads after a solution has worked, then forum users become sure that the solution has worked for your case and therefore is correct.
Regards
Anupam

How to push idoc from r/3

how to push idoc from r/3

Hello
We expect you to be able to search the forum to get answers to basic questions such as this.
- This thread will be locked.
- No points will be awarded to any of the replies.
- Your user will be monitored and if this type of questioning continues your account will be closed.
Please familiarise yourself with the forum Rules of Engagement before posting.
Rules of Engagement
https://wiki.sdn.sap.com/wiki/display/HOME/RulesofEngagement
Regards
XI/PI Moderator

Unable top convert the status of idoc from 03 to 12

Hi experts,
I am working on idoc scenario on ECC6.0.I am pushing the idoc from R/3 system to PI7.0.I have done all the prerequisites involved to pushing idoc-----
maintain Rfc destinations,maintain port,partner profile,distribution model....
But when i am pushing the reduced idoc from sender it's showing the status 03.when i am running RBDMOIND in se38 still it is not getting converted into 12.
kindly help me how can I convert the status from 03 to 12.
Thanks in advance.
Regards,
Naresh.K

Hi Naresh
you have to create the service. Create first the technical system and the business system in the SLD. Look for the right "Logical System" (Transation SALE in R3).
In the Integration Builder Directory go to "Environment/Clear SLD Data" and create the service by "Objects/Service without party/Business System/Assign Business System".
Hope this will solve your Querry
Thanks !!
Questions are welcome here!!
Also mark helpful answers by rewarding points 
Regards
Abhishek Agrahari

Some question on IDOC (Control Record/Data Record/Status Record)

Dear all,
I am new in this area, and would like to enquire some question on this topic.
When I view a IDOC via WE02, each of the IDOC record will consist of Control Record/Data Record/Status Record).
Questions:
I notice that the data records consists of many segment (i.e. E1EDK01, etc) which are use to store application data.
1 - My question is do I have to manually create all these segment and do a mapping to my application field one by one (i.e. that is when I want to create a brand new message type from scratch)?
2 - If question no. 1 is Yes, how to do it, what are the transaction code to create it? can you show me the step by step.
3 - I don't have to create the Control record and the status record for my new message type right ? because those field value will automatically pull out from partner profile and system status message, am I correct?
Thanks.
Tuff

Hi Tuff,
As everything in SAP, with IDOCs too there are
1) Standard IDOCs
2) Standard IDOCs(Extending - Enhancement to an IDOC, to accomodate for custom values)
3) Custom IDOCs
And every IDOC has,
Control record - EDIDC Structure - This mostly reflects the partner profile information, along with few more details which are used for IDOC extension, Sequencing etc
Data Records - EDID4 Structure - These records contain the actual business data of the document in concern. So for ORDERS05 it would contain order details, INVOIC02 - Invoice details so on...
Status Records - These records capture the status of an IDOC from the time it is received/sent from your system and a corresponding business document is created/changed. So this will have messages like "IDOC sent to the port OK" etc which are status from the communication layer(ALE) to application specific messages like "Sales Order XXX created" or "Invalid Material" etc.
You would have noticed something called as Process code in the partner profile, this is associated with a FM(or work flow task etc) which has the business logic coded in.
So in case of an Inbound IDOC, the sending system updates the IDOC - Control and Data records, and sends it to the receiving system. On the receiving system the IDOC's control record is validated against the partner profiles set, if an entry is found then using the process code it finds the associated FM which will decode the data from the IDOC data records as per the IDOC type and then use it to post data into SAP (VIA BDC, Batch Input, BAPI etc).
And all this while the Status records are being updated accordingly.
So with the above context will try to answer your questions,
1 - My question is do I have to manually create all these segment and do a mapping to my application field one by one (i.e. that is when I want to create a brand new message type from scratch)?
In case of a custom IDOC, yes you will have to.
In case of a standard IDOC, you wouldn't have you just have set up the necessary configuration (Partner Profile, Process code etc)
In case of a standard IDOC extended to accommodate for some custom values(for which there are no fields in standard IDOC - Let us say you have added some new fields on VA01) - In this case you can still use the standard Process code and Standard FM associated with it, SAP provides several Function exits in these FM's which you can leverage to add your custom logic.
2 - If question no. 1 is Yes, how to do it, what are the transaction code to create it? can you show me the step by step.
There are several documents available on the net and on SDN detailing step by step approach for all the above three cases,
just search for step by step guide for IDOCS - sap.
3 - I don't have to create the Control record and the status record for my new message type right ? because those field value will automatically pull out from partner profile and system status message, am I correct?
Again it depends, in case of using a standard IDOC you wouldn't have to. But in case you have some customizations/enhancements then you might have to.
For Ex: updating the control record accordingly for indicating that you have extended the standard IDOC. Or append custom messages to the status record as per the business logic.
Try out the examples you find on the net and post any specific questions you might have.
Regards,
Chen

Stop generation of Inbound IDOC from Non - SAP

Hi Experts,
I have a requirement to update data base PA0105 for Email. The Email is coming for external system (Non SAP), which contains 1 employee in 1 IDoc. If SAP has valid email and same has been passed for external system to SAP via Inbound IDoc, it should not update PA0105. Hence, I am deleting the IDOC segments in Exit "ZXHALU07", before RBDAPP01 is getting called. As per the requirement its working fine.
Question: Is there any way to stop generating the IDOC. If the email ID were same, then IDoc should not generate in SAP. Please provide your valuable reply. Thanks.
Regards,
Ganesh R K.

Hi All,
Scenario:
Need to Create Inbound IDOC in SAP system and receive it from Non Sap system.
Problem:
IDOC is successfully dispatched from Non Sap system(Sender Side) but, it is not received to SAP system(Receiver Side).
At receiver side(in SAP system) all configuration settings are fine (RFC destination is tested with no errors, partner profile are given with the inbound parameters, function module is successfully tested with no errors, distribution model is created etc).
In receiving system(SAP) no IDOCs are generated in We02 after sending the IDOC from Non Sap side.
Can any one please suggest me the reason for the above mentioned problem?
Thank you,
Swetha.C

Error sending IDoc from ERP to PI 7.4 Java Only (stuck in SM58)

Hi specialists
I'm trying to send an IDoc to our new PI 7.4 Java Only.
Because of some authorization issues I changed the RFC Destination <blabla> on PI (nwa) pointing to the ERP system.
Now the IDoc is stuck in SM58 (tRFC queue) and I get this error message:
The IDoc Destination <blabla> was changed. Refresh the destination instance with
Meldungsnr. SR053
Anyone able to tell me where to do this refresh? I'm new to PI 7.4 Java Only and could not find useful answers on SCN and other internet sources.
Thanks a lot in advance for any hints.
Renaud

Hi Iñaki
Great document btw... didn't stumble uppon this before. Thanks.
I carefully went through it but nothing I tried helped.
The RFC destination (PI -> ERP) is working fine.
The resource adapter (inboundRA) is configured correctly. I can confirm, that the connection test of the RFC-Destination inside ERP (ERP -> PI) is successful.
BUT still: sending an IDoc from ERP to PI fails with this message in SM58:
The IDoc Destination <destinationName> was changed. Refresh the destination instance with
Meldungsnr. SR053
This seems to happen every time after one changes some settings in the destination specified in the inboundRA property "destinationName".
So my question still is: how / where do I refresh this destination instance on a PI 7.4 Java Stack Only??? I mean without having to restart the whole PI instance...
Best regards
Renaud

Configuration steps to Trigger IDOC from R/3 to XI

Hi All,
I have read several forums ,
and i am in confusion to follow which one of them.
Let me describe the process of configuration steps in r/3 and XI in step by step and correct me when i am wrong.
Steps in R/3
1) Goto SALE.
 Basic settings->Logical Systems->Define logical system.
 Create two logical systems(one for XI and the other for R3)
 Basic settings->Logical Systems->Assign logical system to client.
 Assign the R3 logical system to respective client.
 Assign the XI logical system to respective client.
Whether i need to create logical sys name only for r/3 or both for r/3 and XI?
2)Goto SM59.
 Create new RFC destination of type 3(Abap connection).
 Give a suitable name and description.
 Give the Ip address of the XI system.
 Give the system number.
 Give the gateway host name and gateway service (3300 + system number).
 Go to the logon security tab.
 Give the lang, client, username and password.
 Test connection and remote logon.
 Gateway service can be sapgw<sys number> or it should be 3300+sys number?
3)Goto WE21.
 Create a port under transactional RFC.(R3->XI)
 Designate the RFC destination created in prev step.
 Port name should be in the form of SAP+SID of XI or it can be anyting?
4) Goto BD64.
 Click on Create model view.
 Add message type.
 Is it necessary to create a Distribution model and distribute it ?
5) Goto WE20
 Goto WE20.
 Partner type LS.
 Create a partner profile
 Give the outbound or inbound message type based on the direction.
Steps in XI
1) Goto SALE.
 Basic settings->Logical Systems->Define logical system.
 Create one logical systems(only for R3)
 Basic settings->Logical Systems->Assign logical system to client.
 Assign the R3 logical system to respective client.
Whether i need to create once again logical sys name for r/3 ?
2) Goto SM59
 Create new RFC destination of type 3(Abap connection).
 Give a suitable name and description.
 Give the Ip address of the XI system.
 Give the system number.
 Give the gateway host name and gateway service (3300 + system number).
 Go to the logon security tab.
 Give the lang, client, username and password.
 Test connection and remote logon.
 Gateway service can be sapgw<sys number> or it should be 3300+sys number?
3)Goto IDX1.
 Create a port under transactional RFC.(XI->R3)
 Designate the RFC destination created in prev step.
 Port name should be in the form of SAP+SID of R3 or it can be anyting?
Step 4)Goto IDX2
Create a new Meta data.
Give the Idoc type.
Select the created port.
Is it neccessary to create a medata?
Let me know the answers for my questions.
Thanks
Sai

Not sure what you have referred till now but there are some excellent link that will close this for you.
ALE configuration for pushing idocs from SAP to XI -
ALE configuration for pushing idocs from SAP to XI
Configuration steps required for posting idoc's(XI) -
Configuration steps required for posting idoc's(XI)
Wiki: https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&

While Posting IDOC from XI to R/3 Message Type needs to be changed

We are doing mapping IN XI. For one condition we want Message Type to be ORDERS and for one condition we want Message Type to be ORDERSCHG
when posting IDOC from XI to R/3.
Pls revert anybody asap.
Regards

Hi,
>>>>It means I need to create two Interface Mappings for the same message mapping and then I can use the Interface Determination . Am I right.
no, you need two message mapping
and two interface mappings
file - orders.orders05
file - ordrchg.order05
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Error sending IDOC from external Java application to Sap ERP system

Hi Experts!
When I try to send Idoc from Java application to XI an error occurs : no service for system CLNTJAVA, client in Integration Server.
My question is: What value the setSenderPort() is excepting?The Java third party business system's logical name or the ERP business system's logical name where the JCO can be found?I tried both of them, but still have the problem.
Please help. I read all threads about this error, but non of those can help me.
My relevant java sourcecode:
doc.setSenderPort("CLNTJAVA");
The XI documentation says that:In the case of non-SAP senders, the entry in the SNDPOR field is interpreted as a logical system name, and the corresponding business system is searched for in the runtime cache.
Both case(third party business sytem and erp business system) I have configured the ID i think correctly. I made a business systems,I configured the adapter specific identifies,I made the IDX1 port,I made the RFC destination,I polled the IDOC type with IDX2 transaction, I have made full cache refresh,I configured the INTEGRATION_DIRECTORY_HMI rfc destination,but I do not made any communication channels, receiver determinations, receiver agreement.
My configurations if it can help for you.
Hostname:sapsp5
System name: NE2
Clients:
000 ERP
001 Integration Server
SLD configurations:
Third Party Technical system name: Java_sytem
Business System:CLNTJAVA
Logical system name: CLNTJAVA
ID configurations:
Business System:CLNTJAVA
adapter-specific identifiers:logical system:CLNTJAVA, the rest is initial,because I cant change it.
IDX1 port name: CLNTJAVA the client is 001. the rfc destination is client_001.
I think the IDX1 port and the adapter specific identifiers are wrong. is it?
my java source if the sender is the JCO
doc.setSenderPort("INTSERV");
My configurations if the sender is the JCO.
SLD configurations:
Technical system name: NE2
Business System:INTEGRATION_SERVER_NE2
Logical system name: INTSERV
ID configurations:
Business System:INTEGRATION_SERVER_NE2
adapter-specific identifiers:logical system:INTSERV,system NE2,client 001.
IDX1 port name: INTSERV the client is 001. the rfc destination is client_001.
Could this error be an autorization error?I tired to connect to the xi from the Java, with the user PIISUSER extended with PISUPER roles.
Thank very much.

Hi!
My SNDPOR already set to my source business system's logical name if you check my configurations(JAVACLNT), so there is another problem unfortunately. I set SNDPRN to JAVA, but it still does not work.
Check this configuration please(posted here:
No service for system ... in Integration Directory)
doc.setMessageType("ACC_DOCUMENT");
doc.setRecipientPort("SAPSE1"); // get stuck in XI mapping if not set
doc.setRecipientPartnerType("LS");
doc.setRecipientPartnerNumber("SE1CLNT500");
doc.setSenderPort("SAP3MA");
doc.setSenderPartnerType("LS");
doc.setSenderPartnerNumber("TREMACLNT");
doc.setClient("100");
Inside XI configuration integration builder
Business Service: Service: TREMACLNT
Under the menu Service - Adapter specific identifiers
Idoc Adapter Logical system: TAPPMAN (This thing is important when sending idoc XI -> SAP and should match the logical sys in the receiving SAP system)
IDoc Adapter and RFC adapter R/3 Sysytem ID: 3MA
Client: 100
In IDX1 trans
Port: SAP3MA (Note that the 3MA here is matched against the IDoc Adapter and RFC adapter R/3 Sysytem ID: 3MA)
(a not so well documented feature)
Client: 100
RFC Destination: SE1 (A SAP test system from where IDOC def can be imported, rfc dests are setup in SM59)
I guess that your idx1 port name is the same as the SNDPOR value. I think it should be, because the XI is whatching the IDOC traffic in the idoc adapter port, so you should send the IDOC from external system to the adapter port. Is it right?
My idx1 port is the same as my SNDPOR value in Java,but still came the error.

I need help to create idoc from scrach.

i need help to create idoc from scrach.

Swamy Katta,
Please read "[the rules|https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/rulesofEngagement]" before you post any further, and confirm that you have read them?
=> Search first, ask questions later please!
Julius

Read idoc from archive in program

Hi All,
I want to read the idoc from the archive in the program.
Please suggest the possible options.
we can read the idoc present in the R/3 database using the FM idoc_read_completely.
But how to read the same from the archive. I can view the idoc from the t-code we10.
Thanks in Advance.
Ankit Gupta

Thanks buddy.
I will try this in my code. Look like it will solve my problem.
But now I have another question. Should I start new thread or can post in the same thread.
Archive infostructure SAP_IDOC_001 is not active in my system. what is the procedure to do it and also it should link to the existing Archive file also.
Regards,
Ankit

IDoc from FB01

Hi All:
Can someone tell me how to create a IDOC from FB01 posting.
Please.
I am trying to generate an idoc after posting vendor invoice in FB01.
Please advice.
Sri

y do u have to ask the same question in three different threads??
y do u have to ask the same question in three different threads??
y do u have to ask the same question in three different threads??

Question in idoc from madhav

Similar Messages

Maybe you are looking for