Control record mapping in IDOC

Hi All,
I am doing File to IDOC scenario. In this I am using MBGMCR03. In EDI_DC40 segment I have mapped constants to the sender n receiver port, partner frofile etc. And in IDOC receiver adaptor i have selected take sender from payload. It is working fine.
However when i will transport my scenario to quality , How am i going to change all these constants with the new names?
is there any better way of doing it? Like my sender details will be automatically determined by PI system.
Thanks,
Atul

Hi Atul,
1.if i use full export for transporting SLD from DEV to QA,can i use the same tecnical systems and business systems in QA?
Can T.S and B.S also get transported from DEV to QA?
You can use same technical systems and Business systems.
1. Go to Dev SLD and Export all your SWCV, Products, Technical and Business Systems. This is nothing but saving of the SLD objects as a CIM file on your local machine. You would also need to export the Technical And Business System poitning to your XI integration server .
2. Go to the QA SLD and then import these objects exported in Step 1 in QA SLD
3. Now, create the QA Tech and Business Systems in the QA SLD
4. Go to the Dev Business systems imported on the QS SLD and you will have an option Transport Targets. In this map the Source Business System to the Target Business Systems.
Make sure that all Dev Business Systems have the correspodning Transport Targets for the QA Business SYstems
5. Now if you import the ID objects in QA , the business systems name will be renamed automatically.
2.In such case how to define business systems groups and transport targets?
You need to create Transport Groups on your QA SLD. One for Dev and One for QA. You can create Transport Groups only for Integration Server Business Systems.
And this is why you would need to export the Dev XI technical System and Business System from the SLD of Dev and Import it into the QA SLD.
2. Create the transport groups and then assign all Dev Business Systems to Dev Group, all QA Business Systems to QA group and then create the transport targets.
You use the Option related Integration server in the Business Systems to assign a Business System to a Group.
Refer
Problem regarding xi transport
How to handle SLD for Tranporting Dev to Quality ser
https://service.sap.com/~sapdownload/011000358700001684302005E/HowToSLDandXI.pdf
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/0fa2c490-0201-0010-61b4-df12869c4753
Overview of Transition from Dev to QA in XI
/people/sravya.talanki2/blog/2005/11/02/overview-of-transition-from-dev-to-qa-in-xi
/people/sap.india5/blog/2005/11/09/xi-software-logistics-ii-overview
Thanks,
Satya Kumar
Reward if it is useful..

Similar Messages

IDOC control record mapping - Sender Partner number defaulted to log. sys.

My PI scenario is file to IDOC scenario.
I have ticked "apply values from payload" checkbox, so Sender Partner Number is being defaulted to logical system assigned to my business system.
Logical system name has to be unique in PI. My understanding is that I can not have more than 1 business system with the same logical system assigned to it.
In SAP, I need to have idocs, coming from different businees systems through PI, set to have the same sender partner number,
which is not possible when "apply values from payload = 'X' and messages are coming from different business systems.
Calling all PI Gurus, have you got a workaround ?

Hi,
Idoc will be processed in SAP ECC based on the sender details (snprn,sndpor,sndpfc...) of idoc control record..
instead of different partners name sending in the sender details of control record ...pass the value of the PI logical system name in SNDPRN.... (use only one and this is common for all partners...) any how data records of idoc will have the needed partner details...
In SAP ECC you need to have this logical system ...to process the received idocs..
thats it... Hope you got
Regards
Rajesh

Passing Control Record Data in IDOC to R/3 3.1i system

Hi,
We have PI 7.0.9 installed in-house and are currently attemptng to point to an R/3 3.1i system (we are in the process of upgrading to ECC5).
When I enable the check-box to "Apply Control Record Values from Payload" in the receiver comm. channel for the IDOC adapter, it ignores the directive.
If I look at the Payload in the XML Message in the call to the IDOC adapter, the fields are all filled - however the IDoc adapter simply builds its own values when sending to the back-end. The only difference to idocs for newer SAP systems is we use EDI_DC rather than EDI_DC40.
Does anyone have any knowledge of this problem and a solution?
Thanks
Brian

Hi Brian,
About "Apply Control Record Values from Payload"
If you set the indicator, the conversion of communication parties to the IDoc partner is only possible for systems that are not logical systems.
If you do not set the indicator, all combinations of communication parties and services are handled as services without party.
If the IDoc XML structure contains a control record during outbound processing on the Integration Server, it is rejected and created again by the IDoc adapter. If you want to include additional values in the control record, set the indicator and provide an appropriate mapping for the values
If in the receiver Communication Channel, you do NOT choose option "Apply Record control value from Payload", then EDI_DC40 will contain the values mapped during Mapping in Message Monitoring and SXMB_MONI - Response Payload, but when the IDOC is sent out , control record is filled with the value from the SLD
If you are looking for, where to find the place where the logical system name for the XI system is defined, it can seen in 2 places....IN transaction SALE on XI, under "Basic Settings --> Logical Systems --> Assign Logical System to Client"...double click on the client no you want to check for...
Also it can be seen in the SLD in the corresponding business system details.
Do you want this value as the SNDPRN in the control record ? then you need not do anyhting
Also take a look at these links,
http://help.sap.com/saphelp_nw04/helpdata/en/13/95244269625633e10000000a155106/content.htm
/people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
Also have a look at this thread...
Re: SLD - Logical System Management
I hope it helps....
Regards,
Abhy

"Receiver port not valid in control record"...idoc error

Hi,
The new materials are sent to SAP via a text file which is placed in the application server which EDI uses to populate the Idoc segments and creates the material master.
Recently we upgraded from SAP 4.6 C to ERP 5.0.
After upgrading we are getting a message as Port(HPLED) invalid in control record.
I get an error message as "receiver port HPLED not valid in control record"...
It is not able to find the receiver port & hence cannot create the MM.
We checked all the config and compared with Test and production and we could not find any noticable change.
Did anyone come across any infor on this?
Your valubale reply is really very important for me.
Pls reply.
Regards,
Pri

Hey Ramesh,
I've already done the WE57 setting.
You see the WE57 setting is always done on the reciever side and not on the sender side (There is no harm but it is not what SAP recomends) The Linking on the sender side is done in the Partner Profile, where we give the extension name.
For the reciever this Partner profile setting of extension is not there therefore we need to go to WE57 and do it.
I've done all the config and have tried all the things in both the systems but somehow nothing is working.
That is why I asked that in my Inbound FM which is IDOC_INPUT_HRMD do I need to popluate one of it Parameters or fields where I mention the Extension name and all.
Yesterday however I found an SAP NOTE (105148) which tells me that my naming convention of the Extension is wrong. I have made ZHRMD_A07 extending standard IDOC tupe HRMD_A07, actually it should be ZRMD_A07. Again this is speculative I need to try this out. But I do know that SAP has various checks which checks all the naming convention and all. I'll try this out and hopefully it might work.
In the meantime any other suggestions are most invited. I am using Message type HRMD_A and using IDOC type HRM_A07
Regards
Abhishek Sahi

Version of EDI standard in control record of an IDOC

Hello All,
I want to know from where the Version of EDI(in details tab of control record) is being picked from.
Thanks,
Rakesh.

Hello Amit,
I checkd in WE30.I think release version is different from EDI version because for a vendor in the system the release is 46C whereas EDI version is V11.
Thanks,
Rakesh.

Idoc control record mapping

Hi,
I am doing a flat file to idoc scenario from ftp server to SAP and in mapping I had disabled EDI_DC40 mapping and it is populated all the fields correctly except the sender partner no. field. It is populating the value as XXXFTPDEV whereas I need the logical system name of XI system to be populated. Do I have to enable EDI_DC40 mapping and map just the sender partner field with my value or in that case case I will have to map other control fields also. Is there any other way by which I can overwrite just the sender partner no. field value?
Thanks,
Jassi

It seems SNDPRN is not populated from the values in mapping but it takes default values from IDOC adapter. I have tested this and it is mentioned in this blog also.
/people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
Is there any other way to populate sender partner no. field other than changing the logical system name in SLD?
Thanks,
Jassi

Multiple control records in inbound idoc FM

HI,
I have one basic doubt.
when we write
LOOP AT idoc_contrl
LOOP AT idoc_data where docnum = idoc_contrl-docnum.
endloop.
endloop.
does it mean there can be multiple idocs being processed with single inbound fm call.
where do we controll whether inbound fm is called for every new idoc or there will be collective processing.
Regards,

Mass Processing of IDOC's is possible but not in all the cases. Refer to the given below Link:
http://help.sap.com/saphelp_nw04s/helpdata/en/0b/2a670f507d11d18ee90000e8366fc2/content.htm
http://help.sap.com/saphelp_me52/helpdata/EN/5f/45f93b4139b478e10000000a11402f/content.htm
As far as Coding block you mentioned, I believe the same would be fired for each & every IDOC.

Changing IDOC control record by XSL Mapping

Hi,
I am using scenario: legacy -> XI -> R/3.
In the first step I am mapping XML -> IDOC. I have to map the field "SERIAL" in idoc control record in EDI_DC40 (idoc control record structure) with a constant. When I view the message in XI monitor. I cannot see the change and that field is not visible as before.
Any suggestions would be highly appreciated !
Regards,
Faiq

Hi,
If you have set the Apply Control Record Values from Payload indicator in the receiver IDoc adapter, the following fields are filled from the IDoc-XML payload:
MESCOD
   MESCFT
   TEST
   EXPRSS
   STD
   STDVRS
   STDMES
   SNDSAD
   SNDLAD
   RCVSAD
   RCVLAD
   REFINT
   REFGRP
   REFMES
   STATUS
   DIRECT
   OUTMOD
   CREDAT
   CRETIM
You can change the contents of only above fields by using a mapping and getting it replected in the SAP System.
Regards,
Bhavesh

Cannot map control record values from payload w/XSLT after SP13 upgrade

Hi!
Since we upgraded to SP13, the mapping of control record values form the XML payload to the IDOC control record (File->XI->IDOC scenario) no longer works if the mapping is done via XSLT. It works if the XI graphical mapper is used. The XSLT used is the same pre and post upgrade, but worked fine previously.
[ Apply Control Record Values from Payload is checked in the IDOC adapter comm channel. ]
Has anyone else experienced this? Am looking for any inspiration
Cheers
Duncan

Are you sure the xslt file is still there?
Maybe some non-compliance was corrected in later SP and your XSLT was using that non-compliance.
If you post the XSLT we could try to point out any possible errors.
Regards,
Henrique.

Passing Idoc Control Record information to JMS header

Hi All,
We have a requirement where we need to pass the 'MESCOD' and 'MESFCT" in the EDIDC_40 - Control record for the idoc to the Header of a JMS message.
Basically we are trying to pass IDOC Control segment to the JMS header.
I was looking at the options we have in the JMS adapter, and i am not sure how can this be achieved.
Would appreciate any info on how this can be done.
Thanks,
Karthik

Hi Karthik,
As suggested by Ravi, you can hardcode this values in XI mapping before pushing data to JMS.
Otherway round would be...check for User Exit where you can populate EDIDC_40 with MESCOD and MESFCT.
Nilesh

Passing control records to Idoc

Hi,
how can we pass control record data to Idoc?can we do that in mapping(GUI) in XI ,lets say if I am doing file to Idoc scenario.I know we can disable the control record field and use apply from payload.my concern is if we don't use apply from payload.
I have read in SDN XI takes from sender or reciever business systems as they are related to Logical systems(ref link:XI IDoc control record data source?) ,does it mean that we don't map these cotrol record fileds in the mapping(GUI)?
and also please tell me how XI can pass data from flat file to a particular IDOC?
thank you.

hi,
have a look at blog to see what is being filled and how:
/people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
you can also check my book in which I describe IDOC scenario configurations
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

BADI to Change control record from idoc

Im trying to use the BADI IDOC_CREATION_CHECK to change the control record from the idoc but im not able to do it because the parameter IDOC_CONTROL is an importing parameter not a changing parameter, Ive tried to use the BADI IDOC_DATA_MAPPER but I this case Im just able to change the data record, should I use another BADI?
Regards
Luis Constantino.

hi.
have you tried ABI_IDOC_PROC_MODIF?
i did not read much thru the documentation...
i hope this helps.

BADI/Exit: Changing IDoc Control Record

HI,
do you know a way to modify the IDoc Control Record for MASTERDATA IDocs like CREMAS/DEBMAS/ etc ?
there are a lot of IDOC Badis and Exit´s but without changing the EDIDC.
any ideas ?
Regards,
Gordon

Hi Gordon,
Did you find an answer to your question? I have the same issue and am looking for a BADI or user-exit that will allow me to change the IDOC control record.
Thanks,
Uma

Mapping of Control records in file to idoc scenario

Hi,
In the mapping part of file to idoc scenario is it necessary to provide the exact control record details
or will it pick what ever is mentioned ? Can any one please explain regarding the same?
Many Thanks,
Sharath

hi,
in case of apply control records from payload
It is indeed very simple to do it and the feature is available from SP10. I have seen lot of posts on the forum for the same and that is the reason for this blog. We can manipulate the control record in the mapping editor and map the EDI_DC40 segment of Idoc as required. Most of the times we need to map only SNDPRN, RCVPRN, SNDPRT, RCVPRT for posting Idocs with appropriate partner profiles in SAP R/3 destination systems. We can disable the rest of the fields as shown below. We need to manually change the control record of idoc for populating partner profiles in the control records while dealing with non-sap sender system, which will be used by receiver SAP system for posting idocs with appropriate ALE configurations.
check this blog
/people/sravya.talanki2/blog/2005/12/02/manipulating-idoc-control-records-from-payload
regards
chandra

Idoc control record DIRECT field mapping

Hello,
I have a file to idoc scenario where the receiver system is an external one.
I have the necessity to set in the outbound idoc control record DIRECT = 1.
The XI system is XI 3.0 SP 19 and I've set up the mapping of the idoc control record in the message mapping and selected Apply Control Record Values from Payload and Take receiver from Payload in the Receiver Communication Channel but the idoc is still generated with DIRECT = 2.
In the documentation the field DIRECT is listed as one that will be filled using the message mapping if Apply Control Record Values from Payload is selected.
How can I generate an idoc with DIRECT = 1?
Regards,
Elisa

Hello Punit,
I know that logically the right value should be 2 but the request of the receiver system is to have it as 1.
They only elaborate the idoc they receive with DIRECT = 1 (outbound).
In SAP documentation the field is listed as one that can be mapping with the message mapping but the idoc adapter is ignoring the mapping even when the Apply Control Record Values from Payload is selected.
Regards,
Elisa

Control record mapping in IDOC

Similar Messages

Maybe you are looking for