SAP MDM == PI== SAP ECC, IDOC posting

Hi,
We are integrating SAP ECC 6.0 with SAp MDM 7.1 SP04 using PI 7.1 as a interface. Scenario is SAP MDM ==>PI==> SAp ECC. I would be creating record in ECC and will be posted in SAp ECC through PI. We will be creating Basic Data (MARA), Plant level data (MARC), Sales Level data (MVKE), and Valuation level Data (MBEW) in MDM. IDOC used is MATMAS05.
Plant level data (MARC) will activate various views in Material master like Purchasing, Sales plant general data, MRP views and accounting views...right
I donu2019t want to activate MRP view but need plant level data i.e. Plant and profit center to populate in MARC table. Means same Material Type but some Materials donu2019t have MRP view activated and some may have alongwith other plant related views.
I tried creating record without passing MRP related fields but still IDOC failed saying MRP type is mandatory. (Which means it is activating MRP view)
Do we have separate IDOC for MDM integration?? Do I need to enhance IDOC??
Warm regards,
Rc
NOTE - This is possible while manual creation as will as through BAPI.

Hi,
Have you checked MDM71_Material_Content.pdf page no 20.
3.3.2 Business Scenario: MDM710_Outbound.
You also need MDM PI content to install and run this Scenario..
Hope it helps if you go through MDM71_Material_Content.pdf
As you said, I tried creating record without passing MRP related fields but still IDOC failed saying MRP type is mandatory
Try passing any constant through PI Message Mapping to inbound IDOC (Receiving System, ECC)
Thanks and Regards,
Mandeep Saini

Similar Messages

Reg SAP ECC IDOC documentation

Hi Friends
Where we can get SAP ECC IDOC documentation help for especially Functional Consultant.
Thanks In Advance
Regards
SR

Hi Ravi,
Hope this links will fullfill your need.
http://www.sdn.sap.com/irj/sdn/ale
http://www.riyaz.net/blog/beginners-guide-to-ale-and-idocs-a-step-by-step-approach/technology/sap/18/
Thanks
Vinayak

XSD and XML to integrate sap ecc system using PI 7.3

Hi ,
Please tell me
1.how to integrate using PI 7.3 XML and XSD to sap ecc to post cost centre idocs .
2.how to post standard cost centre idocs using PI 7.3 to third party system ,please througn some light on these scenarios

>.how to post standard cost centre idocs using PI 7.3 to third party system ,please througn some light on these scenarios
You first need to talk to third party system about their tecnologies handling. If the sender system ecc sends idoc to PI then PI can convert the idoc to xml file or idoc to webservice or so.
Example idoc to file is one possible option.

"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

No receiver could be determined while doing SAP ECC Integraion with MDM 7

Dear All,
Can you please help me to resolve the following issue.
We are doing SAP ECC Integration with MDM 7.1 by using MDM PI Adapter.
Source side we are processing MATMAS.MATMAS05 IDoc and Receiver side we are using MDM PI Adapter to Connect the MDM System.
I have checked the Configuration by using Test Configuration Wizard, it showing every thing fine there.
Is it because of any network connection issue at the Target system (MDM) side?
Plz check the error message for your reference;
<?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="RCVR_DETERMINATION">NO_RECEIVER_CASE_ASYNC</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>No receiver could be determined</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks
Mahesh

Hi,
From error looks like it is not failing at receiver determination step. if you all configurations are fine, then this could be because of system cache refresh.
Go to Edit mode in your scenario and again save it and activate it. Do a cache refresh and check if it works.
Regards,
Shiv

IDOC types in SAP ECC

Hi Gurus,
1) 3rd party->PI->SAPECC
We have a requirement that the tenant refunds coming from 3rd party system should be sent to SAP ECC system.
To send this messgae to SAP ECC, is there any separate idoc format for this tenant refunds.
Should I use any FICO or any other standard module to post these files to SAP ECC.
2)SAPECC->PI->3rd party
Also is there any IDOC type for the direct debit details and customer payments or should i run the F110 transaction to execute the customer payments and to send the paymnet files to PI.
Coould you please advise.
Thanks,
Jay.

If you have fair understanding about ECC then you can easily identify which IDoc to use or any extension required for existing IDoc.
otherwise better to talk with ABAP/Functional team they will help you.

IORDER01 IDoc is sent without plant code from SAP ECC

Hi MEINT experts,
Does anyone experience before on the service order integration between SAP ERP and SAP ME, somehow the IORDER01 IDoc is sent over with empty plant code embedded in the original document? (where we suppose to see <WERKS> data tag is attached to the IDoc sent over from SAP ECC). This has resulted to the corresponding IDoc is not able to process by MEINT due to empty plant code.
Please advice how to resolve this if you have done that before.

Hi,
Once the issue stems from ERP side of integration process, this question should be either re-posted to ERP-related forum or submitted as a customer ticket against PP-MES component.
Regards,
Sergiy

Using the Open Catalog Interface (OCI) between SAP-ECC 6.0 and SAP-MDM

Hello ASUG Community.
I'm working on an SAP-MDM project where we will configure the OCI interface between SAP-ECC 6.0 and SAP-MDM. The business requirement will be to punch out to SAP-MDM's catalog from SAP-ECC for expensed items (e.g., no material master record exists in SAP-ECC).
The data that will be returned to SAP-ECC will be purchase price info, material group, short text, & our global SAP-MDM item number.
The question I've been trying to design around is "where to store the SAP-MDM item number"?
I've looked into creating a custom filed on EKPO but now feel that a configured text field will be the best solution from an SAP-ECC point of view (less effort on the SAP-ECC side from a development perspective, no need to regenerate the EKPO table, etc.).
The question I'd like to pose to ASUG is.... Does anyone have experience or an opinion to offer using this functionality? It seems that I will have to code in a user exit or BAdi to insure that the SAP-MDM item numbers are returned to the appropriate text field on my POu2019s. Or can this be done using the standard OCI functionality?
I found OSS note 1347656 which references BADI "ME_CATALOG_INTERFACE" but I'm not sure if this right path to go down or if this would be the correct place to code non-conforming OCI mapping requiremetns.
Any insight would be most appreciated.
Thanks. Sincerely,
Rich Wortmann

I would suggest you create a new field for this as you may require thois going forward for reporting as well. Text fields are difficult to report.
Sorry not sure about the BADI to use.

Send / Receive Idoc(XML) in SAP ECC 5.0

Hi Experts,
We are using SAP standard idocs to exchanges master data and Sales data between SAP and non SAP system. currently all the idocs are generated and posted as flat file structure.
There is possiblity to use idoc(XML) and HTTP service instead of standard process without XI?
All info related with this is welcome. is it possible? how?
all suggestion n helpful ans will be rewards with points.
regards: gaurave.

Hi Gaurave,
I have comae accross this type of issue once and hope the below link will give you an idea.
http://msdn2.microsoft.com/en-us/library/cc185479.aspx
thanks,
KIRAN

IDoc via RFC problem between certified app and SAP ECC 5.0 on AS/400

Greetings.
I'm not sure this is the best forum for this question but here it goes:
Ever since 2000, we have our certified application for HR-PDC interface. We never had any problem that would be hard to resolve.
Recently, we had a customer who installed our app to exchange data with SAP ECC 5.0 on an AS/400 machine (first time interfacing with this platform for us).
We already checked all user permissions and every SAP note that mentioned this problem but it still doesn't work: when receiving and IDoc (just any), we get the error IDOCTYPE_READ_COMPLETE:OBJECT_UNKNOWN.
Permissions for user are SAP_ALL and SAP_NEW and the IDocs used are the ones stated in the HR-PDC interface (for example, HRCC1DNPERSON, for instance).
I traced down the problem by examining the .trc files (RFC trace files) and I found where the problem lies: IDOCTYPE_READ_COMPLETE is being passed the IDoc Basic Type HRCC1DNPERSON and it should be HRCC1DNPERSON01. I did the same tracing for another installation (not AS/400 with SAP 4.6) and everything goes fine: IDOCTYPE_READ_COMPLETE is called with correct HRCC1DNPERSON01.
I'm wondering if this could be a problem in SAP 5.0 for AS/400 as we already have other customers running the same version on different platforms and everything just goes fine.
Any clues, anyone?
Thanks and regards,
André Baptista

hi
we have a similary problem with our certified as400 application. Our client has the version 4.6C service pack 51 and patch 2161. Data transfert by RFC is ok but we have problems since the installation of the patch 2252. The RFC function RFCaccept do not run any more : the log
<i>argc    = 2
argv[0] = 'HLSAP45A/HLKA15C'
argv[1] = '-DCP03'
Fri Nov 24 14:21:53 2006   *
<== RfcAccept                           rfc_handle = RFC_HANDLE_NULL
<== RfcLastError
RFC operation/code: RfcAccept
ERROR/EXCEPTION
key     : RFC_IO5
status : CODE=CM_PRODUCT_SPECIFIC_ERROR STATUS=??? DATA=??? ID=???
message : LOCATION    CPIC (TCP/IP) on local host
ERROR       connection to partner broken
TIME        Fri Nov 24 14:21:53 2006
RELEASE     45A
COMPONENT   NI (network interface)
VERSION     31
RC          -6
MODULE      nio4i.c
LINE        891
DETAIL      NiPRea
internal: IO HANDLE=1 DRV=??? LINE=1369 CODE=5
<== RfcClose </i>
Do you have solve your problem ?
thanks

Sender Port Error in SAP ECC for IDoc

Hi,
I am creating scenario IDOC -> XI -> JDBC with Customer Master IDoc.
After sending it with we19 he said "IDoc sent to SAP system or external program".
In we02 and we05 the IDOC it says "Data passed to port OK".
But in SM58, the IDoc ends in error saying
Transaction IDX1: Port SAPIDST100, client 600, RFC destination contains error.
What I identified that the port SAPIDST100 is the sender port in the IDoc being send. However, for PI we do not need to maintain sender port.
Business Systems:
Sender : SAP ECC
Receiver: SAPPID
Kindly provide your inputs.
Thanks
Rahul

Hi Rahul,
thanks for the information that your scenario is working fine.
But i want to clarify some points:
   - If you send out an IDoc from an ECC system, the senderport is filled with SAP+<system-id> by the SAP IDOC API,
     i.e. if your system id is "ABC", the senderport is "SAPABC"
      => your senderport SAPIDST does not match this template, so i assume you entered the value for the senderport
     manually in the idoc test utility WE19
   - if you send out an idoc, only the receiver port must be created in transaction WE21, it is not necessary to create
     the senderport in WE21, this is not necessary and did not solve your problem
- the idoc was send from ECC (application system with application IDoc metadata) to an XI/PI system (basis system
    without application idoc metadata
   The IDoc adapter on the pi system must analyze the IDoc segments and must know the idoc application metadata,
   but this is not known. So the idoc adapter on PI side looks at the senderport to identify the sender.
   In transaction IDX1 an rfc-destination can be configured to point to the sendersystem with that senderport
   With this rfc-destination the IDoc adapter tries to read the idoc aplication metadata from the ECC system and stores it on PI side.
   If there is no rfc-destination configured in transaction IDX1 on PI side you get the error mentioned in your request.
   I assume that in transaction IDX1 somebody configured the correct RFC-Destination.
I hope this clarification helps you to understand the error and the solution.
Kind regards,
Andreas Dahl

IDOC type for interface between SAP ECC and SAP F&R

Hi Experts,
I need SAP standatd IDOC type for interfacing between SAP ECC and SAP F&R [SAP Forecasting and Replenishment] using message type u201CFRE_LOC_SITEu201D.
Please help me in finding the idoc type?
Regards,
Krishan

Hi Denish,
You have 2 ways of loading data from R/3 to APO.
1. R/3 to BW cube to APO-BW cube to APO planning area
or
2. R/3 to APO-BW cube to APO planning area
BW can be a enterprise BW system ( independent) or you can use the BW inbuilt in APO also referred to as APO-BW.
The only difference between the 2 BW systems is APO-BW can not take the load of reporting where as the enterprise BW can.
Unless your company policy requires the enterprie BW system, I suggest using 2nd way.
You can load the data from R/3 to APO-BW cube using extractors either generic or standard depending on your data. You need to have a RFC connection setup between APO-BW and R/3. ( This is not CIF).
When you load the data into the APO-BW cube, you just have to load the data from the cube to APO planning area using the transaction /sapapo/tscube.
Refer to [DP Data Mart|http://help.sap.com/saphelp_scm50/helpdata/en/13/5ada58309111d398250000e8a49608/frameset.htm] for more information about the data transfer between APO-BW and APO.

SAP ECC Interface w/ IDOC-XML using TCP/IP, HTTP, or FTP to 3rd-Party Syst.

I am trying to understand if the following interface options can occur (without the use of SAP PI or any other middleware):
Option 1A: Can I process an SAP ECC outbound IDoc in XML using TCP/IP to a non-SAP 3rd party system? Can you please explain the reason for why I can or can NOT do this. If possible, please provide supporting documentation on how-to do this?
Option 1B: Can I process an SAP ECC inbound XML-IDOC from a non-SAP calling system that used TCP/IP? Can you please explain the reason for why I can or can NOT do this. If possible, please provide supporting documentation on how-to do this?
Option 2A: Can I process an SAP ECC outbound IDOC in XML using HTTP to a non-SAP 3rd-party system? Can you please explain the reason for why I can or can NOT do this. If possible, please provide supporting documentation on how-to do this?
Option 2B: Can I process an SAP ECC inbound XML-IDOC from a non-SAP calling system that used HTTP? Can you please explain the reason for why I can or can NOT do this. If possible, please provide supporting documentation on how-to do this?
Option 3A: Can I process an SAP ECC outbound IDOC in XML using FTP to a non-SAP 3rd-party system? Can you please explain the reason for why I can or can NOT do this. If possible, please provide supporting documentation on how-to do this?
Option 3B: Can I process an SAP ECC inbound XML-IDOC from a non-SAP calling system that used FTP? Can you please explain the reason for why I can or can NOT do this. If possible, please provide supporting documentation on how-to do this?

Hello Kirk ,
The answers for your question are:
Option 1A: Yes you can .you can use TCP/IP but you must have a middleware component for that such as BC/JCO .
Please see the link : [http://help.sap.com/saphelp_nw04/helpdata/EN/09/c88442a07b0e53e10000000a155106/frameset.htm]
Option 1B: See the link above.
Option 2A: You can use ABAP code :
[http://help.sap.com/saphelp_nw04/helpdata/EN/e5/4d3514c11411d4ad310000e83539c3/frameset.htm]
Option 2B: [http://help.sap.com/saphelp_nw04/helpdata/EN/90/4f3c2ec3c511d6b2b400508b6b8a93/frameset.htm]
Option 3A: Only with ABAP code :[Reg: FTP Connection;
Option 3B: See the link of Option 3A.
Good Luck,
Boaz
Edited by: Boaz Ornan on Feb 21, 2010 4:33 PM

Sending IDOC from SAP ECC to SAP MII

Hello,
Issue while configuring.
I have configured the RFC Destination in the Netweaver message listener and when i check the connection in SM59 I got error as timeout during allocate of registered program and I have attached the screenshot of the error page.
I would request a reply asap.
Thanks,
Praveen

Hi Praveen,
First, I would suggest that you identify what version, and SP, of MII and ECC. Also the NW version and SP if applicable.
Second, use this custom Google search and terms MII, IDoc Listener, and perhaps SM59. There are many discussions on IDoc Listeners going back a number of years. Many of the issues with IDoc Listeners have not changed in most of that time, so look at the older ones as well. I presume that you found and are using my How to Send an IDoc from SAP ECC to the SAP MII IDoc Listener (MII 12.1 to ECC 6.0) to set up your Listener? If not, you should review your configuration and setup procedure against it.
I have not looked at MII 14.0 or 15.0, but understand that the configuration of Listeners really has not changed since MII 12.1. So the document is still applicable.
Third, roughly 90% of the problems experienced with IDoc Listeners involve multiple uses of the self registering ProgID. Deleting it in one place, generally does not work. Use it in one place only. Create a new ProgID for each separate Listener (either type) on each separate MII instance for each ECC instance. Save yourself a lot of headaches. Never, ever reuse ProgIDs!!!
Fourth, most of the other issues involve a PI/XI system in the middle. Those are a bit more complicated since they rely on getting the connection configuration set up properly in PI. Since I am not that familiar with PI systems (most times it is not involved with the Listeners), I generally have to get other experts involved. Sometimes a CSS ticket is required.
Regards, Mike
SAP P&I Technology RIG

Receive XML file from CIDX adapter and Post to SAP as IDoc using XI

I have scenario where we will receive the xml file from CIDX adapter. I need to take the xml from CIDX, do the Database Lookup and post it to SAP as IDoc.
Any technical documentaion or step-by-step process documents can be very helpfull to me, since I am new to XI
Thanks
SP

Lookup in XI is used to call the target data storage system and get data from there to your mapping programme.
In XI you can do Lookup in Message Mapping, Java Mapping and in XSLT Mapping. Previously Lookup in XI was system dependent. But now what ever the system are i.e. SAP system or non-sap system(Oracle,MS SQL etc) lookup API are same.
Overview of Lookup
- Lookups are used to identify/request the data from mapping program.
- It interrupt the process and looking for data which was stored in target system.
- It get that data and comeback to process and continue with that data.
Types of Lookups in XI
- JDBC Lookup: JDBC lookup is used for accessing data from database (non SAP).
- RFC Lookup: RFC lookup is used for accessing the SAP Data.
- SOAP Lookup: SOAP lookup is used for accessing data from Webservice
Steps to perform Lookup in Mapping
Import package com.sap.aii.mapping.lookup.*;
Create connection to the target Database system.
// Determine communication channel created in ID
Channel channel = null;
channel = LookupService.getChannel("DB-SYSTEM-NAME","DB-CHANNEL-NAME");
// Get system accessor for the channel.
DataBaseAccessor accessor = null;
accessor = LookupService.getDataBaseAccessor(channel);
Build the Query String.
Getting Result
// Execute Query and get the values.
DataBaseResult resultSet = null;
resultSet = accessor.execute(Query);

SAP MDM == PI== SAP ECC, IDOC posting

Similar Messages

Maybe you are looking for