Regarding IDOC control data

Hi All,
Please let me there is any function module available for getting control record information if I pass message type to the function module.
Regards
Mahesh

Hi Mahesh,
There is no such function module available in SAP to get you the control record when you give the Message Type as input.
The simple reason is that you might be using the same message type for both inbound and outbound and for many business partners, so you cann't get the control record details that way.
If you wanted to know the basic type associated with that message type then you can use WE82 transaction for getting the corresponding basic type for that message type.
Thanks,
Mahesh.

Similar Messages

Determination Idoc Control data - Outbound

Hi Guru's
I would like to know how to get the idoc control data, like receiver port and receiver partner. For example:
I have an ABAP program which collects the IDOC data at the end I want to send out the IDOC, but what is the best way to determine the receiver information? Or how does it work in relation with partner profiles?
Best regards,
Guido Koopmann

You don't need to specify all of the information - your distribution model will take care of it. Do something like this snippet of code for the control record for output-based processing:
* Populate the control record
gs_ctrlout = gs_ctrlin.
CALL FUNCTION 'OWN_LOGICAL_SYSTEM_GET'
    IMPORTING
      own_logical_system             = lv_logsys
    EXCEPTIONS
      own_logical_system_not_defined = 1
      OTHERS                         = 2.
IF sy-subrc EQ 0.
    gs_ctrlout-sndprt = 'LS'.
    gs_ctrlout-sndprn = lv_logsys.
ELSE.
ENDIF.
gs_ctrlout-serial(8)   = sy-datum.
gs_ctrlout-serial+8(6) = sy-uzeit.
If you have a standalone program, before calling MASTER_IDOC_DISTRIBUTE, you just need to fill the message type and IDOC type in the control record.

Get wrong IDoc control data

Hi, experts, I create a extension base on baisc type SISDEL01 for delivery. And I have add the control data in WE82. But now i found when i get idoc control data, the field of extension has no value. Could somebody give me some advices? Thanks.

Hi Rick
After released the IDOC did you re imported?. Are you able to use the extended structure in PI?.
Check this as well
XI IDoc control record data source?
Thanks
Gaurav

RE: IDOC CONTROL DATA FOR ISU_IDOC_INPUT_ISU_EL40

HI,
CAN ANY BODY PLEASE TELL ME CONTROL DATA FOR ISU_IDOC_INPUT_ISU_EL40
THANKS,
Sarang

Hi raj,
i want to pass data to standard function module which genrates idoc.
function module name is ISU_IDOC_INPUT_ISU_EL40.
now i want to pass control data to IDOC_CONTRL parameter.
my itab consist of 4 fields.
first field is passed to one segment and remaining fields are passed to other segment.
So I want to know how to pass data to different segments and what should be the control data(like partner type etc.)
waiting for ur reply
Thanks,
Sarang

PI AAE = IDOC control data to ECC

Hi All,
I am using the JAVA IDOC receiver adapter to send idoc's to CRM as a test to just send idocs
Need help on the control records.
Things done
1. Passing data manually.
2. Idoc begin =1 and all segments = 1
3. Created Logical system in WE20 in CRM and created partner profile with inbound parameters.
4. Checked business system in ID and it reflects the logical system ; albiet same as the one created in ECC.
5. Created a dummy partner profile in ECC to act as XI sender
Now, can tyou please guide me how to fill the fields in EDIDC_40?
<EDI_DC40 SEGMENT="1">
         <TABNAM>EDI_DC40</TABNAM>
         <MANDT>100</MANDT>
         <DOCNUM>Should i give?</DOCNUM>
         <DOCREL>1</DOCREL>
         <STATUS>1</STATUS>
         <DIRECT>2</DIRECT>
         <OUTMOD>1</OUTMOD>
         <EXPRSS>1</EXPRSS>
         <TEST>1</TEST>
         <IDOCTYP>CRMXIF_ORDER_SAVE_M01</IDOCTYP>
         <CIMTYP>1</CIMTYP>
         <MESTYP>CRMXIF_ORDER_SAVE_M</MESTYP>
         <MESCOD>1</MESCOD>
         <MESFCT>1</MESFCT>
         <STD>1</STD>
         <STDVRS>1</STDVRS>
         <STDMES>1</STDMES>
         <SNDPOR>SAPXX1 ( DOne as part of document available- XX1 SID of pi)</SNDPOR>
         <SNDPRT>LS</SNDPRT>
         <SNDPFC>1</SNDPFC>
         <SNDPRN>XX1CLNT001 ( dUMMY CREATED IN CRM</SNDPRN>
         <SNDSAD>1</SNDSAD>
         <SNDLAD>1</SNDLAD>
         <RCVPOR>SAPXX1_SBX ( Port created in CRM)</RCVPOR>
         <RCVPRT>LS</RCVPRT>
         <RCVPFC>1</RCVPFC>
         <RCVPRN>CX1CLNT100 ( Partner profile created and inbound parameter assigned; also reflecting in the business system)</RCVPRN>
         <RCVSAD>1</RCVSAD>
         <RCVLAD>1</RCVLAD>
         <CREDAT>20140303<CREDAT/>
         <CRETIM>191016<CRETIM/>
         <REFINT/>1<REFINT/>
         <REFGRP>1<REFGRP/>
         <REFMES><REFMES/>
         <ARCKEY>1<ARCKEY/>
         <SERIAL>1<SERIAL/>
      </EDI_DC40>
I ahve something urgent to be delivered and need your help very badly

Hi All,
Exception caught by adapter framework: Sender Partner Number is not available
This is the error i get when i try to process my idoc for the receiver AAE IDOC adapter
Which value do i put in here and here is the config i have made.
1. WE20 in ECC with inbound parameters.
2. Logical system field in SLD filled for the business system i am using.
3. ICO config with Sender and receiver business components checked with the respective business systems.
4. I have also noticed that the sender business system in ID , where you check for adapter specific attributes is blank even though i have provided a logical system in SLD for the BS.Tried Clear SLD cache but still not reflecting. COULD THIS BE THE PROBLEM?
Kindly help as even if it fails i have to send over an idoc as part of my POC and i am dead late .

Hi In ALE ,IDOC HOW CONTROL DATA IS TRANSFERRED

Hi Experts,
Hi In ALE ,IDOC HOW CONTROL DATA IS TRANSFERRED .
Thanks & Regards
Bhaskar Rao.M

Hi Bhaskar Rao,
Good Check out the following documentation.
/people/kevin.wilson2/blog/2006/11/13/ale-scenario-development-guide
http://searchsap.techtarget.com/tip/0,289483,sid21_gci1230385,00.html
Some good links on ALE/IDOC
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
ALE/ IDOC/ XML
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://www.thespot4sap.com/Articles/SAP_XML_Business_Integration.asp
http://help.sap.com/saphelp_srm30/helpdata/en/72/0fe1385bed2815e10000000a114084/content.htm
IDOC Convertion
/people/kevin.wilson2/blog/2005/12/07/changing-fields-in-an-idoc-segment
Please check this online document for ALE and IDoc.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
Also check this links for additional information.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
Good Luck and thanks
AK

Some question on IDOC (Control Record/Data Record/Status Record)

Dear all,
I am new in this area, and would like to enquire some question on this topic.
When I view a IDOC via WE02, each of the IDOC record will consist of Control Record/Data Record/Status Record).
Questions:
I notice that the data records consists of many segment (i.e. E1EDK01, etc) which are use to store application data.
1 - My question is do I have to manually create all these segment and do a mapping to my application field one by one (i.e. that is when I want to create a brand new message type from scratch)?
2 - If question no. 1 is Yes, how to do it, what are the transaction code to create it? can you show me the step by step.
3 - I don't have to create the Control record and the status record for my new message type right ? because those field value will automatically pull out from partner profile and system status message, am I correct?
Thanks.
Tuff

Hi Tuff,
As everything in SAP, with IDOCs too there are
1) Standard IDOCs
2) Standard IDOCs(Extending - Enhancement to an IDOC, to accomodate for custom values)
3) Custom IDOCs
And every IDOC has,
Control record - EDIDC Structure - This mostly reflects the partner profile information, along with few more details which are used for IDOC extension, Sequencing etc
Data Records - EDID4 Structure - These records contain the actual business data of the document in concern. So for ORDERS05 it would contain order details, INVOIC02 - Invoice details so on...
Status Records - These records capture the status of an IDOC from the time it is received/sent from your system and a corresponding business document is created/changed. So this will have messages like "IDOC sent to the port OK" etc which are status from the communication layer(ALE) to application specific messages like "Sales Order XXX created" or "Invalid Material" etc.
You would have noticed something called as Process code in the partner profile, this is associated with a FM(or work flow task etc) which has the business logic coded in.
So in case of an Inbound IDOC, the sending system updates the IDOC - Control and Data records, and sends it to the receiving system. On the receiving system the IDOC's control record is validated against the partner profiles set, if an entry is found then using the process code it finds the associated FM which will decode the data from the IDOC data records as per the IDOC type and then use it to post data into SAP (VIA BDC, Batch Input, BAPI etc).
And all this while the Status records are being updated accordingly.
So with the above context will try to answer your questions,
1 - My question is do I have to manually create all these segment and do a mapping to my application field one by one (i.e. that is when I want to create a brand new message type from scratch)?
In case of a custom IDOC, yes you will have to.
In case of a standard IDOC, you wouldn't have you just have set up the necessary configuration (Partner Profile, Process code etc)
In case of a standard IDOC extended to accommodate for some custom values(for which there are no fields in standard IDOC - Let us say you have added some new fields on VA01) - In this case you can still use the standard Process code and Standard FM associated with it, SAP provides several Function exits in these FM's which you can leverage to add your custom logic.
2 - If question no. 1 is Yes, how to do it, what are the transaction code to create it? can you show me the step by step.
There are several documents available on the net and on SDN detailing step by step approach for all the above three cases,
just search for step by step guide for IDOCS - sap.
3 - I don't have to create the Control record and the status record for my new message type right ? because those field value will automatically pull out from partner profile and system status message, am I correct?
Again it depends, in case of using a standard IDOC you wouldn't have to. But in case you have some customizations/enhancements then you might have to.
For Ex: updating the control record accordingly for indicating that you have extended the standard IDOC. Or append custom messages to the status record as per the business logic.
Try out the examples you find on the net and post any specific questions you might have.
Regards,
Chen

Idoc is recieved on port but only control data

Hi all,
I hav created a program to send data on file port. Idoc gives status 03. but we we see data on recieving port (when file is generated)then data is abent only control data is recieved . No data records are there.I'm using FM EDI_OUTPUT_NEW to send data
If I send that idoc again directly running The FM EDI_OUTPUT_NEW then then conrol data and data records are recieved successfully.
Plz help me
Regards
Richa

Hi!
The data section is missing mostly in that case, if all the data fields within it is empty. IDoc sending is skipping empty fields.
In WE19, I think you entered all data within the fields.
Check your sender program, you might accidentally clear the IDoc data strucure before the MASTER_IDOC_DISTRIBUTE fm call.
Regards
Tamá

SapErrorMessage=Inconsistent IDocs passed: Data records or control records

Dear Friends
I am not a basis guy but am doing that work, since we don't have any basis admin in our company. One of our clients using our server in the lab is doing some testing of sending IDOCs from one server to another and are getting the following error message
SapErrorMessage=Inconsistent IDocs passed: Data records or control records missing..
AdapterErrorMessage=Error occurred while calling function module "INBOUND_IDOC_PROCESS" in R/3
Is there any log files or some thing that I can see to get more info on this problem. I don't know where the log files related to this kind of problems get stored. Any feedback will be highly appreciated.
Thanks
Ram

Hi,
thanks all for your help, great progress has been made!
There was no idoc record in sap as the document had not made it that far
A large part of the problem was my lack of understanding of sap versioning. My previous understanding was that you had a major version of the document: ORDERS01, ..., ORDERS05 and each of these have a version that relates to the software version, e.g. 47, 62, 64 etc.. which appears in the control record.
So I apparently have:
ORDERS05 64 V2
ORDERS05 64 V3
Can anyone explain this versioning model?
I would assume that V3 is the newer version but ...
thanks and regards
m

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

IDoc Control Record

We have an issue with one of our scenarios.
We are sending an IDoc into our SAP system but we get the message
"EDI: Partner profile not available"
Now at first this made sense as our logical system in the Partner profiles was FMS but the SLD had the sending systems logical system name as BS_FMS_QA.
We then changed it to match FMS so in the SLD under business systems the logical system is now FMS.
The issue is that we still have the problem. When we go to check the control segment of the Idoc in WE05 in the receiver system it has the Partner as BS_FMS_QA. The same value is present in the monitoring of XI for the
SAP:SNDPRN>BS_FMS_QA</SAP:SNDPRN
We have changed th value in the SLD restarted the system but still get the same result.
Could someone let me know where this value could also be kept AND where the IDoc control segment gets its values from because I thought it was the SLD.

Hi Alex,
after you changed the ALE data in the SLD for your business system, it might be necessary to reset the SLD cache on the XI IS.
Check if you have success with following SLD related content of
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c0332b2a-eb97-2910-b6ba-dbe52a01be34">How to Handle XPI Caches in SAP NetWeaver 7.0 (2004s) (PDF 1.8MB)</a>
Extract from unit 3.3 - Point 13:
SLD data of the business system is cached in table LCRT_CLNTCACHE. To display the table, use transaction SE16.
This table is populated with the data from the first request for this information.
For manual invalidation, use the function module LCR_CLEAR_CACHE in transaction SE37.
Hope this solves your issue.
Best regards,
Silvia

Problem with IDOC Control Record

Hi All,
mine is File to Idoc scenario, everything is fine, but Idoc is posted with 56 status.Even I'm giving control record at Mapping and check the option at Idoc adapter "Apply control data from payload". Sender port is not populated at Idoc and Sender and receiver partner numbers are taken other than what I had provided at mapping. Can any one explain what can I do now.

Hi Ajay,
It depends whther u wnt to go for automatic filling of control record or filling it from the payload.
In the first case, it will fill the control record with the ALE config u hv done i.e. partner profiles and port defn in we20 & we21.
In the second case also, it will do exactly the same, but in this case there shud be a corresponding ale config to wht u r filling in the mapping. The sender, receiver ports, partners, msgtype values populated in mapping shud be exactly same as tht in ur ALE config.
So, in ur case, compare the values filled in the mappin with tht of the ALE configuration.
Regards,
Akshay

How to post material master legal control data (Foreign trade export view)?

Dear Gurus,
Currently we have an external application which posts material master data into SAP using MATMAS IDOC through JCO. Now we have a requirement wherein we need to post legal control data ( especially ALNUM field) beisdes the regular views. MATMAS Idoc do not have a provision to post this specific field ALNUM ( Export control class).
Can you please suggest how to post this field value in to SAP. Do we need to use any other IDOC or RFM/BAPI as we do with classification view. In that case can you please suggest those relevant APIs.
Thanks in advance
Aman

Hi Aman,
I have got the same problem with this legal control field(ALNUM field).
There is no provison to post this field through IDOC. Can u please tell me what was the why u followed for this issue.
Thanks& regards,
Naren.

Data Origin Types not filled in the tab "Control Data" of BP interface

Hello experts,
I have loaded the clients from ECC6.0 to CRM 4.0.
Before I have loaded the clients I have maintained the data origin type for the BP in spro -> cross application components -> SAP Business Partner -> Business partner -> Basic settings -> Data Origin -> Maintain Data Origin Type.
After I have done the load initial of clients, the field "Data Origin" is empty in the tab "Control Data" in BP interface. If I do F4 in the field appear the configuration that I did in spro appear.
For this field will appear filled I'll need to do more configurations in spro?
Best regards,
Mary

Hi Mary,
The middleware does not fill this field in BP master data. You can maintain data origin type in SPRO, however the mBdoc does not use this customizing in order to fill this field.
Please try to use the BADI CRM_DATAEXCHG_BADI in order to fill this field during master data download.
It hope it helps.
Regards,
Gabriel Santana

Error: IDoc XML data record

Hi all,
   We have file->XI->idoc scenario and the problem we are facing is like, when the idoc structure is prepared using XSLT mapping, when the idoc is ready to get in thru the idoc adapter we are getting the following error.
<i><b>Error: IDoc XML data record: In segment
Z1UKGAS_HEADR attribute occurred instead of SEGMENT                                </b></i>
Anyone faced the same issue....if so pls do throw some light into this issue....
We r in XI 3.0 SP13...
Thanks & regards,
Jayakrishnan

Hi,
In an IDOC structure segment attribute is requried. From the error you posted, it looks like seqment attribute is missing.
<Z>
   <IDOC BEGIN="">
      <ED SEGMENT="">
      </ED>
   </IDOC>
</Z>
Naveen

Regarding IDOC control data

Similar Messages

Maybe you are looking for