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>

Similar Messages

"An IdocException occurred" while posting Idocs from SAP ECC to SAP PI AEX

Hi all,
While sending Idocs from SAP ECC to SAP PI 7.4 AEX, we are experiencing this issue at SAP ECC-SM58
Only a particular Idoc type is having this issue.
Below are the checks done before posting this query:
1. Pushed other Idocs from the SAP ECC to PI and all were getting exchanged successfully.
2. Reloaded the meta data in PI for the particular Idoc type in issue.
3. Checked the RFC destinations in SAP ECC, RFC connection test is also working fine.
4. Unicode option enabled in the SAP ECC RFC destination pointing to PI-AEX
5. Restarted the inboundRA service in PI AEX.
Is there anything still missing. What could be root cause of this issue.
If anyone has encountered it before, pleases share the resolution.
Thank you
Younus

Hi Amit,
Thanks for the reply. Log viewer doesn't provide much help on the error.
The error desc says
"JRA]serverExceptionOccurred. Server XI_IDOC_DEFAULT_SID, Managed_Application_Thread_58, connectionId=5-ip address|sapgw20|XI_IDOC_DEFAULT_SID, Exception: com.sap.conn.jco.JCoException: (104) JCO_ERROR_SYSTEM_FAILURE: An IDocException occurred"
regards,
Younus

Help Required to post IDOC from R/3 to XI

Hello,
I need help to post IDOC from R/3 to XI
My XI System --- E11 on client 001
My R/3 System -- IXS on client 812
In R/3
1. I use Tx SM59 to make RFC Dest --- E11CLNT001 (Client will be 001 Pointing to my XI System )
2. I use TX WE21 to make Port -- A00020 which is using above RFC Dest
3. I use TX WE20 to make Partner Profile -- RECE ( IDOC Outbound Parameter- MATMAS which is using above Port)
In XI
1. I use TX SM59 to make RFC Dest --- E11812 (Client will be 812 Pointing to my R/3 System )
2. I use TX IDX1 to make Port --- SAPB6M (Client will be 812 and RFC Dest -- E11812 )
3. I use TX WE20 to make Partner Profile -- B6MTEST ( IDOC Inboubnd Parameter- MATMAS )
While Posting data from R/3
Recipient Port --- A00020
Recipient Partner No -- RECE
Recipient Partner Type --- LS
Sender Port --- SAPB6M
Sender Partner Number -- B6MTEST
Sender Partner Type --- LS
I am getting error " Could not post IDOC to R/3".
Please let me know where are my setting are incorrect
Regards

In R/3
1. I use Tx SM59 to make RFC Dest --- E11CLNT001 (Client will be 001 Pointing to my XI System )
2. I use TX WE21 to make Port -- A00020 which is using above RFC Dest ( THIS PORT NAME SHOULD BE IN THE FORMAT SAPSID, A00020 (is it you SAPSID, else it will throw error)
3. I use TX WE20 to make Partner Profile -- RECE ( IDOC Outbound Parameter- MATMAS which is using above Port)
In XI
1. I use TX SM59 to make RFC Dest --- E11812 (Client will be 812 Pointing to my R/3 System )
2. I use TX IDX1 to make Port --- SAPB6M (Client will be 812 and RFC Dest -- E11812 ) ( THIS PORT NAME SHOULD BE IN THE FORMAT SAPSID, A00020 (is it you SAPSID, else it will throw error)
3. I use TX WE20 to make Partner Profile -- B6MTEST ( IDOC Inboubnd Parameter- MATMAS ) ( Not require in SAP XI)
chenage the PORT NAME IN R/3 it should work.

How to post idoc from r/3 to xi

hi experts i have one doubt abt posting idoc from r/3 to xi
how to post
for vendor master idoc
for sales order idoc
for purchase order idoc
for delivery idoc
is there any inbuilt posting prgms r there or we have to write the prms.
please clear me
regards
babu

to add more...
Befor posting IDOCS into XI..we need to do ALE SETTINGS...as fallows..
ALE settings.
SAP XI1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name.
and coming to the posting, u can go with WE19

Exit to populate Estimated Price (EKPO-SCHPR) while posting PO from ME21N

Hi All,
While posting PO from ME21N, I need to populate EKPO-SCHPR based on condition records. Can any one please provide me some exit or BADI.
Thanks
Subhankar

Not got the answer. I am closing the thread..

Two idocs are created for one output message type

hi all,
we are communicating our sap idocs to external system using ALE.It is working smoothly.
Our problem raises here,
.idocs are creating at the time of output type attachment for purchase orders.But rarely,two idocs are creating for one message type.It means two idocs are created for same Purchase order.It makes complications for the external system.
anyone can help me pls?
thnks in advance..........

thanks jurgen for ur reply,
jurgen, the second idoc is not an "ORDCHG",It is the replica of first idoc.This one has also "ORDERS" message type.The only difference between these idocs are the time.It means the difference between the time field segments of these idocs have only three(3)seconds difference.We think that its from the system error.If it is not from the system error pls give me the explanation.
thanks in advance.......

Combine IDoc and RFC Respone in one Message Type

Hello,
I need to have the possibility to store the data of one IDoc and one RFC Response in one Message Type.
The structure should be something like this:
IDoc_AND_RFC_RESPONSE (root)
--item (0..onbounded)
ID (Attribute, type xsd:string)
IDOC (Elemtent, type IDOC <--unfortunately not possible in data type definition)
RFC_Response (Element, type RFC_Response <--unfortunately not possible in data type definition)
The goal is to merge 2 messages (idoc data and the data of a rfc response) into 1 message with logical connected items.
e.g.
IDOC (message 1)
--ID 01
IDOC_DATA_01
--ID 02
IDOC_DATA_02
RFC_Response (message 2)
--ID 01
RFC_DATA_0101
RFC_DATA_0102
--ID 02
RFC_DATA_0201
I need this data to be transformed into:
IDoc_AND_RFC_RESPONSE
--item
ID 01
IDOC
IDOC_DATA_01
RFC_RESPONSE
RFC_DATA_0101
RFC_DATA_0102
--item
ID 02
IDOC
IDOC_DATA_02
RFC_RESPONSE
RFC_DATA_0201
The problem ist NOT how to do the mapping, BUT how to define the data type of the target message.
The IDoc and the RFC have a very complex structure so manually building the structure is not possible.
Thanks for your help.

Hi,
thank you for your hints.
- How can I define one interface with 2 message types? I work with XI 3.0.
- Manually manipulatiing the xsd files is what I wanted to avoid (besides that, there is no possibility to get the rfc as xsd, only wsdl). Besides that, I tried to extract the IDoc xsd and imported it as message type, but there is an error message telling me "Schema to be handled does not contain a definition of type <Data Type Name>", whereas <Data Type Name> is the name I give to the Data Type. I tried the name of the IDoc Type here. Importing the xsd as external definition would work, but that would still not solve the problem as I cannot use the message in my data type definition.
Maybe I should specify the scenario a bit better:
I have an R3 System sending an IDoc.
The Idoc contains multiple items.
The data in the IDoc is NOT sufficient (and due to warranty reasons and company guidelines, it is not possible to add all the needed data to the IDoc).
Therefore, the IDoc is passed to an Business Process, where an RFC is invoked (input are the item IDs of the IDoc).
So afterwar the rfc call, I have all neccessary data per item in 2 messages, the IDoc and the RFC response.
Now I need to merge the data per item into one message.
This one message than is splitted into the several items and every item has to be sent separately. So I need a possibility to unite the IDoc with the rfc response.
Any hint?
Thanks a lot!

Error while posting Idoc for customer invoice.

hi,
I m posting Customer Invoice through LSMW using IDocs.
Basic type is FIDCCP02 and message is FIDCC2.
While posting the Idoc I m getting error as:
'Document or line item does not exist for invoice reference'.
I m not getting the error why it is asking for invoice reference because
in FB01 it is not asking for any reference or anything.
In Idoc all the item level values are coming prorperly.
If anybody worked on such issues then please reply.
-Thanx.
-Umesh

Hi Umesh,
Try posting customer invoice through TCode - F-22. There it may be asking for reference number. Generally we post customer invoice by F-22 not from FB01.
If you are getting error you can add reference field in your LSMW it may be mandatory in F-22.
Ashven

Error while posting IDoc

Hi,
i am getting the following error while posting an IDoc: Program parameters for LS XXXXXXXX 2002 have not been set. Please suggest what can be the possible reason for it and the probable solution.

First ,
check the partner profiles in R3,
i.e. a logical system is defined for XI , particluar Message type is added on inbond side and selected the releavnt messge type and and process code. this is all in WE20.
defining a logical system is in SALE.
then ditribute u r the model in BD 64
once every thing is OK in R3
on PI.
create a RFC destination of type R3 which points to R3 , try remote log-on .
this will be used in receiver chaneel
and check u r receiver chaneel is defined under Business system of R3, and BS refers to same client where partner profiles are defined.
and one of the following should be in place.
check 'apply control record from payload' if ur explictly passing Control record from mapping
otherwise,
check sender service and receiver service in Receiver agreement and select appropriate systems.
Regds,
Suresh

SM 58 error while posting Idoc

Hi
I have installed a Netweaver XI 7.0 recently and have completed postinstallation tasks.
Communication between all XI components (i.e IR, ID and SLD is working.)
I am trying to test an Idoc to File scenario and while posting an Idoc from my R/3 system I am hitting upon this error "No service for system SAPD46, client 800 in Integration Directory".
I have scanned SDN forums and came across note 940313 which talks about the registration of R/3 system on SLD by one of the two methods as below..
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 Transaction SLDCHECK.
      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.
I have performed activities highlighted in BOLD. But still error is same.
My question from XI Gurus is that is there any way to know if the manual step of registering my R/3 system in SLD is sufficient (As the SLD bridge for my R/3 system is not configured and I can not use auto registartion.)
Is there any way to check if the R/3 system is successfully registered.
Thanx
Lovein
Edited by: Lovein Khullar on Sep 17, 2008 11:16 AM

Hi,
I think it is due to basis problem, at ID one of service is not working. Please check below mention link for configuration steps
http://help.sap.com/bp_bpmv130/Documentation/Installation/Configuration_Guide_FP.pdf
Meanwhile check all authorization for IDOC processing, else can't process idoc in XI
For IDOC to FILE scenario follow below steps
1. Define Logical system through BD54 after that assign logical system to client through SCC4 window in R3 & XI systems
2. Define RFC destination through SM59 window in R3 & XI
3. Define Port & partner profile through WE21, WE20 windows
4. Trigger idoc from transaction code or test window through WE19.
5. In XI configure SLD under define Product, Component, Technical & business system, it should be WEB as ABAP type.
6. Import component from SLD to ID window meanwhile import idoc from R3
7. Define target structure according to ur requirement and map accordingly
8. Define ports IDX1 & IDX2 in XI
9. In ID define scenario under import business system and configure steps according to ur requirement. Here IDOC is sender so no need communication channel and sender agreement.
It will work without fail

What authorization required to post idoc from XI via RFC?

Hi all,
I need to post idoc to SAP R/3 system from XI. I have done all the steps correctly. While creating RFC in XI system to connect to the R/3 system, intially I gave my R/3 username and password and tested teh connection. Everything was working fine but when I actually ran the scenario, IDOC was not getting posted in the R/3. But there was no error anywhere.
fianlly after debugging I fould it might be the issue of authorization the the R/3 user i used in the RFC. I then assigned SAP_ALL authorization to my user and posted the iodc again and it started working fine.
Can anyone please tell me what are th exact authorizations/role i need to assign to the r/3 used to use it in RFC and successfully posting the idoc? I dont want to use SAP_ALL authorization in my production environemnt.
Please help.
Regards,
Yash

Hi,
Even i had faced this problem. Whenever I tried to send IDOCs, i used to get an error in SM58, " No authorization to send IDOC of type DEBMDM".
When i got SAP_ALL it worked. However I raised a note with SAP asking for an alternative and this is the reply gave me.
You can get good information on this topic in your online help files.
The following is taken from the document "General Security Measures
(ALE)":
Use the transaction SALE to maintain the ALE configuration, to include setting up the distribution model and setting up ALE user authorizations and profiles. Note the following:
- Be restrictive when assigning the ALE authorizations.
The authorization profile B_ALE_ALL contains the following
authorization objects that are needed for ALE:
Authorizations for ALE
Authorization Description
B_ALE_CGRP ALE Customizing Distribution: Group Activities
B_ALE_LSYS ALE/EDI: Maintaining logical systems
B_ALE_MAST ALE/EDI: Distributing master data
B_ALE_MODL ALE/EDI: Maintaining customer distribution model
B_ALE_RECV ALE/EDI: Receiving IDocs via RFC
B_ALE_REDU ALE/EDI: Generating messages (ex. reduction)
S_PROGRAM ABAP: Program run checks
S_TABU_DIS Table Maintenance (using standard tools such as SM30)
Protect external users and passwords.
For example, for a non-SAP system to send IDocs to a SAP System using transactional RFC, it must also send a SAP user ID and password.
In most cases, the user and password are stored outside of the SAP System. Make sure that this information is not accessible to external systems or programs. (How you can do this is dependent on the system that you have; therefore, you need to refer to the documentation for the system where the information is stored.)
However, I feel assigining the profile S_IDOC_ALL should also be enough. Just try and see.
Regards,
Merrilly

Dump while testing Idoc from WE19-OBJECTS_OBJREF_NOT_ASSIGNED

Hi Experts,
I am trying to Post inbound PO idoc from we19 tcode.
MessageType:PORDCR1
Idoctype:PORDCR102
FM:BAPI_IDOC_INPUT1
while testing this Idoc it is going dump.
Runtime Errors     :    OBJECTS_OBJREF_NOT_ASSIGNED
Short text            :    Access via 'NULL' object reference not possible.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_REF_IS_INITIAL', was not
     caught in
    procedure "PROCESS_COMPONENTS" "(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:
    You attempted to use a 'NULL' object reference (points to 'nothing')
    access a component (variable: "L_ITEM").
    An object reference must point to an object (an instance of a class)
    before it can be used to access components.
    Either the reference was never set or it was set to 'NULL' using the
    CLEAR statement.
Could you plz suggest how to resolve this issue.
regards,
Bhuvan.

Hi,
Please implement the OSS Note 1409498 (Relavent to your problem).
I am sure it will resolve your issue.
If not solving your than You can serch for relavent SAP note on SAP serivce market place.
Regards,
Lokesh.
Edited by: Lokesh Tarey on Apr 15, 2010 2:31 PM
Edited by: Lokesh Tarey on Apr 15, 2010 2:33 PM

Error while posting data from SCM to XI

Dear Expertise,
I got a requirement where I need to post data from SCM to XI server. From SCM
side it is an ABAP proxy. When I tested the scenario and checked in the MONI of
SCM I got an error. But SCM is correctly configured pointing to XI under Tcode
SM59 (SM59 --> Connection Type H (HTTP Connection to ABAP System) -->with
correct user credentials and PIPE line URL of XI server).
Please let me know is this the correct settings for ABAP proxy for connecting
from SCM system to XI system.
Error Dump in SXMB_MONI:
<?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>XIServer</SAP:Category>
<SAP:Code area="INTERNAL">HTTP_RESP_STATUS_CODE_NOT_OK</SAP:Code>
<SAP:P1>401</SAP:P1>
<SAP:P2>Unauthorized</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText><!DOCTYPE html PUBLIC"-//W3C//DTD HTML 4.01Transitional//EN">
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>HTTP response contains status code 401 with the description Unauthorized Authorization error while sending by HTTP (error code: 401, error text: Unauthorized)</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks in Advance,
Gujjeti

HI
Check these
For Error: HTTP_RESP_STATUS_CODE_NOT_OK 401 Unauthorized
Description: The request requires user authentication
Possible Tips:
Check XIAPPLUSER is having this Role -SAP_XI_APPL_SERV_USER
If the error is in XI Adapter, then your port entry should J2EE port 5<System no>
If the error is in Adapter Engine
then have a look into SAP note- 821026, Delete the Adapter Engine cache in transaction SXI_CACHE Goto --> Cache.
May be wrong password for user XIISUSER
May be wrong password for user XIAFUSER
for this Check the Exchange Profile and transaction SU01, try to reset the password -Restart the J2EE Engine to activate changes in the Exchange Profile After doing this, you can restart the message

Error while pushing idocs from SAP to XI

Dear All,
For doing ALE configurations for pushing IDOC's from SAP to XI, I am following the following blog posted on SDN:
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
I am able to create the model view distribution successfully but when I am clicking on EDIT --> MODEL VIEW --> DISTRIBUTE (which is one of the steps mentioned in the blog), I am getting an error tht
Target system XIDEV Communication error occurred
User is locked. Please notify the person responsible
please tell me what is the error ie which user is locked and how should i proceed now.
Waiting for your reply.
Warm regards,
N.Jain

hi krishnamoorthy,
i hve created one RFC in my R/3 system which is pointing to Xi-DEV. So, in the RFC I have used my XI user id & password for loging and the RFC is wrking fine when I am testing tht. I have used my id "XISUPER" in that RFC and it is not locked in XI-DEV. I have not used user id "XI_APPLUSER" anywhere.
Please suggest.
Warm Regards,
N.Jain

Getting Error in SM58 and IDX2 while using IDOC from

Dear All,
Getting error when trying to send FIDCCP02 Idoc from ECC to PI system.
"Basic Type 'FIDCCP02' is unknown"
Getting the same error while trying to import metadata using IDX2 from PI side.
All connections and distribution model are created.
Please help
Regards

hey,
I checked all config again but getting error while checking ocnsistency in BDM5 on ECC system(E1Q).
It is failing when the messge type FIDCC1 reaches PI QA (X1Q) system and the error states
Message type FIDCC1 is not defined
Please check last line of below message:
E1QCLNT001     Checks in own system E1QCLNT001
     Message type     @08\QCheck OK@     Message type FIDCC1 is defined
     Segment filtering     @08\QCheck OK@     No segment filtering
     Conversions     @08\QCheck OK@     No conversion
     Partner profile     @08\QCheck OK@     Partner profile has been created
                                @08\QCheck OK@     .....Port PI_QA
          @08\QCheck OK@     .....Port PI_QA
          @08\QCheck OK@     .....Packet size 0001
          @08\QCheck OK@     .....Basis type FIDCCP02
          @08\QCheck OK@     .....enhancement
     Port     @08\QCheck OK@     Port PI_QA : To PI Quality System
          @08\QCheck OK@     .....Port type: Transactional RFC
          @08\QCheck OK@     .....port version 3: IDoc record types from Version 4.0 onwards
          @08\QCheck OK@     .....Logical address (destination) X1QCLNT001
     Logical address (destination)     @08\QCheck OK@     Logical address (destination) X1QCLNT001 is defined
X1QCLNT001     Checks in partner system X1QCLNT001
     Check of own logical system     @08\QCheck OK@     Own logical system is X1QCLNT001
          @08\QCheck OK@     Logical system is the same as the target address
                   Message Type     *@0A\QCheck resulted in error@*     Message type FIDCC1 is not defined
When I am clicking on error it is taking to WE81 on PI side.
So do I need to add this message type in PI system as it is present in ECC side?
Thanks
Edited by: Chanakya Sharma on Dec 10, 2010 12:10 PM

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

Similar Messages

Maybe you are looking for