IDOC to Idoc Serialization of Cremas and adrmas interface

Dear Friends,
This is scnario which need to develop a interface to pull specific company code data from one ECC system to another ECC system using sap PI. The data is vendor master, for which i used Serialization of adrmas and cremas. I have restricted the cremas data by implementing a user-exit. Now i am trying to restrict the address data on dependent on cremas which is not working.
Have any one who has worked on smillar scnario clarify whether it is possible by using standard filters on dependent objets or not. If not how we can achive this .
Regards
Vijay
Edited by: vijay Kumar on Mar 23, 2011 7:40 AM

Hi,
Use maintain order at runtime in SAP PI to send CREMAS and ADRMAS IDOCs sequentially to SAP ECC. This way, SAP PI will make sure ADRMAS IDOC will reach SAP ECC always after CREMAS.
Now in SAP ECC, IDOCs has to be processed sequentially. that is, the first IDOC reached should be processed first. Check with ECC ABAP person for this.
-Gouri

Similar Messages

IDOC to file but source 2 Idocs (CREMAS and ADRMAS) send PI as single file

Hi All,
I have scenario IDOC to file but source I am getting 2 Idocs (CREMAS and ADRMAS).I want merge these 2 idoc and send to single file to target. I am working on PI 7.11.Please proved your inputs.....
Regards,
Ramesh

Hi,
Thanks for your reply!!
Is there any way do with out BPM using multimapping?
Regards,
Ramesh

IDoc Configuration for Production Order Creation and Change

Hi All,
Please Help me out for IDoc Configuration for Production Order Creation and Change
I have found the IDoc for Production Order
Messgae Type : LOIPRO and IDoc type : LOIPRO01
Actually my requirment is to send the (LOIPRO01 )IDoc from SAP R/3 to XI system ,when ever the Production Order Created and Changed,
I have done following Configurations:
1. RFC Destination created for XI system
2. PORT was created for XI
3. Partner profile created WE20 and LOIPRO01 IDoc is added in OutBound Perameter.
I need to know how to do the followning.
1. How do i configure the outbound Production order idocs when Production Order is created or changed.
2. in NACE (Output control) which is the Application for Production Order.
3. How can I set IDoc as output Type for Production Order Creation.
Thanks in advance
Dhanabal T

Hi Michal,
I know that it is the old thread but still want to get clarified from you out of curiosity.
Unlike other IDOC, i actiavated change pointers for LOIPRO
1.message and idoc type is linked
2.function module , message type , idoc type is linked
function module used is CLOI_MASTERIDOC_CREATE_LOIPRO
3.BD64, distribution model is created and distributed
4. port and partner profile is in place.
5. IDOC is not getting generated after creating the process order.
do we need to activate the change documents for the message type in BD52,
if yes can you please provide the object types for the same.
or i am missing something else. please guide me in this regards.
Thanks in advance for your time.
S.Janagar

Idoc b/w sap(r/3) and non sap system .

hi gurus,
how i pass an outbound idoc b/w sap(r/3) and non sap system .
which function module we will use in this scenerio for inbound and outbound idoc both
please guide me with an example .

Hi Pawan,
Non SAP system should have RFC adapter in order to receive and send Idocs from/to SAP.
If this is not your case, you should us a Integrator Middelware with RFC and standard adapters like SAP Exchange Infrastructure.
If for example, your non SAP system is able to process data from flat files you can build next interface: SAP send Idocs to middleware that receive them using RFC adapter, middelware maps Idocs into flat file and send it to a one of non SAP system folder using FTP adapter. Non sap system triggers the flat file into its applications.
Reward points if useful.
Roger

Sender Namespace and Sender Interface in the IDOC to IDOC scenario

My question maybe very basic...
It is SAP IDOC to SAP IDOC scenario.
Lets assume that I have done config in XI for:
             Sender = A,
             Interface = B,
             Namespace = C.
My question is:
Is there a place in the source system or somewhere to point that
when an IDOC e.g. DEBMAS is triggered in the source system,
then the Interface should be B and Namespace should be C in the xml file ?
Cheers
Agnie

Hi Agnieszka,
     Check these threads/blogs from you may get some help:
/people/michal.krawczyk2/blog/2005/11/21/xi-idoc-to-idoc-tunneling--how-fast-and-easy-can-you-get
Idoc-to-idoc scenario
IDoc to IDoc scenario necessary configuration steps
For A-Z help on IDOC, you can refer Michal's book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi IDoc Business Scenarios with SAP XI</a>
Regards,
Subhasha Ranjan

Tunnelling in IDOC To IDOC and payload size

Hi XI Experts,
We runned in a PI 7.0 SP13 an IDOC To IDOc scenario with non conversion XML (Tunnelling with IDOC/XML_CONVERSION parameter set). Refer to Michal Krawczyk blog : /people/michal.krawczyk2/blog/2005/11/21/xi-idoc-to-idoc-tunneling--how-fast-and-easy-can-you-get
All seems good : payload in message monitoring is flagged as 'application/x-sap.idoc.bin' et scenario works fine.
But we have 2 questions :
Q1 : in monitoring, payload document is displaied in right bottom window like XML representation....like an XML-converted document.
Q2 : value parameter 'SIZE_PAYLOAD' in message with non conversion XML is greater than....in conversion XML ?!?....
Thanks for yours responses.
Etienne

Hi
Please find here with you the clarification,
*Q1 : in monitoring, payload document is displaied in right bottom window like XML representation....like an XML-converted document.
the value is set to XML_CONVERSION parameter to value 2
a) 0 - Every IDoc is saved as a table; no IDoc-XML conversion
b) 1 - Every IDoc is converted to IDoc-XML
c) 2 - An IDoc is converted to IDoc-XML if requested by the service
Here the IDOC is internally be treated as IDOC-XML as you would be using the Business systems with SAP. And it depends upon the services.
Q2 : value parameter 'SIZE_PAYLOAD' in message with non conversion XML is greater than....in conversion XML ?!?....
The SIZE_PAYLOAD will be always more with non-conversion XML includes the header details also..(I am not sure with it).
Its better that you copy the XML Payload and save on local PC. Then check with its size.
thanks
Swarup

I have a scenario, ECC-PI-Message broker. ECC sending IDOC to PI, PI execute mapping and sending data to Message borker.(with almost one to one mapping)., IDOC(AAE)-PI-JMS. Now my requirement is., from PI after mapping we need to save file in SAP fold

I have a scenario, ECC-PI-Message broker. ECC sending IDOC to PI, PI execute mapping and sends data to Message borker(thru JMS channel).(with almost one to one mapping)., IDOC(AAE)-PI-JMS. Now my requirement is., from PI after mapping we need to create file with same data what ever send to Message broker and put the file in SAP folder without touching mapping. Is it possible? Please advise with the steps. We are using the ICO for this senario. Quick response is appriciated.

Hi Pratik,
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/502991a2-45d9-2910-d99f-8aba5d79fb42?quicklink=index&overridelayout=true
This link might help.
regards
Anupam

IDOC --BPM--IDOC AND FILE

Hi Experts,
My scenario is idoc to idoc and file through BPM.
so I hve one integration process and 2 receiver.The prob is frm IP it is pointing to only file not to IDOC
1) 1 sender agreement
2) 3 receiver determination
3) 3 interface determination
please help me out..

Why are you using BPM for this?it is not good design.
If you want to still use bpm then
1)1 receive step,
2)2 transformations steps(if or are executing Operation mapping in IP).
3)2 send steps.
check your BPM design and monitor Integration process work flow.
Regards,
Raj

Difference in idoc adapter header mapping between SP14 and SP19

Hi All,
i have a very strange problem.......i have 2 XI systems : XI-sandbox and XI-dev.....
XI-sandbox is on XI3.0 SP19 whereas XI-dev is on XI3.0 SP14...........
I have a file->XI->idoc scenario which is same on both XI-sandbox and XI-dev....
in receiver idoc adapter, i am using header mapping for sender service and in the sender service i am using XPATH of a field of control rec of idoc.........
this scenario works fine on XI-sandbox which is on SP19 and the idocs are sent to SAP R/3 sandbox...........but this scenario on XI-dev gives error in SXMB_MONI in XI-dev of Call adapter - "No party conversion found".........
So my question is that is there any difference in idoc adapter header mapping between SP14 and SP19.........
Thanks,
Rajeev Gupta
Message was edited by:
RAJEEV GUPTA

><i>so i cant use apply control rec values from payload.........</i>
rajeev,
I know this has nothing to do with the original problem but please do bear.
If I undertood you posts correct, the Sender Partner Name is set in the Idoc Control record in the field SNDPRN in the mapping using some mapping logic.
Now, this is the partner name with which the idoc is to be posted to thge R3 system.
if yes, then like I have pointed above, using "Take Sender From Payload" in the Receivcer Idoc Adapter is a better option as pointed in the SAP help as well.
As you are already populating the idoc control ecord with SNDPRN just make the SNDPRT as LS and then select "Take Sender from Payload" in the receiver Idoc adapter and the Sender Partner Name will not be taken from SDNPRN just as you want.
This is different from "Apply Control Records From Payload" .
Regards
Bhavesh
PS : you can ignore this reply if the situatios is too late to make this change and thanks for the patience.

APP and Bank interface with IDOC

Dear Friends,
We are in process of interface between APP with Bank for processing the Bank payments.
Need a clarification that is it ok if I can use the IDOC instead of using DME standard program to move file to Bank server and also want to know that is it ok for processing the IDOCs for APP documents.
Kindly provide the broader view of pros and cons for above query.
Thanks MD.

IDOC is also a standard way and recommended approach. You can generate it via RFFOEDI1.
Just check that your bank is able to process the IDOC file in standard format (like PEXR2002 format)
Regards,
Gaurav

Diff... between ALE, IDOC, RFC, BAPI, BADI --- Not clear and clarify

Hi All
    I am learning XI and the difference between " ALE, IDOC, RFC, BAPI, BADI "
    Not clear and when to use what and how in point of XI ?
   Pl..clarify me
Adv..thanks and points
--- Rakesh Behera

Hi
This will expalin you every thing ...pl..go through
The interface concept of the classic R/3 is based on two different strategies: Remote Function Calls (RFC) and data exchange through IDoc message documents. RFC makes direct and synchronous calls of a program in the remote system. If the caller is an external program it will call an RFC-enabled function in R/3 and if the calling program is the R/3 system it will call an RFC-function in another R/3-system or it will call a non-R/3 program through a gateway-proxy (usually rfcexec.exe). BAPIs are a subset of the RFC-enabled function modules, especially designed as Application Programming Interface (API) to the SAP business object, or in other words: are function modules officially released by SAP to be called from external programs.
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
The philosophical difference between EDI and ALE can be pinned as follows: If we send data to an external partner, we generally speak of EDI, while ALE is a mechanism to reliable replicate data between trusting systems to store a redundant copy of the IDoc data. The difference is made clear, when we think of a purchase order that is sent as an IDoc. If we send the purchase order to a supplier then the supplier will store the purchase order as a sales order. However, if we send the purchase order via ALE to another R/3 system, then the receiving system will store the purchase order also as a purchase order.
I hope this will help you to understand the difference bet..those
regards
--- prasad

IDoc to IDoc scenario with Master and Item data

Hi,
We are developing a scenario where IDoc will be coming with Master ana Item data.
In the receiver side Master IDoc must be created every time and Item IDoc must be created only if the particular segment occurs.
Is it possible to do this scenario with out BPM.
Thanks and Regards,
Jeevan.

Hi,
Its possible without BPM.
1)Export the target Idoc
2)Change the occurance of Idoc to 0..unbounded
3)Also change the occurance segment to 1
4) Now import this external definition in the target.
Refer this blog for details :
The specified item was not found.

Sendind idoc tcode foe msg type WVINVE and WPUUMS

Dear All,
What is the tcode for sending phy inventory data through IDOC message typy WVINVE, and also for message type WPUUMS POS interface: Upload sales data (Compressed)
Ex: BD10 for sending material.
Thanks and regards,
Arun.

Hi,
Wpuums is inbound IDOC so you can crete this IDOC with the help of We19
and for testing purpoase u can use WPUK tcode
Thanks
Amit Shivhare

Standard Idoc for Goods Issue from MIGO and standard BADI to do the MIGO-GI

Hi Gurus
What is the standard IDoc for Goods Issue from MIGIO and standard BADI that takes care of Goods Issue from MIGO?
Thanks

BADI :
MB_MIGO_ITEM_BADI
MB_MIGO_BADI
Idocs:
/ISDFPS/GOODSMVT_SAPCREATE01
/CWM/MBGMCR01

Very simple and working IDoc to IDoc scenario

Hi!
I would like to implement for demo issues a working IDoc to IDoc scenario with SAP XI 7.0.
The IDocs sohuld be send from SAP ECC 6.0 system client 100 to SAP ECC 6.0 system client 200.
Questions:
- which material type should be used (e.g. MATMAS02,..)
- how should the message mapping (e.g. MATMAS02 to MATMAS02) look like
- what are the other settings in IB Repository and IB Configuration
- how should the test from WE19 look like?
Thank you very much!

Hi Holger,
No issues for that , U can use the MATMAS 02 or MATMAS 03.
Setting in R/3 system:
1) Create the RFC Destination(SM59).
2) Create the tRFC port(WE21)
3) Create the Partner profiles( WE20)
4) Create the Distribution Model(BD64)
Setting in XI:
1) Create the RFC Destination
2) Create the IDOC Port into IDOC Adapter(IDX1)
3) Load the Metadata into IDOC into IDOC Adapter(IDX2).
Same settings happened in Receiver IDOC also.
Directory : No need to create the Sender agreement & no need to create the Sender Communication Channel.
Repoistery: Import the Sender IDOC and Receiver IDOC from R/3 system.
In WE19 Testing tool we can test IDOC generated or not.
Regards,
Sateesh
D

IDOC to Idoc Serialization of Cremas and adrmas interface

Similar Messages

Maybe you are looking for