Idoc not posted in sap system

Hi All,
i have configured the file to idoc and idoc to idoc scenario.
in sxmb_moni,the inbound idoc is fetching one port and the out bound idoc is fetching the default port,how can i config the port that is idoc comming from sap system.
in interface mapping i am not able to assign the operational mapping that is created in IR, it is fetch the default name space of the idoc ,which is not to our operational mapping created in IR.
Regards,
reddy

in sxmb_moni,the inbound idoc is fetching one port and the out bound idoc is fetching the default port,how can i config the
port that is idoc comming from sap system.
In Message Mapping enable the EDI_DC40 segment and then give value to the SNDPOR/ RCVPOR ....once done in receiver IDOC channel check the Apply Control Record from Payload....Michal has written a blog on EDI_DC40 segment check it once.
in interface mapping i am not able to assign the operational mapping that is created in IR, it is fetch the default name space
of the idoc ,which is not to our operational mapping created in IR.
This behavior is correct....IDOC will refer to its own namespace and not to the one created in IR.....and this should not cause any issue while assigning mapping in Interface Determination....if it is causing an error then you have not selected the objects properly.
Regards,
Abhishek.

Similar Messages

MATMAS01 IDOC not reaching to SAP XI via report program.

Dear Experts,
WE are facing small challenge.
I searched on SDN on scenarios: IDOC not reaching to SAP XI. But could not find exact solution t oour scenario.
Problem:
MATMAS01 IDOC is not reaching to SAP XI via report program and is in status of 03 on SAP system. And there are not entries under SM58.
Under SAP XI system IDOC entry is not reflecting under IDX5 transaction, I tried to delete meta data of MATMAS01 thru IDX1 and uploaded again but still IDOC is not reaching to SAP XI.
The strange is that MATMS01 IDOC is reaching to XI via WE19 test tool. So PORT and RFC destination settings betweeen R3 and XI is also correct.
What could be the wrong ?
Thanks
Divyesh

When sending Idoc from R/3,
Settings at R/3
create one port at WE21,
Create Partner Profile for Outbound Message type in WE20.
settings at XI
Create one port in IDX1
Import Matadata in IDX2.
Create complete scenario in ESR for Idoc sender, also import IDoc in Imported Objects.
Check these settings & send test idoc using WE19.

Local currency is not posted into SAP

Hi,
I am using the program 'RFBIBL00' for postings into SAP from leagacy file after validations. For this I am facing one issue.
CURRENCY - USD
AMOUNT - 12345.12 (example)
for this postings , the amount in local currency is not posting into SAP and the amount in local currency is recalculated by SAP at the exchange of system.
Please help me for this how to post local currency into SAP.
regards
SVR

Hi,
Which field in BBSEG structure you are passing the amount field to? Did you use BBSEG-DMBTR?
Regds,
Rudra

How we can import an IDOC structure from one SAP system to another w/o ALE

Hi Gurus,
How we can import an IDOC structure from one SAP system to another? we're not able to use ALE tech, these two sap systems are isolated.
Any response will be awarded!
Thanks a lot.
Samson

hi,
1.One is by change pointer concept i.e by executing the RBDMIDOC.We can generate the idoc and automatically to the inbound System.
2.By executable program also like bd10 and bd11.
Regards,
SHIVA(reward if helpful).

SWCV still contains IDocs/RFCs from an SAP system

Hi
I have imported Idoc to a SWCV. Now am trying to create one more namespace under it. When I try to create another namespace, it automatically selects the check button Import of Idoc and RFC interfaces from SAP systems permitted. If I select not permitted and try to create namespace it gives me this message
Unable to save object XYZ , 1.0 of ABC
Indicator cannot be undone since the software component version still contains IDocs/RFCs from an SAP system
Delete the objects first.
Is it possible for me to create another namespace under a SWCV, to which I have already imported Idoc, by selecting the option " Not permitted ". I want to create another namespace and I don't want to select that option as I have already imported Idoc

Hi,
You no need to touch that check box, you can still create the namespace under software component.
Just double click lick on software component, goto edit mode and click on + symbol to insert namespace and save then activate.
Note:- As you have already imported the RFC and IDoc under your software component(not namspace as you mentioned), you keep that check box import of RFC and IDocs permitted. Dont try to uncheck that.
thanks,
madhu

How do i check the list of invoices which are not posted into sap.

Hi All,
Iam displaying(ALV) the list of invoices and epayments for both PO & non PO transactons which are being processed in workflow but not posted in sap.
(Non po transaction is th eone with out reference of a PO)
How to check and list out the invoices that are not posted in sap. where does this get stored.
please help.
Thanks
jyothi.

Hello Jyothi,
U can give try with EKBE table for getting invoices for PO. In this table there is a field vgabe which has various status. U can try that. Now for Non PO, u would be directly creating invoice doucment using FB60(i guess) which would create an entry directly into BKPF/BSEG. U can scan BKPF for the date range company code document type KR which vendor invoice.

IDoc adapter with Non SAP systems

SAP XI 3.0 help says:
You can use the IDoc adapter to connect SAP systems (as of release 3.1) and non-SAP systems with the Integration Server using native IDoc structures
What does this mean?
-Naveen.

Hi Naveen,
Let me give a use-case in one of our projects ....we have 2 middlewares in our landscape...webmethods and XI...and in one particular instance there was a need to send an FI IDoc from webmethods to XI and forward it to R/3....
In this case, the webmethods was treated like any other sap system for receiving IDoc into XI(with settings in IDX1)...
Hope this might clarify a little bit...
Thanks,
Renjith

How we can import an IDOC structure from one SAP system to another

Hi Gurus,
How we can import an IDOC structure from one SAP system to another? If we're using ALE, how can we do that? Please can someone give me the process and necessary t codes.
Any response will be awarded!
Thanks a lot.
Samson

hi!
Define the logical system names in both the systems.
Logical system names :SAP001
SAP002
SAP001 FOR 001 CLIENT
SAP002 FOR 002 CLIENT
These two logical system definitions should be present in both the systems.
Assign the logical systems to the client. (in both the systems)
Assign SAP001 to 001 CLIENT
Assign SAP002 to 002 CLIENT
you can See these in transaction SALE.
After this define the rfc DESTINATION IN sm59. (in both the systems)
In 001 client create the RFC destination name SAP002
In the tab log on security, give the user name and password and client of the 002 client and save it.
Similarly do the reverse in the 002 Client.
In 001 client create the port.(Transaction WE21)
Specify the RFC destination name as SAP002.
Now you can define the ports, (both the systems)
Create the partner profile for partner(ie gve logical system name of partner) , so give as SAP002.
partner profile in both the systems.
Now create the distribution model in BD64 and goto edit>model view>distribute.
The same model view will be visible n distributed to the partner system also..which in this case is sap002.
U may trigger the idoc from we19 and chk its status in we05.
Please let me know if you need further info on this.

How to send IDocs from a non-SAP system to a SAP system

Hi everyone i am new to SAP R/3 System.
Currently i am required to send IDocs from a non-SAP system to a SAP R/3 System.
There is a guide on Cost-Effective and Quick Communication between SAP and 3rd Party Systems using IDOC HTTP XML Interface. But its from a SAP system to a non-SAP system and i am able to do that.
Is there any step by step guide where they teaches you how to send IDocs from a non-SAP system to SAP system via similar method?
Thank You!

Hi,
I hope this link may help you......
http://publib.boulder.ibm.com/infocenter/iisinfsv/v8r1/index.jsp?topic=/com.ibm.swg.im.iis.ds.entpak.sapr3.use.doc/topics/c_pack_r3_Introduction.html

Post IDOC internally in same SAP system

Hi All,
I used IDOC to send data from SAP to XI in my previous assignments.
Now i have a requirement wherein i need to use an idoc to post data within SAP i.e in the same system. This is because incase the idoc fails the end user can correct the data and re-process the idoc and post it again. though its not so recommended its agreeded upon in the design phase.
now my doubt is in MASTER_IDOC_DISTRIBUTE should i set the control record so that it points to the same system which means the port i create which has an RFC which will point to the same system from where the report is run. is this the correct way.
thank you.
Regards,
Jayaram

Hi,
You can test in the same system
But make sure that the using partner profile(WE21) is having Collect IDOC's option so that the IDOC are not transferred to the target system.
Hope this helps
Regards
Shiva

Inbound idoc failing to reach SAP system.

Hi All,
We are upgrading our SAP system from release 700 to 730. Post upgrade we have identified that idocs which are supposed to reach SAP as inbound are failing in Biz Talk with below message.
Error details: Microsoft.ServiceModel.Channels.Common.XmlReaderParsingException: The segment name is not valid for the IDOCTYP, Release, or CIMTYP. Segment name: E2EDT37003GRP IDOCTYP: SHPMNT03 Release: 700 CIMTYP: . Ensure that your message xml validates against the operation schema.
This happening for only one inbound idoc which is using SHPMNT03 idoc.Whereas other inbound idoc which is using /AFS/ORDERS05 idoc is reaching SAP without any issues. I am bit confused why this is happening for idoc SHPMNT03.
Please let me know your thoughts.
Thanks,
Gowrinath.

Hi Ramya,
Thanks for your response.
In Biz Talk schema is designed for 700 release idoc.Whereas our system is upgraded to 731 release.
Hotfix is for Biz Talk. Can't we implement any solution in SAP side.
Thanks,
Gowrinath.

Idoc not appearing in Xi system

Hi experts,
I have developed a idoc to file scnario but the idoc trgerred in the ECC system i snot comming to XI. I have done all the setting IDX1 and IDX2 and partner profile settings in ECC. the idoc status is 03 in ECC which says the idoc is sent to port successfully, but it is not appearing in SXMB_MONI in XI. It used to work earlier. Is there any batch job or peogram does this transfer. what do i check?/
thanks
sankar

Hi,
Add the Logical System of SAP R/3 in Integration Directory as shown in the Blog and check Now
The specified item was not found.
And also check these Disscussions
No service for system in Integration Directory
No Service for System XYZ,Client 300 in Integartion Directory
Regards
Seshagiri
Edited by: N V Seshagiri on Aug 7, 2008 8:16 AM

Idoc not visible in Business system

Hello Experts,
I am trying to configure a scenario where in I am trying to use the IDoc ZCNOSE_PRICAT.PRICAT02.ZPRICAT1.
However, this IDoc is not reflected in the business system in which I am using.
I have already released the extension from the backend SAP system.
Can you please suggest what I am missing such that the extension is visible in the Business system.

Hi,
You imported the idoc structure into the ESR, under a specific SWCV.
Make sure that SWCV is linked to your Business System in the SLD.
Kind regards,
Dimitri

Data elements for IDoc Segments to non-SAP system

Hi,
I need to create IDocs for transferring data to non-SAP system. When I create segmet fields should I create new data elements for all the fields with attributes specific to receiving system? Because there are many fields where the field attributes of SAP system do not match the corresponding fields of receiving non-SAP system.
Thanks in advance!!
Regards,
Sriram

Hi Sriram,
When I create segmet fields should I create new data elements for all the fields with attributes specific to receiving system
Is it custom segments .
Regards,
Madhu.

** File to IDoc scenario - IDoc not created in target system

Hi friends,
We are doing File to IDoc scenario. We made required setting in both application as well as XI system. While test the scenario, the file is picked up and successfully processed in SXMB_MONI, but the inbound IDoc is not created in target system. What could be the problem?
We are using DEBMAS message type DEBMAS06 IDoc type. We checked the following.
1) SM59 - Connections are OK both application and XI system
2) IDX1 - In XI System, we have assigned SAP<R/3> port.
3) IDX2 - IDoc is imported.
4) In ID - Sender File - Business Service - Adapter-Specific Identifier - Logical System name is given.
5) In application system. - Partner Profile maintained correctly.
6) SM58 - There is no error.
So, what could be the reason ?
Kindly reply, friends,
Thanking you.
Kind Regards,
Jeg P.

Hi,
Check all the steps ..
File to IDOC
Do these configurations in R/3 and in XI...
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.
Thanks,
Satya

Idoc not posted in sap system

Similar Messages

Maybe you are looking for