Reading Custom IDOC from xMII

Hi all,
I'm trying to read a custom IDOC coming from ECC system, with no result. I'm able to read standard IDOC but it seems there are some kind of limitations reading custom IDOC.
IDOC on the ECC side are setted up in the same way, but when I send the IDOC in a Z transaction from ECC the IDOC is not visibile both in the xMII Message Monitor and in the xMII Messages Without Rules.
Do you have any idea?
Thanks.
Regards,
Roberto

Roberto,
This has come up several times in the last year or so. So far in my memory, that problem always turned out to be some configuration setting with the custom IDoc. Do a search on IDoc or custom going back a year (maybe more) to see the issue others found when experiencing problems with custom IDocs.
Regards,
Mike

Similar Messages

Send IDOC from XMII to SAP

Hi All,
I want to send an IDOC from xMII to SAP. Can anyone suggest me the steps and how to configure in SAP and xMII.
thanks
Manoja

Hi,
What ever Dipankar Saha said is correct.
SAP xMII is used for the purpose of connecting ERP and shop floor.
Usually from R/3 system, you can get info in the form of idoc.(through other forms also you can get data. I hope that you have got the data through idoc)
From shop floor, you get data in the form of B2MML.
If you want some data back to ERP, you can use JCO interface present in the
business logic editor. Use this, to find correct BAPI which can push some data into ERP.
Link the data from B2MML field to BAPI field.
Save this transaction and call this where you want.
Hope this may help you...
Regards,
P.S.Kishore kumar

Read idoc from archive in program

Hi All,
I want to read the idoc from the archive in the program.
Please suggest the possible options.
we can read the idoc present in the R/3 database using the FM idoc_read_completely.
But how to read the same from the archive. I can view the idoc from the t-code we10.
Thanks in Advance.
Ankit Gupta

Thanks buddy.
I will try this in my code. Look like it will solve my problem.
But now I have another question. Should I start new thread or can post in the same thread.
Archive infostructure SAP_IDOC_001 is not active in my system. what is the procedure to do it and also it should link to the existing Archive file also.
Regards,
Ankit

Create IDOCs from DMEE Files

Hi SDN,
Can I create Custom IDOCs from the DMEE file format.
The file is getting downloaded after the DMEE Run in a specific format individual to every company code.
I want to generate IDOCs for every DMEE Run.
Thanks,
Manu

Take a look at this :
http://www.sappoint.com/ppt/idoc.ppt
you need to create File port in Tr.WE21 , as file port
Then you have to sechdule the program RSEout00 to collect Idocs .
You can test it in Tr.WE19 , you can also use the Tr.BD87 to see your Idoc status
Hope thisll give you idea!!
<b>P.S award the points.</b>
Good luck
Thanks
Saquib Khan
"Some are wise and some are otherwise"

Regarding Creation of Custom IDOC

Hi,
This is Abdullah Shaik. I want to create an IDOC from the existing IDOC. Some times I need to add some segments to the existing IDOC. Can anybody plz let me know the process how to create the Customized IDOC from the Standard IDOC?
Thanks & Regards,
Abdullah shaik.

Hi Abdullah,
There are basically two types of IDOCs:-
Basic IDOCs and Extended IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
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
Go thro' this link:-
http://help.sap.com/saphelp_46c/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
I hope this provides you a solution.
Regards.
Praveen

Regarding ALE/IDOC in XMII

Can anyone explain me the procedure of using ALE/IDOC in xMII

Hi,
In xMII we don't have IDOC system,we can not send IDOC directly.
We can receive IDOCS in xMII sent from SAP using IDOC Listner.
If you want some data back to ERP, you can use JCO interface.
Use this, to find correct BAPI which can push some data into ERP.
And have a look at this thread
Re: send IDOC from XMII to SAP
Vijaya

[NIO] custom messages from the netwerk

Hi you all,
Yes this is another NIO question :)
Ok I have the following situation, I've got a NIO server which reads custom messages from the netwerk. These messages consists of an interger and then a variable byte array.
int -> length of the message
byte array -> data of message (could be anything)
On my local network it works fine because I don't have to worry about my read() not reading all the bytes the client send. So I can just use the ByteBuffer.getInt() to read the int and create a buffer for the byte array etc.
But... on the intenet there is no garentee all the bytes are read. So if only the first 3 bytes of the whole message are in my read buffer and I call the getInt() I'll get an exception.
How would you fix this? The only garentee is that I will always have 1 byte (except when a connection is closed or other error)
I could create of small bytebuffer of 4 bytes and wait till it's full and then read the int, but what if I also have a length that can consist out of like 5 or 6 bytes... and I don't know by forehand if it's 4 or 5 or 6... or just 2...
Any idear would be welcome... or even code if you have the time...
Grtz
David

Use ByteBuffer[] { lengthField, dataField } as a structure for messages. Set the size of the length field statically as part of the protocol. Set dataField's limit to 0. Do readsinto this structure (there is an appropriate read method for an array of ByteBuffers) until there lengthField.remaining() == 0. At this point, read the int/long/whatever from lengthField and set dataField's limit to that. Then do the reads necessary until dataField.remaining() == 0. At this point, you'll have your whole message.
The reason that I say "do reads" is that on any particular read you may only get one byte's worth of data. Therefore you have to hold this partially completed message in some variable, or as an attachment to the SelectionKey which was selected. As the Channel continually gets selected for OP_READ, you can do the above steps, and if there's not enough left in the channel, you just leave the message partially completed for the next OP_READ. Once it's complete, you do what you need to with it, and replace the attachment or variable with an empty ByteBuffer[] of the above format.
--Dan

Creating IDoc from DMEE File Format

Hi SDN,
Can I create Custom IDOCs from the DMEE file format.
The file is getting downloaded after the DMEE Run in a specific format individual to every company code.
I want to generate IDOCs for every DMEE Run.
Thanks,
Manu

Hi,
your problem is just like filling the segements using the data in other segements. that means if you have knowledge of enhancing the idoc and populating the enhanced segments then in the same way you can populate the BATCH segment also.
you just go to the function module which will be creating the idoc(if its outbound) / function module which will be posting the idoc which is for inblund and then find the perform where it fills the segments ( it will be the one which you will use to fill the segment BATCH )and go that and at last of form you will find one customer function which you can use to fill the BATCH segment.
i think this will help u,
Regards,
Ravi

CUSTOM IDOCS

HI ALL,
I WANT TO SEND A CUSTOM IDOC FROM ONE SYSTEM [ONE SERVER ] TO ANOTHER [ANOTHER SERVER ]. GIVE THE PROCEDURE.
ANY HELP WILL BE HIGHLY APPRECIATED.
WITH REGARDS,
SURESH.A

Hi,
this is one way comunication..
create rfc destination ,from A to B in sm59,
create port this rfc.
ALE IDOC
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
1) System Name : ERP000
Description : Sending System
2) System Name : ERP800
Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
Client : ERP 000
City :
Logical System
Currency
Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
3)
Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
5) Goto Tcode BD64
seelct the modelview
goto >edit>modelview-->distribute
press ok & Press enter
6)goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
7)goto Tcode : BD11 for Material Receiving
Material : mat_001
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
I know how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
<b>Reward points</b>
Regards

Is it possible to read Idocs from SAP R/3 System?

Is it possible to read Idocs from SAP R/3 System? Instead of the aRFC

Unless Hydra emulates ECC sending IDOCS, then you just might want to use the WSMessageListener (http://help.sap.com/saphelp_xmii120/helpdata/en/45/6a86ac88130dece10000000a11466f/frameset.htm) and configure your message processing rules accordingly.

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)

Sender / Receiver on DEBMAS customer IDOCs mapped from XI

Hello XI experts,
I'm hoping you can help me resolve a question.
In our system, customers are maintained in an AFS ERP system. They are then distributed to MDM, via XI, using DEBMDM messages.
We have a second (Retail) ERP system that also needs the customer data. An XI colleague has created a mapping, so that the DEBMDM IDOC from AFS is mapped to DEBMAS and ADRMAS IDOCs, which are sent to AFS.
Functionally this works fine: the customer data from AFS goes to both MDM and retail as expected.
The question is on the IDOCs arriving in Retail. They have the same logical system for the Sender and Receiver, which is the Retail logical system. So it looks like the IDOCs have been created in Retail and then processed, rather than being created in XI. However in XI, in transaction IDX5, we can see IDOC numbers. I'm a developer with no XI experience, so I may be misunderstanding how XI works.
- Does XI actually create an IDOC locally and then send it out?
- Or would XI be calling some kind of RFC in my Retail system to build the IDOC there?
- If the IDOC is built locally, can anyone suggest why I am getting the sending partner to be the same as the receiver?
Even if the sending and receiving systems are set in the XI mapping, the values still get overwritten with the Retail logical system.
Many thanks, Roger

Roger,
In the Receiver IDoc Adapter , 3 options are available.
Apply Cntrol Record Values From payload.
When you select this option, the values of these fields are filledfrom the idoc payload,
+MESCOD
· MESCFT
· TEST
· EXPRSS
· STD
· STDVRS
· STDMES
· SNDSAD
· SNDLAD
· RCVSAD
· RCVLAD
· REFINT
· REFGRP
· REFMES
· STATUS
· DIRECT
· OUTMOD
· CREDAT
· CRETIM+
Take Sender From Payload
Selecting this fills the values for Sender System with values of SNDPRN and SNDPRT.
Take receiver from payload
Receiver Partner Names values are filled from the payload with values of RCVPRN and RCVPRT.
These are the only values from which you can pass the value from payload, rest of the fields are filled by default.
More,
http://help.sap.com/saphelp_nw2004s/helpdata/en/13/95244269625633e10000000a155106/content.htm
Regards
Bhavesh

Need help- need to read a customer table from the payroll schema

Hi gurus,
I need to read an amonunt from a customer table in the payroll schema. Is it possible to input TABLE XXXX in the schema, or is impossible to read from a customer table?Do I need to create a report to upload the amount in an infotype?
Thanks in advanced for for support!

You should create your own custom operation (based on operation TABLE) to read your custom table from a Payroll PCR.
If your custom table's name is longer than 5 characters, you may be required to use operations VAOFF and/or VALEN prior to your custom operation in the PCR.

PLEASE READ - Awful Customer Service from both Sky and BT

For several weeks or more my broadband connection has been dropping off completely literally whenever it wants. There is no pattern, specific times or any clues as to why it does this whatsoever. We first moved to the area I currently live in back in November'14 and there had been a couple of issues in the area causing broadband to go down. So we assumed the connection dropping was because of similar issues but it just kept happening so enough was enough, time to call sky. So the teach advisor does a line test which comes back fine and confirms the connection has dropped many times by looking at the history just as I said. They then do a 24 hour line test where they were supposed to call me back with the results, you guessed right....they didn't. So of course I was back on the phone to them, they confirmed the connection coming into the home was perfect. They then ask a number of standard questions regarding the setup and connection socket. We established the connection socket was an old one and 'not' a test connection socket. The advisor then tells me their booking a BT Openreach Engineer because the socket will need changing for the Sky Engineer to test the connection. I also asked "Do you think it could be the router", the advsor replied "I wouldn't put my money on it". This was great of course, already onto fixing it I thought. So the day of the appointment comes and low and behold it's a SKY Engineer at the door NOT a BT Engineer even after establishing over the phone he wouldn't be able to test the connection because of the old socket. He knew nothing about the issue & my perfect working router was changed to a brand new one along with the microfilter etc, which was fair enough because I ended up with a new one. Amusingly I couldn't keep my old one as a back up....jobsworth, this was of course SKY guessing & hoping it would resolve the issue even if it is the first thing to do they were wasting my time because they 'knew' the connection socket wasn't a test one. He said if it still continues then to call SKY and tell them a BT Engineeer will need to fit a Test Connection socket as we knew anyway. IMO this was unbelievable because regardless of this being their procedure I was given the wrong advice from a so called proffesional Tech advisor and they could have sent a new router in the post as well as booking a BT Engineer = waste of my time. I finally got an appointment with a BT Line Engineer who turned up knowing nothing about the issue, he did a copper wire test and it come back perfect, he said he's never seen a connection so fast. The Exchange is literally around the corner hence the connection is so fast. He said as the copper wire test was perfect that's him done now but he will change the connection socket to a test one. Whilst fitting it he said it could be the socket as it's old & the connection might not be filtering through properly. Once fitted it dropped & connected again 5 times or more in front of his very eyes, nothing more he could personally do. When the line engineer was originally booked Sky's advisor also booked a call from their technical support (higher up) to call me in the afternoon after the engineer had been to see if had been fixed etc. I confirmed the connection had dropped after the new socket was fitted so this completely rules that out. Due to the history of the connection dropping before my original call, Sky's checks and a new socket of course it's time to book a Broadband Engineer. So the lady says "we've established there is no problems within the home so it must be between the home and the exchange so the last thing to do is book a BT broadband enginner". She says "I'll put you on hold a minute whilst I see what appointments we can get". To me astonishement she says they need to collect some more data and will call back in the morning at 9:30am. So she calls me back and says they are not going to book an enginner because I have been connected for more than 16 hours now. Well that nearly made me choke in disgust and shock simply because their log history of the connection dropping confirms I have gone much longer connected. Not just that but it dropped 5+ times after the new socket was fitted and in front of the enginner that changed it. So if that isn't an advisor not giving a dam about the customer and attempting to save SKY money I dream that just happened. As you can imagine I told her what a joke that was and hung up the phone, absolutely ridiculous and I am sure the majority of SKY employees would agree. The next day just as I knew it would the connection started dropping again as & when it likes, random as usual. So they actually book a BT Boradband Engineer this time, finally. So the engineer arives once again knowing nothing about the job making him the 3rd person to arrive in the dark about the job. He believed the problem was SKY trying to speed up everyone's broadband for a number of months now even if there was only a meg in it. Because of this apparently my dsl noise-margin was set at 3 and that was too low. So after discussing noise margins with me he went back to the exchange, called SKY who agreed 3 was too low and changed it to 6. He called back and advised me it should be OK now and to give it 10 days for the line to settle. Rather than running at a fragile 24meg it would be a steady 16 now he said, which I could cope with as long as it didn't keep dropping off. Later that day my connection starts dropping again and I knew full well this has nothing to do with allowing the line to settle. So the SKY advisor goes through the notes that the engineer had made, he mentioned everything we spoke about apart from something that shocked me. He has put down that he couldn't do an Earth *something* test because there was young children about. To my amazement not once did he mention that and if he had my partner could have took them upstairs. However that was that and another Broadband Engineer was booked. He turns up making him the 4th person that knows nothing about the job so after expaining the issue he seems very enthusiastic about the job itself so that was confident. After doing the same tests as the 1st 'broadband' engineer he can't find any issues either, so he climbs the pole 50 metres away from the house. He took it apart, cleared a bit of corrosion but nothing unusual. Then he tells me he'll get SKY to monitor the conection, he has another job to go to annd he'll call back at 3. It got to 5pm and still no call or knock at the door so I called SKY who's customer solutions contact BT who say the the issue has been put down as 'resolved'. I confirmed my connection hadn't dropped since so I left it at that. Because I wasn't at all confident it was fixed it was fixed I kept joking with my partner by saying "Resolved" every so often because of the engineer not calling back and the stress it has caused. Surprise, surprise, the connection drops again the same evening at just gone 7pm (Saturday) so I am straight back on the phone to SKY. Having to explain everything again he puts me on hold to discuss it with a colleague. They put all the notes from every case into a new one as previous one's have been closed as the engineer's claimed 'reolved' when obviously it wasn't. He explained that it is being 'Viper' escalated now as a complaint to BT because they have given 2 frontline Engineers to rectify the problem & they haven't. So they booked a more 'senior' engineer to come out. SKY advised he will be given all the notes from the case & when they get confirmation of the appointment they receive a reference. SKY then contact BT with that reference and explain everything verbally as well. Whilst booking the appointment & speaking with me the broadband connection goes and so the does the landline so we get cut off. This happens everytime they book and engineer. and 2/5 advisors haven't bothered calling me back to contine the conversation, this guy was the 2nd NOT to call me back. The day of the appointment arrives and because I wasn't called back & received no confirmation I call SKY to confirm who do just that. I decided to discuss more discount with this advisor because I had only previously received a small amount because BT Engineers keep putting the case down as resolved. On the Saturday the advisor offensively offered 65p because he does as the computer tells him....pat on the back for him. Thankfully the lady advisor this time was more understanding and applied £20 which was at least something. She also said she would speak with her manager and call be back in the morning with some offers as an apolgy because the enginner would have been out and fixed the issue by then. I was also advised it's the last thing that could try as he is a 'senior engineer'. The so called 'Senior' BT Broadband Engineer arrives and regardless of what SKY told me about it being 'Viper' or 'Hyper' escalated he was also pretty much in the dark. Well as you can imagine that is just the icing on the cake, lost for words. Anyway, he does his tests & says "Sounds like all they've done so far is climb a pole". So he climbs the pole & replaces the cable from the pole to the exchange still confirming everything is fine. There is nothing more he can do and says I will need to call them if it happens again and say "What do you want to do"....shocking to the least. He put in his notes/suggestions to SKY; should it happen again, replace the equipment at the exchange or book another type of engineer. I NEVER got a all back the following morning from the advisor that said she would call back with offers even though she said "I always make my call backs"..........looks that way. Of course the connection drops once again, this time when I call & after having to explain literally everything again I get put through to 2nd tier techincal support (something like that). The lady explains that she needs to book a BT REIN Engineer, this was definitely what she said as I asked how it was spelt and since googled it too for an understanding. She said she would normally take my case on because of everything I have gone through & it would mean not having to explain it everytime but she is going on holiday and not back until September. She apologised a number of times on behalf of SKY and arranged a call back on 6th September (I think) to discount me further as an apology. So apparently the REIN Engineer is booked, she told me to unscrew the connection socked and plug the microfiliter directly into the test part of the socket. Whilst she's putting the appointment through the landline goes off which we were taling on as well as the broadband connection going off. When she called back she assumed I was doing the connection socket whilst on the phone to her. Absolutely not, so I explaine that evertime an appointment is booked with BT this happens. A previous advisor told me that BT does and automatic line test upon booking which is why the landline & broadband drop. She was absolutely adament that this shouldn't happen but that was that & the appointment booked. The Engineer turned up and would you believe it wasn't until I started chatting with him and he'd already started tests that he realised I was expecting a REIN Engineer. He then told me that SKY cannot raise a REIN Engineer they have to (Broadband Engineers) & there's only 2 in the whole of North *my area*. Well again, what do you do but laugh or cry?, I went for the laugh where my blood was boiling. He also said that there is no 'Senior' engineer as such and also said "If he put in his notes about changing the equipment at the exchange, why didn't here"....exactly. So the Broadband Engineer goes back to the exhange calls SKY who allow him to change the equipment & calls me back advising it's all up & running. I aksed "If it happens again is there anyone I can call directly", he replies; "I don't know, we have a number specifically for BT and I just spoke to someone called Chris who doesn't think it's REIN *Facepalm* . This BT Engineer actually did his job properly but for SKY to say "I don't think it REIN after all that is well......lost for words. If I have missed anything out of all this mess I guarantee if it's not incorrect spellings & grammat it's just more awful, awful customer service from both BT & SKY whom are business patners lol. So SKY.....Is the Issue fixed?What was it?Where's my further discount?What offers you got as an apology? bear in mind I already pay around £80 per month for everything after call charges. So after this shambles I hope it's FREE. Oh and what are the odds on someone calling me? because evertime I get through it's luck of the draw & most of the time it's BAD LUCK. Although I have already spent literally hours on the phone to you I am glad I have got this on the net now as it will know become common knowledge. I have also kept a personal copy in case the Thread is removed. Regards.

Thanks for the info and of course the understanding, althought I am sure someone official browses it now & again my main aim was to get this out there. I had an issue a while ago with EA sports regarding their FIFA 15 game, to cut along story short I was incorrectly banned from their servers for apparently botting so I couldn't play online. Their customer service was diabolical, pretty much on par with this. After some research I found out they were the voted the worse company in the states so that said it all. After being passed from advisor to supervisor to manager and back again everything fell on death ears. So through Google I found as many sites & email addresses as possible and posted/sent my argument. It got as far as the EA president where it was all sorted and I was heavily compensated. If I hadn't of done that though I'd still be banned from their servers. Will do exactly the same with this case, as everthing goes throught to someone as SKY in the UK it should be a dam sight easier than getting a reply from EA Canada etc.

Error while Reading Idocs from ECC 6.0 to Sun IDM .

Hi Gurus,
We have a scenerio where we have to update the Sun IDM Server with all the changes in HR Data happening in ECC.
For that... we have
1. Created a Logical System for Sun IDM server, Port, RFC Connection (TCP/IP).
2. Assigned Partner Profiles, Distribution Model etc. for msg. type HRMD_A ;
3. We have created a Communications User used by the IDM server to connect to ECC.
Idocs are created daily and are in status 03 - Data passed to Port OK !
and on the In Sun Identity manager 8.0 we have created SAP resource adapter for ECC 6.0,
after giving resource parameters our test connection is successful.
We also changed edit synchronisation policy for the same but when we start synchronisation in IDM, it is unable to read any idocs although Idocs are generated in SAP .
Log file gives the message as "Incoming IDoc list request containing 0 documents"
We also have one more error ;
some times while doing a connection test : JCO.Server could not find server function 'åäåä¹'
while most of the times the connection is successful.
Please suggest .

Hi Gurus,
The error got resolved .
The changes in the settings i did :
SAP SIDE : Made the RFC Connection Unicode.
IDM SIDE : Checked on the "SAP Server Unicode" checkbox; while doing the HR Activ Synch Settings.
This Resolved the error.
regards
Vaibhav

Reading Custom IDOC from xMII

Similar Messages

Maybe you are looking for