Idocs getting posted as segments

Hi all,
I have a scenario where in there are mutilpe idocs in a message (XI output) but when its getting posted to SAP(r/3) its posting as multiple segments in one idoc instead of multiple idocs.
I would be glad if someone help me in resolving this.
Thanks in Advance.
Regards,
Satish.

HI Pola
Problem is with mapping somewhere.
You have mapped multiple occurring segment to 0.1 target thats the reason it is generated more than once.
Check again.
Thanks
Gaurav

Similar Messages

EDI vendor invoices do not get posted before GRN is posted

Hello All,
The requirement is our vendor sends EDI invoices and they get parked in SAP as IDOCs. IDOC gets posted if GRN exist for a PO.
In purchase order it is GR based IV. If vendor parks invoice and there is no GRN for purchase order then IDOC fails and it goes in status 51 (Error).
Our requirement is, IDOC should get posted even if there is no GRN for a purchase order and client do not want to remove GR based IV tick from PO. After through verification of the parked invoice it gets posted in the system.
We have done the config change in MM>>LIV>>EDI>Enter program parameters, we have maintained value "1" for field "Processing". Inspite of this change system does not process inbound ICOCs and they go in error (51) status.
Please provide solution for this.
Thanks & regards.
Sanjay

Hello Jurgen,
The change in piece of code suggested in SAP note no. 501524 was already implemented in our syste, However still invoice IDOC fails and it goes in error "status 51" as there is no GRN for that purchase order. However if material GRN is made for 1 qty then the invoice gets parked with the full amount even if the GRN is for 1 no.
Please suggest a suitable solution.
Thanks.
Sanjay

File to IDoc scenario-CREMAS not getting posted

Hi Experts,
i am doing a file to idoc scenario in which i am giving the xml file from MDM ,consisting of Vendor Master data and posting the address and the general data into the ADRMAS and CREMAS idocs into the R/3 system.
The problem that i am facing is that the ARMAS is getting posted correctly but the CREMAS is getting posted with the red signal,status 51.It says "Not authorized to change the Vendor Centrally."
Can anyone please tell me what is the reason and the solution for this problem?
Is this a data error or XI error?
Thanks in advance,
Shweta.

Hi Shweta
Status 51, 52 means Posting error
Please check wheteher all the configuration has been done or not
SM59-rfc destination
IDX1-port
IDX2-load metadata
we05-IDoc status records
BD54-Create Partner Number
We20-Create Partner Profile
WE19-Testing IDoc Processing
After That check the solution it is due to Authorization
File to idoc - IDX5 Error
Regards
Abhishek Mahajan
*Please reward points if helpful**

EDI / IDoc : While posting inbound IDocs, IDocs gets into status 56

EDI / IDoc : While posting inbound IDocs, IDocs gets into status 56 with message "EDI: Sender port in control record is invalid".
But if I reprocess the same idoc without doing any changes using RBDINPUT and select radio button to processs idocs for status 56, then it gets successfully posted.
So not getting why this stucks for the first time.
Thanks in Advance..........

i fixed this my self

IDoc - Get Segment Definition or Version in Code

I'm working on the ABAP-PI Port, created a FM based on FM OWN_FUNCTION now.
In my FM, there is a call to a function
CALL FUNCTION 'EDI_SEGMENTS_GET_ALL'
that retrieves all the segment data for a particular IDoc number.
However, it returns only the segment name EDIDD-SEGNAM and not the segment definition.
Example:
Value returned: "E1EDKA1" ( EDIDD-SEGNAM , 27 char long field)
I'm actually looking for the Segment Definition that goes up to 30 characters long.
Value I need to be returned: "E2EDKA1001" - has the extra 3 digits at the end that represents the Version.
If you go to WEDI, Development > IDoc Segments, You can see that the Segment definitions belong to a data type EDISEGDEF (30 characters long).
Does anyone know how I can get this programmatically?
The IDoc file downloaded by the FILE port stores the 30 char Segment Definition in the file
Using the ABAP-PI it only returns the segment name (27 char)

Hi all,
Thanks for your replies.
EDISDEF might be useful, but I'm not sure how to use it at the moment.
I am supplied in the code a structure of type EDIDC, which has the following values (not all are listed)
MANDT C 3 308
DOCNUM N 16 0000000000002050
DOCREL C 4 640
STATUS C 2 03
DOCTYP C 8
DIRECT C 1 1
RCVPOR C 10 SUBSYSABAP
RCVPRT C 2 B
The above represnets a particular IDoc being processed (see DOCNUM and DOCREL)
The default code then uses a FM to get the segment data based on the DOCNUM.
CALL FUNCTION 'EDI_SEGMENTS_GET_ALL'
 EXPORTING
 DOCUMENT_NUMBER = I_EDIDC-DOCNUM
 TABLES
 IDOC_CONTAINERS = I_EDIDD
 EXCEPTIONS
 DOCUMENT_NUMBER_INVALID = 1
 END_OF_DOCUMENT = 2
 OTHERS = 3.
Does anyone know of any FM that returns a EDID4 (has 30 char segment version) structure instead of a EDIDD structure (27 char seg def)?
And the value EDIDC-DOCREL (SAP Release for IDoc) e.g.
640
does not match up with values available in EDISDEF-RELEASED (IDoc development: Release of segment definition), e.g.
30F
40A
45A

How can I find if the segment definitions are
E2EDKA1 or
E2EDKA1001 or
E2EDKA1002 or
E2EDKA1003

Plz Help:Idoc not getting posted

In my requirement some of the idocs are not getting posted.The error message is "Balance not zero".Idoc type is "INVOIC01".In my requirement they told to look into the standard sap pgm"SAPLMRMC" in that FM MRM_AMOUNT_COMPARISON.Please give me suggestions to proceed.

Hi Hema,
Please check the invoice data that your are trying to send. From the error it seems that the IDoc is failing the data validations that must be placed in the program/FM that is used to generate/post the IDoc.
Regards,
Ashwinee

Idoc not getting posted into XI

Hello Experts,
I am trying IDoc-XI-File senario...
I have configured, ALE on backend system. Configured IDX1 and IDX2 in XI system.
At sender the Idoc has been sent without any errors.
But when I check in XI using SXMB_MONI there are no messages. Idoc is not getting posted into XI.
Please suggest as I am struck at this point. I am using XI 7.0
Thanks
Suma

Hi,
Kindly verify the ALE steps that you have performed...
Steps for ALE settings:-
Steps for XI
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the R3 system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto IDX1.
     Create a new port.
     Give the port name.
     Give the client number for the R3 system.
     Select the created Rfc Destination.
Step 3)
     Goto IDX2
     Create a new Meta data.
     Give the Idoc type.
     Select the created port.
Steps for R3.
Step 1)
     Goto SM59.
     Create new RFC destination of type 3(Abap connection).
     Give a suitable name and description.
     Give the Ip address of the XI system.
     Give the system number.
     Give the gateway host name and gateway service (3300 + system number).
     Go to the logon security tab.
     Give the lang, client, username and password.
     Test connection and remote logon.
Step 2)
     Goto WE21.
     Create a port under transactional RFC.(R3->XI)
     Designate the RFC destination created in prev step.
Step 3)
     Goto SALE.
     Basic settings->Logical Systems->Define logical system.
     Create two logical systems(one for XI and the other for R3)
     Basic settings->Logical Systems->Assign logical system.
     Assign the R3 logical system to respective client.
Step 4)
     Goto WE20.
     Partner type LS.
     Create two partner profile(one for XI the other for R3).
     Give the outbound or inbound message type based on the direction.
Step 5)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
Step 6)
     Goto WE19
     Give the basic type and execute.
     fill in the required fields.
     Goto IDOC->edit control records.
     Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
     Click outbound processing.
Step 7)
     Go to SM58
     if there are any messages then there is some error in execution.
     Goto WE02.
     Check the status of the IDOC.
     Goto WE47.
     TO decode the status code.
BD87 to check the status of IDOC.
In case if not authorized then go to the target system and check in SU53, see for the missing object
and assign it to the user.
SAP r3
sm59(status check)(no message)
WE02(status check)
WE05(status check)
BD87(status check)
Xi
IDx5(Idoc check)
SU53(authorization check)
Reward points if helpful...
PrasHaNt

FI - Interface triggerring multiple idoc is not getting posted

Hi all,
I have a scenerio, where I am receving data from SAP PI, which calls standard idoc ACC_DOCUMENT03 and which posts FI Document.
now, the problem is interface trigger's 2idoc with seperate number with same message type and same idoc type, but both the idoc are not getting posted and show's error like 'No currency line exists for line item 0000000001' and so on.
But the same idoc, when i proccess indivisually get's process gets posted successfully.
I have also done implementation in function module IDOC_INPUT_ACC_DOCUMENT.
As an abaper, I am not able to understand problem to take corrective steps.
Thanks & Regards
shashikant

hi,
if the IDoc is stuck in a qRFC queue means that the message did not reach the pipeline to be send to R3 so, anything in wrong at PI side.
please, go to SMQ2 and check whats happening. to know the queue name check the SXMB_MONI, select the proper message and scroll rightto the proper colum.
let us know.
Rodrigo P-.

Message should get generated in outbound program when idoc is posted in ot

Dear All,
Can anyone please tell me,how i can send response back to the idoc program.
Requirement: Outbound program will generate an idoc and when it gets posted in the other server a message should appear that idoc was posted in other server...
Now can anyone tell me how i can do this,i mean message should get generated in outbound program when idoc is posted in other server..
warm regards
Sajid

hi,
Go through the following thread
iDoc - XI - iDoc with Acknowledgement
Regards
Mudit

Data records in an IDoc getting erased, when conversion rules are defined

Hello ,
We are sending IDocs of message type GLMAST & COELEM from a system(version 4.7) to another system (version 4.6B).
The segment data in the IDocs are changed using the user exit enhancement KKCD0001. The function exits used are EXIT_SAPFKCIM_001 and EXIT_SAPFKCIM_002.
If there is no conversion rule defined in the receiver system, for the segments, the IDocs are posted correctly in the receiving system. But if we define conversion rules , then the data records for all the segments for which conversion rule is defined are getting erased, and an error occurs during processing of IDocs
Please let me know what can be the the reason behind this issue..And how to solve this..
Thanks in advance,
Afsar

Issue solved

CREMDM splitted by PI, ADRMAS gets posted, CREMAS in inbound queue

Hi all,
I am on SAP MDM 7.1 SP03, SAP PI and SAP ECC6.
I have gone thorugh all the threads and Guides related to MDM but couldn't find a valid solution for my problem described below. However, I did find some tricks and tweaking which I dont want to use as they are not recommended by SAP.
We syndicated NEW Vendor records being created in MDM using CREMDM with standard Syndication Map. We have Vendors number generated in MDM and the number range being used exists in ECC and is marked as external. Moreover, the number range uses all of 10 digits, so there is no question of Conversion Routines with it. We deployed PI for splitting CREMDM to ADRMAS and CREMAS. We have serialized ADRMAS to go before CREMAS. We have assured that fields common between these two, have "no data" character i.e. "/" in CREMAS with correct data in ADRMAS. And ADDR_GROUP is mapped as "BP".
Now the problem is, ADRMAS gets posted but CREMAS remains in the inbound queue. The queue running but still CREMAS remains there with CODE as "75". This results in non-creation od Vendor master record as CREMAS is not posted.
Can anybody help with this. I really appreciate the support.

Hi R,
The ALE inbound function modules treat each IDoc segment as a current set of data. Missing fields (or fields that have no data) are interpreted as a value deletion. To keep the existing value for a single field, you have to add a no-data sign as field value for NAME_1. This no-data sign is a single slash (/).
Please execute the inbound function module manually in WE19 to test this. If an exception is seen at NAME_1 ,pass a value or '/' and check for successful posting of Idoc.
If this works, modify inputs to CREMAS accordingly.
In addition a good SAP Note 1052964 - MDM: Distribution of Business Partners, Customers, Vendors for your reference.
Regards,
Vinay M.S

Idoc successfully posted without deleting service line

Dear Team,
I am trying to delete the service line item for multiple service lines throguh Idoc (FM : BAPI_PO_CHANGE) its bit of surprising thata my IDOC is getting posted without any errors but nothing is changing ,however the value is getting changed for single line but not able to delete the service line .
I can able to delete the main line item but not the service line item .Anyone can quickly help on this i am trying since last two days but nothing worked for me .
Also kindly confirm me if is there any SAP note i need to check
Thanks for your support ..
Regards
Kiran Kumar
Please find Below Idoc passing values :
Header -
PO_NUMBER      C00014
DOC_TYPE      CCTC
VENDOR      0000010001
PURCH_ORG      D001
PUR_GROUP      018
CURRENCY      EUR
Header X
PO_NUMBER      X
DOC_TYPE      X
PURCH_ORG      X
PUR_GROUP      X
CURRENCY      X
Item
PO_ITEM      00010
SHORT_TEXT      ITEM 10 CHANGE
PLANT      D001
MATL_GROUP      10341
ITEM_CAT      9
ACCTASSCAT      T
PCKG_NO      0000000035
SRV_BASED_IV      X
Item X
PO_ITEM 00010
PO_ITEMX      X
SHORT_TEXT      X
PLANT      X
MATL_GROUP      X
ITEM_CAT      X
ACCTASSCAT      X
PCKG_NO      X
SRV_BASED_IV      X
PO Account :
PO_ITEM      00010
SERIAL_NO      01
WBS_ELEMENT      D-000015-01-001
RES_DOC      0050000014
RES_ITEM      001
Po Account X :
PO_ITEM      00010
SERIAL_NO      01
PO_ITEMX      X
SERIAL_NOX      X
WBS_ELEMENT      X
RES_DOC      X
RES_ITEM      X
Service line :
PCKG_NO      0000000035
LINE_NO      0000000001
EXT_LINE      0000000010
OUTL_IND      X
SUBPCKG_NO      0000000050
linkage Service line1 :
PCKG_NO      0000000050
LINE_NO      0000000002
EXT_LINE      0000000010
QUANTITY      5.00
BASE_UOM      D
PRICE_UNIT      1
GR_PRICE      5.00
SHORT_TEXT      TEST CHANGE
MATL_GROUP      10341
NET_VALUE      25.00
linkage Service line 2:
PCKG_NO      0000000050
LINE_NO      0000000003
EXT_LINE      0000000020
QUANTITY      5.00
BASE_UOM      D
PRICE_UNIT      1
GR_PRICE      6.00
SHORT_TEXT      TEST CHANGE
MATL_GROUP      10341
NET_VALUE      30.00
Account assignment dist. service line1 :
PCKG_NO      0000000050
LINE_NO      0000000002
SERNO_LINE      01
PERCENTAGE      100.00
SERIAL_NO      01
QUANTITY      5
NET_VALUE      25.00
Account assignment dist. service line2 :
PCKG_NO      0000000050
LINE_NO      0000000003
SERNO_LINE      01
PERCENTAGE      100.00
SERIAL_NO      01
QUANTITY      5
NET_VALUE      30.00
PO results after IDoc posted : Purchase order Item changes screen below
Item Indicator for Service-Based Invoice Verification Changed X BONGAK 01.05.2015 11:20:40 3168 WE19
Item Indicator for Service-Based Invoice Verification Changed X BONGAK 01.05.2015 11:23:12 3169 WE19
Item Purchasing Document Item Change Date Changed 01.05.2015 30.04.2015 BONGAK 01.05.2015 11:20:40 3168 WE19
Item Indicator for Service-Based Invoice Verification Changed X BONGAK 30.04.2015 16:41:02 3154 WE19
Item Indicator for Service-Based Invoice Verification Changed X BONGAK 30.04.2015 16:43:09 3156 WE19
Item Indicator for Service-Based Invoice Verification Changed X BONGAK 30.04.2015 16:49:50 3157 WE19
Item Indicator for Service-Based Invoice Verification Changed X BONGAK 30.04.2015 17:00:19 3159 WE19
Item Indicator for Service-Based Invoice Verification Changed X BONGAK 30.04.2015 17:02:33 3160 WE19
Item Indicator for Service-Based Invoice Verification Changed X BONGAK 30.04.2015 17:37:31 3165 WE19
Item Indicator for Service-Based Invoice Verification Changed X BONGAK 30.04.2015 17:40:29 3166 WE19
Item Purchasing Document Item Change Date Changed 30.04.2015 13.04.2015 BONGAK 30.04.2015 16:41:02 3154 WE19
Item Short Text Changed ITEM 10 CHANGE FS-FND-223 - Fees BONGAK 30.04.2015 16:41:02 3154 WE19

Hi Kiran,
If you are using message type ORDERS then check the qualifier and action which you have used in segments E1EDK01 E1EDK14 also check all your service segments also.
Rgds,
Nayeem.

SOAP to IDocs Scenario...IDocs getting locked at SAP

Dear Experts
We are sending measuring point details to SAP system from 3rd Party. Scenario is working fine for small amount of load. If more number of messages triggered (say 100) IDocs at SAP are getting stuck u201CMeasPoint 10000211 currently locked -> document processing not possibleu201D.
I tried configuring Sender SOAP adapter as EOIO and specified the Queue name as Test Queue. Still IDocs are getting stuck at SAP ECC. Now one more issues messages are getting stuck in queue SMQ2. We can control the flow by using BPM in PI. I donu2019t want to use BPM for this. Can we control this from SAP or using Trigger by background program in Partner profiles?
Please suggest. Thank You.
SAP Error Details:-MeasPoint 10000211 currently locked -> document processing not possible
Message no. IR007
Diagnosis
The object you want to access is locked, either
u2022     By yourself in another session, or
u2022     By another user
u2022     or by the system, which is still processing data for this object
System Response
The system cannot access the object.
Procedure
u2022     If you are locking the object yourself in another session, exit processing in the other session and continue processing in this session.
u2022     If the object is locked by another user, you can
o     contact the other user
o     wait until the other user has finished processing the object
u2022     If the object is locked because the system is still processing its data, wait a while, and then call up the object again.

1. Create a new process code "Z" and check the enque state of the objects before passing back to standard processing modules. Id also change to process immediate as part of this change
or
2. I think assuming RBDAPP01 is still used you may be able to make use of an exit there to do the same thing .. check and wait before processing.
or
3. In message mapping place a UDF that has some kind of wait timer in it (this is random and wont always work cause you wont know when the lock is dropped) but should work.
or
4. Dont use IDOC's create an abap proxy to do the work as a sync process. Processing will need to finish in the proxy and return to the PI stack before the next message is processed in the EOIO queue - this would be the prefered option as far as im concerned, it guarenteed to work and as long as your proxy sticks to the standard rouintes it should be upgrade friendly.
or
5. Use a proxy as above but dont do any processing, just use the proxy to build the IDOC and post it - then check the status of the locks until you are ready then rinse and repeat ..... but like scratching your right ear with your left hand .. but it will work.

Duplicate Outbound IDocs getting Triggered at the same time.

Hi Folks,
I have created custom outbound idoc and done all the configurations required like WE20, WE30, WE31, WE81, WE82, WE 41, WE57 etc.
Also I have written my code to populate segments and then call MASTER_IDOC_DISTRIBUTE in the custom function module which is assigned to the process code and also done the configurations like we57 etc. for the same.
Now when I trigger my output type from VL74 transaction, I noticed two entries in we02 resulting in two IDocs generated for 1 HU.
The difference in two IDocs is the first IDoc getting generated in error with status 29. While the second one as success with status 03.
The data records containing segments have same values for both the IDocs number.
Whether the configuration is a issue here or problem in code of custom fm?
Please help.

Hi Anil,
Appreciate your quick response.
In my custom FM I have populated an internal table it_master_idoc_data with two records of two segments, containing segment name in SEGNAM filed and segment data in SDATA field.
Please let me know whether the data in this internal table of structure EDIDD sufficient for passing to MASTER_IDOC_DISTRIBUTE FM? Or do I need to populate any other field of EDIDD.
Also I am exporting a structure master_idoc_control containing values in this 5 fields.
MESTYP = Z message type, Z IDOCTP, partner and details in RCVPOR, RCVPRN, RCVPRT fields.
I am not populating the internal table communication_idoc_control while calling FM MASTER_IDOC_DISTRIBUTE from my custom function module.
After executing MASTER_IDOC_DISTRIBUTE FM, when the control comes back to my custom FM there is one record in communication_idoc_control internal table with IDoc number in DOCNUM field with status 29(error). Now when we check in WE02 there are two IDocs generated after this transaction's execution.
The first one in error which FM MASTER_IDOC_DISTRIBUTE returns and second one in success with status 03.
Please help....
Thanks,
Pravesh

Not getting payload in segments at SXMB_MONI

Hi,
I am doing scenario HTTP_XI_IDoc.i am sending the payload as thru component monitoring
<?xml version="1.0" encoding="UTF-8"?>
<p2:FICO_DT xmlns:p2="http://igate.com/peoplesoft/peoplesoft_ficoxrpm">
 <PROJID>PROJECT01</PROJID>
 <TASKID>TSK01</TASKID>
 <APPLICATION>SAPCO</APPLICATION>
 <LS>PSFT01</LS>
 <ORGTYPE>COA</ORGTYPE>
 <ORGID>0001</ORGID>
 <ORGCURR>USD</ORGCURR>
 <OBJLINK>100159</OBJLINK>
 <COBJTYPE>IO</COBJTYPE>
 <COBJID1>100159</COBJID1>
 <COBJID2>100159</COBJID2>
 <OBJCURR>USD</OBJCURR>
 <VALTYPE>41</VALTYPE>
 <VERSION>000</VERSION>
 <FISCYEAR>2005</FISCYEAR>
 <COSTCAT>0000415000</COSTCAT>
 <PERIODTYPE>Y</PERIODTYPE>
 <PERIODID>1</PERIODID>
 <PSTRTDATE>20030517</PSTRTDATE>
 <PENDDATE>20050817</PENDDATE>
 <AMTINORGCURR>140000</AMTINORGCURR>
 <AMTINOBJCURR>2580000</AMTINOBJCURR>
</p2:FICO_DT>.
In SXMB_MONI ia m able to see my outbound message as specified above.The thing here is i am not able to see my payload in the segments.it is showing like below.
<?xml version="1.0" encoding="UTF-8" ?>
- <RPMINTF1>
- <IDOC BEGIN="9999">
- <E1PRJTS SEGMENT="9999">
- <E1OBLKS SEGMENT="9999">
- <E1OBKFD SEGMENT="9999">
 <E1PDAMT SEGMENT="9999" />
 </E1OBKFD>
 </E1OBLKS>
</E1PRJTS>
</IDOC>
</RPMINTF1>.
I would like to see message like..
<IDOC BEGIN="9999">
- <E1PRJTS SEGMENT="9999">
 <PROJID>PROJECT01</PROJID>
 <TASKID>TSK01</TASKID>
 <APPLICATION>SAPCO</APPLICATION>
 <LS>PSFT01</LS>
 <ORGTYPE>COA</ORGTYPE>
 <ORGID>0001</ORGID>
 <ORGCURR>USD</ORGCURR>
- <E1OBLKS SEGMENT="9999">
 <OBJLINK>100159</OBJLINK>
 <COBJTYPE>IO</COBJTYPE>
 <COBJID1>100159</COBJID1>
 <COBJID2>100159</COBJID2>
 <OBJCURR>USD</OBJCURR>
- <E1OBKFD SEGMENT="9999">
 <VALTYPE>41</VALTYPE>
 <VERSION>000</VERSION>
 <FISCYEAR>2005</FISCYEAR>
 <COSTCAT>0000415000</COSTCAT>
 <E1PDAMT SEGMENT="9999" />
 <PERIODTYPE>Y</PERIODTYPE>
 <PERIODID>1</PERIODID>
 <PSTRTDATE>20030517</PSTRTDATE>
 <PENDDATE>20050817</PENDDATE>
 <AMTINORGCURR>140000</AMTINORGCURR>
 <AMTINOBJCURR>2580000</AMTINOBJCURR>
 </E1OBKFD>
 </E1OBLKS>
</E1PRJTS>
</IDOC>
Plz tell me where could be the problem.The XI is able to post the IDOC with 51 error in SAP.
The same thing which is specified above is working fine with HCM data.but not working with FI/CO.
Thanks in advance
Sridhar Raju Mahali

Hi Sridhar,
In the 2nd line of the payload check the entry.
You are giving
<?xml version="1.0" encoding="UTF-8"?>
<p2:FICO_DT xmlns:p2="http://igate.com/peoplesoft/peoplesoft_ficoxrpm">
make it
<?xml version="1.0" encoding="UTF-8"?>
<p2:FICO_MT xmlns:p2="http://igate.com/peoplesoft/peoplesoft_ficoxrpm">
Regards,
Vijay

Idocs getting posted as segments

Similar Messages

Maybe you are looking for