In exit EXIT_SAPLKD01_001 populate custom segment of idoc ext. cremas05

Hi,
I am using EXIT_SAPLKD01_001 where I need to populate 2 custom segments for idoc extension cremas05.
I have created a function module separately where I have populated the 2 structures that is of same type as the segment structure.
In the exit I have called the function module where the structures are populated.
Now my question is how to populate the custom segments from the function module structures directly in the exit.
Thanks and Regards
P

Hi
Now I'm able to do this.... closing the thread.

Similar Messages

Fill / populate customer segments in extension of ARTMAS05

hi,
currently looking for a solution to this.
1) I need to add customer segments to an extended version of ARTMAS05.
Name to clear yet. But it will e a cimtype of ARTMAS05.
2) system is a retail system.
- SAP ECC 6.0
- SAP_APPL 6000 / level 9
I have looked for enhancement spots and user exits. The only thing close to it is enhancement project MGV00003. There I got a component( EXIT_SAPLMV01_003) to populate the EXT segments / containers. But I cannot fill / populute own segments there.
I want to sent the data using tcode BD10 (report RBDSEMAT). No exits found in there I could need.
Anybody done something like this? Knows the right enhancment section or spot? Or did you just modify the thing which I would really want to avoid. If possible.
Thanks for an anwer.
Rob

Hello Freinds,
Can Some body help me. I am facing the same problem as in this post. I have extended Orders05 Idoc and followed below steps.
Created Segment - Created Extended Idoc with Custom Segment created - Released both Segment and Idoc - Attached Idoc to ORDERS message type - Added message type to model view - maitained partner Profiles with extended idoc u2013 I have written my custom code in User Exit u2018EXIT_SAPLEINM_002u2019 - activated my project.
The problem I am facing is u2013 When I keep a breakpoint at the user exit u2013 it never stops u2013 it just creates an basic idoc. I have tried keeping breakpoint at all the places where I can think but no where it is stopping.
Thanks for the help.

User exit to update extended segment in idoc for va01

Hi Experts,
I am working on Outbound IDOC interface for VA02 and VA01
I am using ORDERS05 IDOC type
i want to create one custom segment
and i want to fill that custom segment
but i am not able to find user exit to update this custom segment
please help.

Akshay,
I think you want to send order response for the orders created via Va01 or edited by Va02
To do this steps are:-
1) Use FM IDOC_OUTPUT_ORDRSP to send order response (ORDERS05)
2) Find the function exits in this Fm using search string as " Call Customer-function".
3) Use include in the exits to write code to append new segments to the IDOC. Look for the Tables parameter in the Exits which are of structure type EDIDD. Insert new Segment details in this table and your IDOC will be generated with required values.
Hope this helps!!
Harry

Populating the custom segments for the Basic type attached to HRMD_A (IDOC)

Hi,
I've enhanced a few infotypes and want the new fields to be available in an IDOC created through the program RHALEINI.
Here are the steps I followed.
Step 1 :(we31)
We created new segment Z1IT023 , containing all the fields from infotype 0023 along with the custom fields added.
Step 2 :(we30)
We created an extension of IDOC type HRMD_A07 by name HRMD_EX to include this segement.
Step 3 :
We added an entry in table EDIMSG against message type HRMD_A , with base type : HRMD_A07 , extension : HRMD_EX , version : 700
Step4 :(we20)
Now , we made changes to partner profile by adding entry for message type HRMD_A with base IDOC type as HRMD_A07 and extension as HRMD_EX
Step5:
We changed the entry in table T777D and specified the IDOC segment as Z1IT023.
Step6.
We then tried to execute the report RHALEINI to generate the IDOC. The IDOC got created, but it didn't have the data for the segment Z1IT023.
In fact, there is a different solution to this... by adding the custom segment(containing nly the new infotype fields) as a child of the original segment E1P0023 and then writting code in the user-exit to populate the segment, but our intension is to have a single segment with all the infotype 0023 data. Besides, I believe in HR, making an entry in T777D should free us from writing any code for populating the IDOC segments.
Can anybody please suggest me, where am I going wrong. How can the new segments be populated automatically.
Thanks in advance.
Sujit.
Responses will be suitably rewarded.

Hi,
Did u get any exit to populate the custom segment?
Thanks,
San

How to enhance DEBMDM06 to add custom segments and do mass message transf

Hi Team,
I have a requirement to transfer multiple IDocs(Customers) as a single IDoc to PI (Earlier XI) system. As I know this could be done by doing necessary config in ALE and execute the transaction MDM_CLNT_EXTR(MDMC specific to customer master day) by creating a variant with proper Extraction Object details. This works perfect with only standard idoc type DEBMDM05/06.
1. I have extended the IDoc type DEBMDM06 to ZEUDEBMDM06
2. Created a new message type ZDEBMDM (using WE81)
3. Assigned the message type to IDoc type(using WE82).
4. Created a new extraction object ZCUSTOMER_EXTRCT from CUSTOMER_EXTRACT by executing
program 'MDM_METADATA_MAINTAIN'.
5. Maintained the view 'VMDMMETA' using SM30 to add custom segments and altered the positions according to new IDoc type.
6. Found a user exit to fill custom segments.
7. Executed the transaction MDMC, in the debug managed the hord coded extraction object from 'CUSTOMER_EXTRACT'
to 'ZCUSTOMER_EXTRCT'.
This has generated a single IDOC for 2 customers but ulike one segment for one customer, it has addes somany segments at same level.
Can we enhance the mass message transfer concept so that we can use it for extended IDOC type so that I can have custom segment types added ?
Thanks in advance...
Arun
Edited by: Arunkumar Ponnoju on Sep 8, 2009 11:31 AM

hi Caíque ;
Firstly thanks for your answer.But your badi is at CRM side, I want to fill BDOC with custom fields from ECC to CRM when I changed them in IE02 of ECC.
Do you know there is any badi after BDOC is filled in ECC.
Regards.

Do any standard functions populate all segments?

I have been using the ALE Send transactions for MATMAS and BOMMAT. But now I am discovering that all of the segments in the IDOC it creates are there. Is there a different mechanism (other than writing ABAP) to get more of the segments populated? I'm especially interested in the E1CUCFG that is not available in MATMAS05.
I would also like to have the BOMMAT IDOC generated for all effectivities instead of just one. Is this possible, and how?

Hi Paul,
Please check this links which will help you to know more detail on how to use user exits.
http://sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://sap-img.com/abap/what-is-user-exits.htm
http://sap-img.com/abap/what-is-the-difference-between-smod-and-cmod.htm
The best user exits to populate E1CUCFG segments is EXIT_SAPLMV01_002.
It depends on your business requirements. You can use change pointers to send MATMAS and BOMMAT IDocs if there are master data changes by running or schedule program RBDMIDOC.
Hope this will help.
Regards,
Ferry Lianto
Please reward points if very helpful.

Problem in filling Custom segment data using User Exit for ZORDERS05

Hi,
I am using Process Code SD10 to generate the custom Idoc ZORDERS05.
The function module used is IDOC_OUTPUT_ORDRSP.
I am able to succesfully generate the Custom Idoc (VA02->Extras->Header->Edit) but unable to populate the custom segments in the IDOC.
I have tried to write the code in User Exit EXIT_SAPLVEDC_003 -> ZXVEDU15. But still I'm unable to populate the Z segments.
Even though I place a break point in the FM or in the User Exit during the generation of Idoc the control doesn't stop in FM nor in the User Exit.
I am unable to understand how to go about this.
Can anybody please help me with this?
Thanks in Adavance,
Rohan.

Okay I under what you are speaking about NACE.
Yes that configuration has been done and I am sucessfully able to generate the IDOC.
But even though I know that in FM IDOC_OUTPUT_ORDRSP, I have to write code in User Exit EXIT_SAPLVEDC_003 to populate the Z segments; I'm unable to understand y the control doesn't pick the FM and Exit.
Right now I have code in the Exit to fill Z segments.
Thanks
Rohan.

User Exit is required to populate PO type in IDOC

Hi,
My requirement is:
DELVRY03 Idoc presently doesn't carry any field in which we can store a purchase order.
here i need to extend the idoc with a new segment with PO type as field and sales order number field.
I need to get Purchase document type field(BSART). from EKKO table ,
here i need to retrieve the PO number from the line item reference field LIPS-VGBEL., based on the PO number i need to get the EKKO-BSART.
in which exit i need to write the logic for this.
Pls help me on this ASAP.
Thanks,
Satish

Hi
Go to the related Function module for this IDOC type/Message Type/PROCESS CODE which you are using for this purpose
then in that Fun module search for the CUSTOMER-FUNCTION's which are nothing but the user exits where we write code to populate the custom segments and other values.
search for the relavent FUNCTION and write the above code.
Regards
Anji

Custom segments to basic IDOC type without extension

Hi,
Is it possible that an IDOC has custom segments which are getting populated and the basic type does not have any custom segments.
How should we find from where the custom segments are getting populated and displayed?
Regards,
Subhashini

Hello,
Lets say in DELVRY05 Idoc Type, we have a Segment Called E1EDL20 and since this is a Standard SAP Provided Basic Type, it will not have any Custom Segments ( Z-Segments). Now, If I want some additional Information to be populated as part of a Custom Segment, what I would do is to Create an IDoc Extension ZDELVRY05 with reference to the Basic Type DELVRY05 and Create a Custom Segment Z1EDL20 (Per Say) in which I'll populate the Custom Data Fields using an Exit. So, unless we create an IDoc Extension for a Basic Type, the Standard SAP Basic Type will not have any Custom Segments-Fields (Z-Segments).
Thanks,
Venkata Phani Prasad K

How to add a custom segment in standard IDoc?

Hi,
I want to add a custom segment in stanard IDoc type (eg. MATMAS). I don't want to go for extended idoc (copying stanard idoc into zidoc and adding custom segment).
Please tell me.

Hello
Transaction BD10 uses fm MASTERIDOC_CREATE_REQ_MATMAS which in turn uses MASTERIDOC_CREATE_MATMAS to create and distribute material master IDocs.
Fm MASTERIDOC_CREATE_MATMAS belongs to function group MV01 in package MGV. Here you will find the user-exit function group XMGV.
Perhaps EXIT_SAPLMV01_002 might be useful for you.
Regards
Uwe

BD10 and BD21 - Idoc custom segment - Error in BD21 but no error in BD10

Hi All,
I have a custom segment 'ZXXXXX' added to MATMAS05 idoc type.
When I use BD10 to send a material to another system I don't have any errors but when I use BD21 Change pointers I'm getting an internal error.
Is there something I need to add so that it works both for BD10 and BD21 without any errors?
Please help.
Meghna

Do you have a filter in the distribution model for a field in your custom segment ?
If yes ... you have to assign parameter CIMTYP (changing parameter) in your customer exit with the Value of your "IDoc Extensionname"
Example:
IDOCTP = MATMAS05
Extzension = ZZMATMAS
P_CIMTYP = 'ZZMATMAS'.
That´s all !

SAP ER Connector 9.1.2.2 IDOC Data Parser Error to read custom segments

Hi,
We are in the trouble to find out the root cause of the issue in SAP Employee Reconciliation Connector 9.1.2.2 for processing idoc. As per our requirment, we need to retreive the field values in the custom segments(ZHR) other than the base segments(E2P). As we tried a lot for the couple of days and identified the custom segment filednames are not parsing by SAP HRMS Listener (in tRFC mode of communication).. The same idoc file works properly to retreive the value in the reconciliation event at "SAP User Reconciliation" (in file port). Its strange why it is not reading the idoc through listener. Will there be any db refresh or any configuration on SAP system required to do in tRFC mode of idoc file transfer?
OIM Log :-
INFO,11 Apr 2013 12:16:53,513,[OIMCP.SAPH:info],oracle.iam.connectors.sap.common.parser.HRMDAParser : parse() : process_IDOC ROOT:General root segment
DEBUG,11 Apr 2013 12:16:53,514,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : getFieldValue():: STARTED
DEBUG,11 Apr 2013 12:16:53,515,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : getFieldValue() : returned value is: 12507708
DEBUG,11 Apr 2013 12:16:53,516,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : getFieldValue():: FINISHED
DEBUG,11 Apr 2013 12:16:53,516,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : isValidRecord():: FINISHED
DEBUG,11 Apr 2013 12:16:53,517,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : isValidRecord():: FINISHED
DEBUG,11 Apr 2013 12:16:53,518,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : isValidRecord() : return value is TRUE
DEBUG,11 Apr 2013 12:16:53,518,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : isDeletedUser():: STARTED
DEBUG,11 Apr 2013 12:16:53,519,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : isDeletedUser():: FINISHED
DEBUG,11 Apr 2013 12:16:53,520,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processChildSegment():: STARTED
DEBUG,11 Apr 2013 12:16:53,520,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord():: STARTED
DEBUG,11 Apr 2013 12:16:53,521,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord() : Personnel Number set to 12507708
DEBUG,11 Apr 2013 12:16:53,522,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord():: FINISHED
DEBUG,11 Apr 2013 12:16:53,522,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processChildSegment():: STARTED
DEBUG,11 Apr 2013 12:16:53,523,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord():: STARTED
DEBUG,11 Apr 2013 12:16:53,524,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord():: FINISHED
DEBUG,11 Apr 2013 12:16:53,524,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processChildSegment():: STARTED
DEBUG,11 Apr 2013 12:16:53,525,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : getFieldValue():: STARTED
DEBUG,11 Apr 2013 12:16:53,526,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : getFieldValue() : returned value is: Sat May 25 00:00:00 PDT 1985
DEBUG,11 Apr 2013 12:16:53,527,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : getFieldValue():: FINISHED
DEBUG,11 Apr 2013 12:16:53,529,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord():: STARTED
DEBUG,11 Apr 2013 12:16:53,529,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord() : First Name set to SRI
DEBUG,11 Apr 2013 12:16:53,530,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord() : Middle Name set to RAM
DEBUG,11 Apr 2013 12:16:53,531,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord() : Last Name set to RAM
DEBUG,11 Apr 2013 12:16:53,531,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord():: FINISHED
DEBUG,11 Apr 2013 12:16:53,532,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processChildSegment():: STARTED
DEBUG,11 Apr 2013 12:16:53,533,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : getFieldValue():: STARTED
INFO,11 Apr 2013 12:16:53,534,[OIMCP.SAPH:info],oracle.iam.connectors.sap.common.parser.HRMDAParser : getFieldValue() : (5) IDOC_ERROR_FIELD_NOT_FOUND: Field "BEGDA" is not a member of IDocRecord "ZHR_OIM000".
DOCUMENT: type=HRMD_A06, type extension=ZHRMD_A06_OIM, number=0000000002303362; SEGMENT: type=ZHR_OIM, definition=ZHR_OIM000; FIELD: name=BEGDA
DEBUG,11 Apr 2013 12:16:53,534,[OIMCP.SAPH:debug],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord():: STARTED
ERROR,11 Apr 2013 12:16:53,535,[OIMCP.SAPH:error],====================================================
ERROR,11 Apr 2013 12:16:53,536,[OIMCP.SAPH:error],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord() : (5) IDOC_ERROR_FIELD_NOT_FOUND: Field "MGRFLG" is not a member of IDocRecord "ZHR_OIM000".
DOCUMENT: type=HRMD_A06, type extension=ZHRMD_A06_OIM, number=0000000002303362; SEGMENT: type=ZHR_OIM, definition=ZHR_OIM000; FIELD: name=MGRFLG
ERROR,11 Apr 2013 12:16:53,537,[OIMCP.SAPH:error],====================================================
ERROR,11 Apr 2013 12:16:53,538,[OIMCP.SAPH:error],================= Start Stack Trace =======================
ERROR,11 Apr 2013 12:16:53,539,[OIMCP.SAPH:error],oracle.iam.connectors.sap.common.parser.HRMDAParser : processRecord()
ERROR,11 Apr 2013 12:16:53,539,[OIMCP.SAPH:error],(5) IDOC_ERROR_FIELD_NOT_FOUND: Field "MGRFLG" is not a member of IDocRecord "ZHR_OIM000".
DOCUMENT: type=HRMD_A06, type extension=ZHRMD_A06_OIM, number=0000000002303362; SEGMENT: type=ZHR_OIM, definition=ZHR_OIM000; FIELD: name=MGRFLG
ERROR,11 Apr 2013 12:16:53,540,[OIMCP.SAPH:error],Description : (5) IDOC_ERROR_FIELD_NOT_FOUND: Field "MGRFLG" is not a member of IDocRecord "ZHR_OIM000".
DOCUMENT: type=HRMD_A06, type extension=ZHRMD_A06_OIM, number=0000000002303362; SEGMENT: type=ZHR_OIM, definition=ZHR_OIM000; FIELD: name=MGRFLG
ERROR,11 Apr 2013 12:16:53,541,[OIMCP.SAPH:error],com.sap.conn.idoc.IDocFieldNotFoundException: (5) IDOC_ERROR_FIELD_NOT_FOUND: Field "MGRFLG" is not a member of IDocRecord "ZHR_OIM000".
DOCUMENT: type=HRMD_A06, type extension=ZHRMD_A06_OIM, number=0000000002303362; SEGMENT: type=ZHR_OIM, definition=ZHR_OIM000; FIELD: name=MGRFLG
at com.sap.conn.idoc.rt.record.impl.AbstractRecord.indexOf(AbstractRecord.java:457)
at com.sap.conn.idoc.rt.record.impl.AbstractRecord.getValue(AbstractRecord.java:1881)
at oracle.iam.connectors.sap.common.parser.IDOCParser.processRecord(Unknown Source)
at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
at oracle.iam.connectors.sap.common.parser.HRMDAParser.parse(Unknown Source)
at oracle.iam.connectors.sap.common.parser.SAPIDOCListener$IDocHandler.handleRequest(Unknown Source)
at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:341)
at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:160)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3366)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2844)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2663)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2554)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2375)
at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:284)
at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:369)
at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:245)
at java.lang.Thread.run(Thread.java:662)
ERROR,11 Apr 2013 12:16:53,542,[OIMCP.SAPH:error],================= End Stack Trace =======================
ERROR,11 Apr 2013 12:16:53,542,[OIMCP.SAPH:error],====================================================
ERROR,11 Apr 2013 12:16:53,543,[OIMCP.SAPH:error],oracle.iam.connectors.sap.common.parser.HRMDAParser : processChildSegment() :
ERROR,11 Apr 2013 12:16:53,544,[OIMCP.SAPH:error],====================================================
ERROR,11 Apr 2013 12:16:53,545,[OIMCP.SAPH:error],================= Start Stack Trace =======================
ERROR,11 Apr 2013 12:16:53,546,[OIMCP.SAPH:error],oracle.iam.connectors.sap.common.parser.HRMDAParser : processChildSegment()
ERROR,11 Apr 2013 12:16:53,546,[OIMCP.SAPH:error],
ERROR,11 Apr 2013 12:16:53,547,[OIMCP.SAPH:error],Description :
ERROR,11 Apr 2013 12:16:53,547,[OIMCP.SAPH:error],oracle.iam.connectors.common.ConnectorException:
at oracle.iam.connectors.sap.common.parser.IDOCParser.processRecord(Unknown Source)
at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
at oracle.iam.connectors.sap.common.parser.HRMDAParser.parse(Unknown Source)
at oracle.iam.connectors.sap.common.parser.SAPIDOCListener$IDocHandler.handleRequest(Unknown Source)
at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:341)
at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:160)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3366)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2844)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2663)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2554)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2375)
at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:284)
at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:369)
at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:245)
at java.lang.Thread.run(Thread.java:662)
Caused by: com.sap.conn.idoc.IDocFieldNotFoundException: (5) IDOC_ERROR_FIELD_NOT_FOUND: Field "MGRFLG" is not a member of IDocRecord "ZHR_OIM000".
DOCUMENT: type=HRMD_A06, type extension=ZHRMD_A06_OIM, number=0000000002303362; SEGMENT: type=ZHR_OIM, definition=ZHR_OIM000; FIELD: name=MGRFLG
at com.sap.conn.idoc.rt.record.impl.AbstractRecord.indexOf(AbstractRecord.java:457)
at com.sap.conn.idoc.rt.record.impl.AbstractRecord.getValue(AbstractRecord.java:1881)
... 18 more
ERROR,11 Apr 2013 12:16:53,548,[OIMCP.SAPH:error],================= End Stack Trace =======================
ERROR,11 Apr 2013 12:16:53,549,[OIMCP.SAPH:error],====================================================
ERROR,11 Apr 2013 12:16:53,550,[OIMCP.SAPH:error],oracle.iam.connectors.sap.common.parser.HRMDAParser : processChildSegment() :
ERROR,11 Apr 2013 12:16:53,550,[OIMCP.SAPH:error],====================================================
ERROR,11 Apr 2013 12:16:53,552,[OIMCP.SAPH:error],================= Start Stack Trace =======================
ERROR,11 Apr 2013 12:16:53,552,[OIMCP.SAPH:error],oracle.iam.connectors.sap.common.parser.HRMDAParser : processChildSegment()
ERROR,11 Apr 2013 12:16:53,553,[OIMCP.SAPH:error],
ERROR,11 Apr 2013 12:16:53,554,[OIMCP.SAPH:error],Description :
ERROR,11 Apr 2013 12:16:53,554,[OIMCP.SAPH:error],oracle.iam.connectors.common.ConnectorException:
at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
at oracle.iam.connectors.sap.common.parser.HRMDAParser.parse(Unknown Source)
at oracle.iam.connectors.sap.common.parser.SAPIDOCListener$IDocHandler.handleRequest(Unknown Source)
at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:341)
at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:160)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3366)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2844)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2663)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2554)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2375)
at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:284)
at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:369)
at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:245)
at java.lang.Thread.run(Thread.java:662)
Caused by: oracle.iam.connectors.common.ConnectorException:
at oracle.iam.connectors.sap.common.parser.IDOCParser.processRecord(Unknown Source)
... 17 more
Caused by: com.sap.conn.idoc.IDocFieldNotFoundException: (5) IDOC_ERROR_FIELD_NOT_FOUND: Field "MGRFLG" is not a member of IDocRecord "ZHR_OIM000".
DOCUMENT: type=HRMD_A06, type extension=ZHRMD_A06_OIM, number=0000000002303362; SEGMENT: type=ZHR_OIM, definition=ZHR_OIM000; FIELD: name=MGRFLG
at com.sap.conn.idoc.rt.record.impl.AbstractRecord.indexOf(AbstractRecord.java:457)
at com.sap.conn.idoc.rt.record.impl.AbstractRecord.getValue(AbstractRecord.java:1881)
... 18 more
ERROR,11 Apr 2013 12:16:53,555,[OIMCP.SAPH:error],================= End Stack Trace =======================
ERROR,11 Apr 2013 12:16:53,556,[OIMCP.SAPH:error],====================================================
ERROR,11 Apr 2013 12:16:53,556,[OIMCP.SAPH:error],oracle.iam.connectors.sap.common.parser.HRMDAParser : processChildSegment() :
ERROR,11 Apr 2013 12:16:53,557,[OIMCP.SAPH:error],====================================================
ERROR,11 Apr 2013 12:16:53,558,[OIMCP.SAPH:error],================= Start Stack Trace =======================
ERROR,11 Apr 2013 12:16:53,559,[OIMCP.SAPH:error],oracle.iam.connectors.sap.common.parser.HRMDAParser : processChildSegment()
ERROR,11 Apr 2013 12:16:53,559,[OIMCP.SAPH:error],
ERROR,11 Apr 2013 12:16:53,560,[OIMCP.SAPH:error],Description :
ERROR,11 Apr 2013 12:16:53,561,[OIMCP.SAPH:error],oracle.iam.connectors.common.ConnectorException:
at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
at oracle.iam.connectors.sap.common.parser.HRMDAParser.parse(Unknown Source)
at oracle.iam.connectors.sap.common.parser.SAPIDOCListener$IDocHandler.handleRequest(Unknown Source)
at com.sap.conn.idoc.jco.rt.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:341)
at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:160)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:3366)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2844)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2663)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2554)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2375)
at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:284)
at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:369)
at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:245)
at java.lang.Thread.run(Thread.java:662)
Caused by: oracle.iam.connectors.common.ConnectorException:
at oracle.iam.connectors.sap.common.parser.HRMDAParser.processChildSegment(Unknown Source)
... 16 more
Caused by: oracle.iam.connectors.common.ConnectorException:
at oracle.iam.connectors.sap.common.parser.IDOCParser.processRecord(Unknown Source)
... 17 more
Caused by: com.sap.conn.idoc.IDocFieldNotFoundException: (5) IDOC_ERROR_FIELD_NOT_FOUND: Field "MGRFLG" is not a member of IDocRecord "ZHR_OIM000".
DOCUMENT: type=HRMD_A06, type extension=ZHRMD_A06_OIM, number=0000000002303362; SEGMENT: type=ZHR_OIM, definition=ZHR_OIM000; FIELD: name=MGRFLG
at com.sap.conn.idoc.rt.record.impl.AbstractRecord.indexOf(AbstractRecord.java:457)
at com.sap.conn.idoc.rt.record.impl.AbstractRecord.getValue(AbstractRecord.java:1881)
... 18 more
ERROR,11 Apr 2013 12:16:53,561,[OIMCP.SAPH:error],================= End Stack Trace =======================
ERROR,11 Apr 2013 12:16:53,562,[OIMCP.SAPH:error],====================================================
ERROR,11 Apr 2013 12:16:53,563,[OIMCP.SAPH:error],oracle.iam.connectors.sap.common.parser.HRMDAParser : processChildSegment() :

Now i am able to configure but i am seeing this error
java.lang.UnsatisfiedLinkError: /opt/Oracle/jco/libsapjco3.so: /opt/Oracle/jco/libsapjco3.so: ELF file data encoding not little-endian (Possible cause: endianness mismatch)
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1807)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1732)
at java.lang.Runtime.loadLibrary0(Runtime.java:823)
at java.lang.System.loadLibrary(System.java:1028)
at com.sap.conn.jco.rt.DefaultJCoRuntime.loadLibrary(DefaultJCoRuntime.java:444)
at com.sap.conn.jco.rt.DefaultJCoRuntime.registerNativeMethods(DefaultJCoRuntime.java:310)
at com.sap.conn.jco.rt.JCoRuntime.registerNatives(JCoRuntime.java:1027)
at com.sap.conn.rfc.driver.CpicDriver.<clinit>(CpicDriver.java:956)
at com.sap.conn.rfc.engine.DefaultRfcRuntime.getVersion(DefaultRfcRuntime.java:43)
at com.sap.conn.rfc.api.RfcApi.RfcGetVersion(RfcApi.java:261)
at com.sap.conn.jco.rt.MiddlewareJavaRfc.<clinit>(MiddlewareJavaRfc.java:198)
at com.sap.conn.jco.rt.DefaultJCoRuntime.initialize(DefaultJCoRuntime.java:75)
at com.sap.conn.jco.rt.JCoRuntimeFactory.<clinit>(JCoRuntimeFactory.java:23)
at com.sap.conn.jco.rt.About.<init>(About.java:42)
at com.sap.conn.jco.rt.About.main(About.java:81)

IDoc - Custom segments added?

Hi,
I am new to IDOC and working on Sales Order BOM inbound interface. Using BOMORD01 Idoc and filling E1STZUM, E1KDSTM and E1STPON segments. Getting a message saying "Segment cannot be identified" (ZE1FIKP) and also "Custom segments added" but actually my intention is not to add any custom segments, why I am getting this message and how to correct it.
Thanks in advance.
Regards,
Balaji Viswanath.

Hi,
Just For your understanding...
There are basically two types of IDOCs.
Basic IDOCs
Extended IDOCs
Idoc Components
Basic Idoc
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extension Idoc
Extending the functionality by adding more segments to existing Basic IDOCs.
Creation of IDoc
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
create IDOC Type
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
for futher info check the below links
http://www.allsaplinks.com/idoc_sample.html
http://www.allsaplinks.com/
http://www.sap-img.com/
http://www.sappoint.com/abap.html
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
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://expertanswercenter.techtarget.com/eac/knowledgebaseCategory/0,295197,sid63_tax296858_idx0_off50,00.html
http://sap.ittoolbox.com/documents/popular-q-and-a/extending-a-basic-idoc-type-2358
http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b7eee43d711d1893e0000e8323c4f/frameset.htm
<b>if u find it useful plz mark the points</b>

Custom segments to HRMD_A

Hi,
I am using the HRMD_A message type and it does not contain certain infotypes part of its schema for ex infotype 77, so we extended the IDOC HRMD_A07 and added few fields from infotype 77. Using SCDO tcode we created a custom change document for table PA0077 and using tcode BD52 we included the fields from the table PA0077 which were added to the extended segment. In the user exit which gets triggered when infotype 77 is udpdated we are writing it to the change documents now my question is how will the custom segment ZP0077 get updated when there is a change in the infotype 77 data. Do we have to write a custom code to populate the custom segments , if we need to then how can we retreive the latest data, populate the custom segments and in which user exit does it have to go. We have written some logic to popuate some other custom segments in the following user exits, do we have to use one of them.
EXIT_SAPLRHA0_001
EXIT_SAPLRHA0_002
EXIT_SAPLRHA0_003
EXIT_SAPLRHA0_004
EXIT_SAPLRHA0_005
EXIT_SAPLRHA0_006
EXIT_SAPLRHAL_001
EXIT_SAPLRHAL_002
EXIT_SAPLRHAL_003
EXIT_SAPLRHAL_004
All inputs will be appreciated and rewarded suitably.
Thanks
Vick
FYI: This is a duplicate thread, I will make sure that i delete the other thread

Hi,
With change documents an event might be triggered check tcode
swels and switch on event trace
now change the infotype (assuming you have attached/activated change documents)
go to tcode swel and execute to see if any event is triggered.
now you can call the workflow and in the workflow in the business object put the code necessary for fetching the data and call pfal or other tcodes u using to export data.
Regards,
Divya

User exit to populate data

Hii ,
I have to send IDOC ORDERS05 to be extended to add custom fields and code an appropriate user exit . Is there any user exit to populate data ??
They have told me to use RSEOUT00 program to send the orders05 idoc . My main concern is which user exit will I use to populate data ??what are the basic steps to populate data and send the idoc Please let me know .
Thank you

Hi,
Please note that user exits provided in the function module IDOC_OUTPUT_ORDERS.
Use T/Code SE80 and explore function group "XVED". This will give you all the user exit functions in IDOC_OUTPUT_ORDERS.
You can write your code in Zinclude programs .
Ex: ZXVEDU03
CASE SEGMENT-SEGNAM.
    WHEN 'E1EDK01'.
      CLEAR: WK_PLANT, WK_EQUNR, WK_BNDDT,WI_WERKS.
      CLEAR: WK_PLANT_DONE, WK_PRICE_DONE, WK_EQUNR_DONE, WK_BNDDT_DONE.
      CLEAR: WK_BAAN_LINE_PRICE_DONE.
      CLEAR: WK_BAAN_HEAD_PRICE_DONE.
      PRICING_CTR = 3.
    WHEN 'E1EDK14'.
      MOVE SEGMENT-SDATA TO E1EDK14.
      PERFORM Z_EXIT_E1EDK14.
    WHEN 'E1EDP19'.
      XVBAP = DXVBAP.
      MOVE SEGMENT-SDATA TO E1EDP19.
      PERFORM Z_EXIT_E1EDP19.
      DXVBAP = XVBAP.
and soon....

In exit EXIT_SAPLKD01_001 populate custom segment of idoc ext. cremas05

Similar Messages

Maybe you are looking for