on 03-20-2008 7:39 AM
Hi,
i m working on a file to idoc scenario using MATMAS.MATMAS02, once i got the scenario executed with error status 51 , and then even after posting the file to repective directory its not showing in the sxmb_moni or in receiver R/3 system using we05 although file has been picked up from the source directory.
Error status 51 is "Messages have been issued: number 0000000000198012"
Pl help how to rectify the error and find out where the error has again occured and why .
ans will be rewrded
rgds
mojib
Hi,
Check the Idoc sender settings clearly ... follow this steps and if not revert back with the query..
Steps
SAP XI
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 (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.
regards,
Kishore
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
thanks , the issue was in mapping
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi mohammad,
i think theres a problem in configuring the partner profile for receiever system .
check the required message types or basic types are added to the LS systems created in R/3.
Thanks & Regards,
Rama krishna
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Execute RBDMOIND in outbound side status will be change from 03 to 12
Execute RBDMANIN in inbound side status will be change from 51 to 53
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Gabriel ,
Thanks by running the report RBDMANIN atlest i could see the idoc geeting processed but again with error status 51,
THE ERROR is The numeric material number 1010000163 was transferred without leading zeros
Trying to change: 1010000163 ____ ____ ____ __________ ____ __ ___ ___
can u please tell me how to delet the idoc and get rid of it
PL help
rgds
mojib
I assume that the IDOC arrives in the R/3 system and that there is no error on the XI side when you check SXMB_MONI.
Further you have also done the inbound IDOC configuration for the process code etc.
Did you check the payload in SXMB_MONI to see if the IDOC data is correct before it is send to R/3.
If that is all ok, did you reprocess the IDoc with TCODE BD87 as there you can setup breakpoint and debug it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi
Kishore , i have gone thry ur steps and then i received the result also ,
Seshagri , i went thru the blog at one place it asking to chk with in XI and click on Transaction ID , when i clicked in it says nothing was selected ,
Gabriel : There was in error in taking the values , becz material no is auto generated but i took one no ,
i m not able to perform tcode BD87 becz nothing is getting selected , it has to be performed in receiveing r/3 system , isnt it
pl help , i m trouble
mojib
Hi,
Lets see if this works for you.
1. The problem could be that file structure lengths and datatype structure lengths in IR are not same. If both structures are same and still if the file is not getting converted into xml format then the problem could be in File Content Conversion (FCC). FCC parameters might not be configured correctly in sender file communication channel.
2. If there is no message in SXMB_MONI, do the below setting at Tcode SXMB_ADM.
Execute the Integration Engine Configuration
Check if role of business system has been configured to Integration Server or not. If it is not ,then configure it to Integration Server.
Regards
Aashish Sinha
PS : reward points if helpful
Hi,
Check this
Troubleshooting File-to-IDOC Scenario in XI
/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
Regards
Seshagiri
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.