Conversion Error in Inbound Idoc

Hi team,
I have a file with Chinese characters on them. Running the program RSEINB00 results to a conversion error. After debugging, I found out that the error was caused by these Chinese characters. I am already logged in 'ZF' language. Is there something that I need to check or do so that the system will accept these characters?
Thanks so much.

Hi amythiel,
The above has nothing to do with the conversion exits, If you are sure it is because of chinese characters then confirm if you are running on a Unicode system or a non unicode system. If it is a non unicode system, then change the code page(8300, 8304 etc) on the file port to accommodate for Chinese characters.
The other reason could be that the release version of the IDOC are different between source and the target system, you can check this by using tcode WE82 on both the systems.
Regards,
Chen

Similar Messages

Error in Inbound Idoc trigering Workflow Scenario

I am getting below Error while I am posting Z Inbound IDOC in production system.
Please tell me what is getting wrong and how to correct.
Work item 000000000000 cannot be read
Message no. WL803
Diagnosis
The work item with the specified ID can either not be read completely or partly (for example, its container).
System Response
The action was cancelled and the work item, if it still exists, set to error status.
Procedure
Check whether the work item has already been deleted or whether only parts of it can no longer be read.
In the latter case, the work item is inconsistent.
Refer to your workflow system administrator.
Points will be surely given to helpful answers.
Regards
Edited by: Tushar Mundlik on Feb 12, 2008 8:15 AM

Hi Krishna,
First we have to find out if the error comes from processing in the application or from one of the checks performed before the application is called.
Go to function module IDOC_INPUT_OPDERS and put a breakpoint on "PERFORM edi_mode_to_mem.". Then reprocess the Idoc and when the program stops at your breakpoint set INPUT_METHOD to 'A'. In this way your order will be processed online (using BDC and you can find the error).
If the program doesn't stop at your breakpoint the error comes from one of the checks before.
But please try this first and come back if this doesn't solve your problem.
Kind regards,
John.

Serialization error in inbound idoc

Hi Friends
Am getting inbound idocs with this error : Serialization errror for object 01,S, 34343434,Expected counter 000001<
and error in details says,
The expected serialization counter has the value 000001. However, the serialization counter in the IDoc has the value 000002 and is therefore too big. There are therefore older IDocs with this HR object with the serialization counter values in between. These IDocs have either not yet been posted, or have been posted incorrectly.
Intrested Part is   i put check ( Selected ) on as per client suggestion in ,
IMG -> Sap Netweaver -> Application server ->Idoc Interface / Application Link Enabling (ALE ) -> Modelling and imple Business process -> Configure Predefine ALE Business Process -> Human Resource -> Master data Distribution ->Serialize HR Master Data -> ( Serialize HR Master data in ALE inbound processing ) ...   settings and i was getting this error but when i take back this check ( unselect ) flag   idoc posted successfully    Now am confuse i shd keep this or not because am getting data from diff countries also.
what shd i do for this few expert said i need to do some thing for Serialization so automatically system shd take care for this,
Need your support on this .
Regards
Meeta

I have been working with IDocs in a serilization-active HR-ALE system and have learned a few things along the way ....
- Serialization must be active in both sending/originating and receiving/destination systems. (Turn on flag in customizing, as you have already done).
- Both systems maintain a registry of HR objects that includes in each record the object type, object id, and serial counter. The serial counter is increased by one in the sending system every time the object is sent via ALE and increased by one when the object is correctly processed in the receiving system. The serial counter is passed in the E1PLOGI record of each object in the IDoc.
- When a similar serialization error is received (where the counter received is lower than the expected counter), the error message gives a little more detail:   "Decide what to do based on your own particular situation. Responses could range from ignoring or editing the IDoc, to manually adjusting the serialization counter in the registry of the receiving system to the expected value."
Options are therefore:
- Edit IDoc - can use IDoc test tool (WE19) to create and edit a copy for processing.
- Use transaction RE_RHALE_HRMDRGIN to maintain the serial counters
- Use transaction RE_RHALE_RGIN2IDOC to adjust the serial counters for the offending IDoc
I strongly recommend, however, that you take some time to further understand the serialization process before updating the counters manually. If you've turned on, then off, then on the serialization flag(s) through customizing, you might consider initializing the serial counters in both sending and receiving systems and starting from scratch.

Error in Inbound IDoc processing

Hi all,
While processing Inbound delivery IDocs(Status 64), we are getting an error "Cannot convert Dimensionless Units".
Please help.
Regards,
SP.

Hi Vijay,
The IDoc is a Delivery IDoc. The OSS Note that you have sent is for a similar error but is related to APO systems and hence I don't think it is related.
Has anyone encountered this error before...?
It says 'Conversion of dimensionless units is not possible'....
Regards,
SP.

ERROR IN INBOUND IDOC

Hi Expert ,
while i am prcoess a custom idoc ,
i am getting the following error
status no :53
Error Msg : Application document not Posted ,
( No status record was passed to ALE by the application )
data is comingin the receiving end ,pls help to solve the problem
points will be given to the solutions
thanks and regards
Renjith MP

Hi ...
In WE19, Give the IDOC number & execute ... then put the cursor on the idoc control record . then click on the Standard Inbound push button on the application tool bar.it will show show all the details like partner no,type , message type , process code & function module name ...
now put a break point in the function module .. & debug .
if u r using customised inbound function module , then click on inbound function module .. there u will get a pop screen with FM name & debugging option in both background & foreground mode...
try & let us know ....
Reward Points if it is Useful.
Thanks,
Manjunath MS

IDOC-XI-Idoc error in inbound idoc

Hi all.
   We have a Idoc-xi-idoc scenario.
   SAP R/3 - Xi - SAP CRM
   We have configure the idoc out in SAP R/3. And I use we19 to test the Orders Idoc and check the staus is ok.
   But in XI, I cannot see the Orders Idoc is sending in. However, this time I havenot configure any repository and directory.
   My question is , if I havenot configure XI repository and directory, how can I check the Idoc in error messages ? How can I know that the SAP R/3 idoc is sending to XI correctly ?

Hi Jianhong,
plz check SM58 at R/3. Assumedly the IDoc was refused by XI - because of missing Configuration in IB Directory.
Regards,
Udo

Conversion error in outbound idoc-

Hi ,
When idoc is generated for payment idoc the idoc is generated successfully ( Idoc status is 30) but when I am processinng the idoc through program RSEOUT00 idoc is getting status 02 and the reason is conversion_error in a segment. Now the segment in which the error is coming has a field having text in chinese character.When I debugged RSEOUT00 I am getting the exception CONVT_CODEPAGE in transfer statement.
Can anyone tell me how to correct this error?
Also when I checked the file port definition in WE21 I found that the unicode format indicator is turned off . What is the significance of this indicator?

> Also when I checked the file port definition in WE21 I found that the unicode format indicator is turned off . What is the significance of this indicator?
Good remark! This indicator is used to create the file in UTF-8 encoding, so it can store all Unicode characters and you won't get any dump. If you don't want to use the Unicode format, then you have to define a replacement character (# by default) so that to avoid the dump.
For more information, you may refer to the ABAP routines WRITE_TO_FILE (which determines the code page if port is non-unicode) and OPEN_FILE (it determines which OPEN DATASET statement is used according to the port attributes) in the include LEDI7F1 (both are called inside IDOCS_OUTPUT_TO_FILE function module).

Error in inbound IDOCS from XI to SAP

Hi,
We have a migrated system XI 20 to 70 (SP9) and we have adapter engine in 620. When a adapter engine in 620 send a xml message to XI for the R3 system , the XI system doesn't converts well the SNDPRN and SNDPRT. In concret the XI set as SNDPRN = SAPSID and as SNDPRT = LOGICALSYSTEM of SAPSID. and we want set in the fields SNDPRN and SNDPRT the values of the payload.
How can we correct this?
it can be a standard error in XI?
Example
Idocinbound
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:IDocOutbound xmlns:SAP="http://sap.com/xi/XI/Message/30">
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>100</SAP:MANDT>
<SAP:DOCREL>700</SAP:DOCREL>
<SAP:DOCNUM>0000000000003016</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>/AFS/ORDERS05</SAP:IDOCTYP>
<SAP:CIMTYP>ZAFSORDERS05</SAP:CIMTYP>
<SAP:MESTYP>ORDERS</SAP:MESTYP>
<SAP:MESCOD />
<SAP:MESFCT />
<SAP:SNDPOR>SAPXSD</SAP:SNDPOR>
<SAP:SNDPRN>ale_sfabs</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:SNDPFC />
<SAP:RCVPOR>SAPST1</SAP:RCVPOR>
<SAP:RCVPRN>ST1CLNT100</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
And the payload
<?xml version="1.0" encoding="UTF-8" ?>
- <_-AFS_-ORDERS05>
- <IDOC BEGIN="1">
- <EDI_DC40 SEGMENT="1">
<TABNAM>EDI_DC40</TABNAM>
<MANDT />
<DOCNUM />
<DOCREL>46C</DOCREL>
<STATUS />
<DIRECT>2</DIRECT>
<OUTMOD />
<EXPRSS />
<TEST />
<IDOCTYP>/AFS/ORDERS05</IDOCTYP>
<CIMTYP>ZAFSORDERS05</CIMTYP>
<MESTYP>ORDERS</MESTYP>
<MESCOD />
<MESFCT />
<STD />
<STDVRS />
<STDMES />
<SNDPOR>0120XI02_4</SNDPOR>
<SNDPRT>LS</SNDPRT>
<SNDPFC />
<SNDPRN>0120XI04</SNDPRN>
See it put
<SAP:SNDPOR>SAPXSD</SAP:SNDPOR>
<SAP:SNDPRN>ale_sfabs</SAP:SNDPRN>
and we want
<SNDPOR>0120XI02_4</SNDPOR>
<SNDPRN>0120XI04</SNDPRN>
Thanks in advanced.

Hi,
our communication channel was migrated from SAP XI 20 and in XO 70 with SP9 we have not the option "Take Sender from Payload" or "ake Receiver from Payload" in the screen only has the option "Queue Processing" and "Apply Control Record Values from Payload"
Take Sender from Payload" and "Take Receiver from Payload" are in the same screen?
Thanks in advanced.

Error in Inbound Idoc ADRMAS03

Hi All,
I'm getting fallowing error message while uploading the Vendor address through   ADRMAS03 IDOC .
Message : No appropriate entry found in table TSADOBJ
Process code i used is BAPI_MDM.
Even though i maintain the values in TSADOBJ table, values that maintained are like this
TSADOBJ-OBJTYPE       = LFA1.
TSADOBJ-ADDR_TYPE = 1.
TSADOBJ-CONTEXT      = 0001.
TSADOBJ-TABLENAME = LFA1.
TSADOBJ-FIELDNAME = ADRNR.
TSADOBJ-TABLE_PERS = ADRC.
TSADOBJ-FIELD_PERS = ADDRNUMBER.
I searched in fourm i could not get any solution.Please help me.

Hi Martin,
What you said is correct, i passed OBJ_TYPE = 'LFA1' and CONTEXT = '0001' to E1ADRMAS, it is asking Account Group, I passed account Group also at this i'm getting error message like this :      Internal error - access to IT_ADR3_L .

Status 51 error for inbound idoc

Dear All,
the error is sales order type 'OR' is blocked. I want to use Order type "ZD10" how can i change it. Please help me.
Thanks in advance

I found at VOE2

Inbound Idoc error

Hi ,
I am getting error in Inbound idoc as follows "CC. .EX.593 does not exist" when i go to BD 87
and process it says "order is not valid for making status changes ".
can some one please guide how to solve this error "CC. .EX.593 does not exist"?
Thanks,
Pradeep.

This is a data problem .Closing it.
Edited by: Pradeep Akula on Jun 15, 2011 7:10 AM

Handling of Error(s) for Inbound IDOCs

Hi Gurus,
I have an requirement where we need to handle and correct the error if inbound IDOC fails. This inbound will be for Account Document posting.
Please let me know how to handle this issue.
Thanks in advance.
Regards,
Gajanan

<b>Hi,
smells like workflow task.
DI Information
Message type
INVOIC
IDOC type
INVOIC01, INVOIC02
X12 transaction set
810
Edifact message type
INVOIC
Workflow in case of error
TS 0000 8056</b>
Executable program
IDOC_INPUT_INVOIC_FI
Regards,
Clemens

How to Identify EDI errors in inbound IDocu0092s?

hi,
I just want to know how to identify EDI errors in inbound IDocs?

Hi
Ref this links
http://www.hibcc.org/EBUS/editemplates.htm
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
/people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
/people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
/people/sravya.talanki2/blog/2005/12/02/manipulating-idoc-control-records-from-payload
/people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
/people/ravikumar.allampallam/blog/2005/02/28/creating-sales-order-through-idoc
With Seeburger we can conver to edi format to XML
seeburger doc
http://www.stylusstudio.com/edi/XML_to_X12.html
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
Details on XI EDI adapter from seeburger
Doc for Conversions-
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
SAP Adapters
EDI with XI
http://www.seeburger.com
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
Thanx
Bommireddy.Sridhar

Problem in Inbound Idoc creation

Hi experts,
My requirement is i want to send purchase order from one system to another system as sales order using ALE and IDOC concept...
I have done configuration settings in both systems..i am using standard message type ORDERS....i am getting outbound IDOC sucessfully...but i am getting error in inbound idoc like Sales organization,distribution channel is not determined for customer 1000 and vendor 1005...
Can anybody tell me how to rectify this?
Thanks & Regards,
Praveena....

Dear praveena,
...salesorganization ..distribution channel ..division not determined for customer 1000...
i think this is because in your inboud system customer is not created in that sales org, distribution channel and division.
Just extend this customer to slaes org, distribution channel and division what appearing in error using XD01, then try.
might be that is the reason.

Status 64 "No filters , No conversion .." when receipt an Inbound Idoc

Hi expert,
I transfers an idoc from client 200 to client 700. At client 200 the outbound idoc is transfer ok but on client 700 when receipt inbound idoc I have status 64 "No filters , No conversion , No version change ." I have writen a FM to process this inbound I think I have this status because I have not true parameter in Tcode we57 we42 but I don't know what parameter on those Tcode. Please help me please!
Thank for reading!
Screen we42 and we57:
http://i612.photobucket.com/albums/tt203/talaai04071986/we57.png
http://i612.photobucket.com/albums/tt203/talaai04071986/we42.png

Hi Reddy,
I can't find any error on my function. Can you find it for me?
This is my code.
FUNCTION Z_IDOC_INPUT_ZRZSO_MTC .
""Local Interface:
*" IMPORTING
*"     VALUE(INPUT_MET) LIKE BDWFAP_PAR-INPUTMETHD
*"     VALUE(MASS_PROCESSING) LIKE BDWFAP_PAR-MASS_PROC
*" EXPORTING
*"     VALUE(WORKFLOW_RESULT) LIKE BDWF_PARAM-RESULT
*"     VALUE(APPLICATION_VARIABLE) LIKE BDWF_PARAM-APPL_VAR
*"     VALUE(IN_UPDATE_TASK) LIKE BDWFAP_PAR-UPDATETASK
*"     VALUE(CALL_TRANSACTION_DONE) LIKE BDWFAP_PAR-CALLTRANS
*" TABLES
*"      IDOC_CONTRL STRUCTURE EDIDC
*"      IDOC_DATA STRUCTURE EDIDD
*"      IDOC_STATUS STRUCTURE BDIDOCSTAT
*"      RETURN_VARIABLES STRUCTURE BDWFRETVAR
*"      SERIALIZATION_INFO STRUCTURE BDI_SER OPTIONAL
*" EXCEPTIONS
*"      WRONG_FUNCTION_CALLED
Include File containing ALE constants
INCLUDE MBDCONWF.
TABLES : ZCUSTOMERS, "Cutomer Header
           ZSOHEADERS, "Sales Header
           ZSOITEMS. "Sales Items
***Data
DATA : W_ZRZSEG1 LIKE ZRZSEG1,
W_ZRZSEG2 LIKE ZRZSEG2,
W_ZRZSEG3 LIKE ZRZSEG3.
DATA : T_ZCUSTOMERS LIKE ZCUSTOMERS OCCURS 0 WITH HEADER LINE.
DATA : T_ZSOHEADERS LIKE ZSOHEADERS OCCURS 0 WITH HEADER LINE.
DATA : T_ZSOITEMS LIKE ZSOITEMS OCCURS 0 WITH HEADER LINE.
WORKFLOW_RESULT = C_WF_RESULT_OK.
LOOP AT IDOC_CONTRL.
    IF IDOC_CONTRL-MESTYP NE 'ZRZSO_MT'.
      RAISE WRONG_FUNCTION_CALLED.
    ENDIF.
Before reading a new entry, clear application buffer
    LOOP AT IDOC_DATA WHERE DOCNUM EQ IDOC_CONTRL-DOCNUM.
      CASE IDOC_DATA-SEGNAM.
        WHEN 'ZRZSEG1'.
          W_ZRZSEG1 = IDOC_DATA-SDATA.
          MOVE-CORRESPONDING W_ZRZSEG1 TO T_ZCUSTOMERS.
          INSERT INTO ZCUSTOMERS VALUES T_ZCUSTOMERS.
        WHEN 'ZRZSEG2'.
          W_ZRZSEG2 = IDOC_DATA-SDATA.
          MOVE-CORRESPONDING W_ZRZSEG2 TO T_ZSOHEADERS.
          INSERT INTO ZSOHEADERS VALUES T_ZSOHEADERS.
        WHEN 'ZRZSEG3'.
          W_ZRZSEG3 = IDOC_DATA-SDATA.
          MOVE-CORRESPONDING W_ZRZSEG3 TO T_ZSOITEMS.
          INSERT INTO ZSOITEMS VALUES T_ZSOITEMS.
      ENDCASE.
    ENDLOOP.
CUSTOMER HEADER *
   SELECT *
   FROM zcustomers.
   ENDSELECT.
   IF sy-subrc NE 0.
     INSERT INTO zcustomers VALUES t_zcustomers.
   ELSE.
      UPDATE ZCUSTOMERS FROM T_ZCUSTOMERS.
   ENDIF.
    IF SY-SUBRC EQ 0.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '53'.
      IDOC_STATUS-MSGTY = 'I'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '004'.
      IDOC_STATUS-MSGV1 = T_ZCUSTOMERS-KUNNR.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
    ELSE.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '51'.
      IDOC_STATUS-MSGTY = 'E'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '005'.
      IDOC_STATUS-MSGV1 = T_ZCUSTOMERS-KUNNR.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
      WORKFLOW_RESULT = C_WF_RESULT_ERROR.
      RETURN_VARIABLES-WF_PARAM = 'Error_Idocs'.
      RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
      APPEND RETURN_VARIABLES.
      CLEAR RETURN_VARIABLES.
    ENDIF.
SALES HEADER *
   SELECT *
   FROM zsoheaders.
   ENDSELECT.
   IF sy-subrc NE 0.
     INSERT INTO zsoheaders VALUES t_zsoheaders.
   ELSE.
      UPDATE ZSOHEADERS FROM T_ZSOHEADERS.
   ENDIF.
    IF SY-SUBRC EQ 0.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '53'.
      IDOC_STATUS-MSGTY = 'I'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '004'.
      IDOC_STATUS-MSGV1 = T_ZSOHEADERS-VBELN.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
    ELSE.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '51'.
      IDOC_STATUS-MSGTY = 'E'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '005'.
      IDOC_STATUS-MSGV1 = T_ZSOHEADERS-VBELN.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
      WORKFLOW_RESULT = C_WF_RESULT_ERROR.
      RETURN_VARIABLES-WF_PARAM = 'Error_Idocs'.
      RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
      APPEND RETURN_VARIABLES.
      CLEAR RETURN_VARIABLES.
    ENDIF.
SALES ITEM *
   SELECT *
   FROM zsoitems.
   ENDSELECT.
   IF sy-subrc NE 0.
     INSERT INTO zsoitems VALUES t_zsoitems.
   ELSE.
      UPDATE ZSOITEMS FROM T_ZSOITEMS.
   ENDIF.
    IF SY-SUBRC EQ 0.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '53'.
      IDOC_STATUS-MSGTY = 'I'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '004'.
      IDOC_STATUS-MSGV1 = T_ZSOITEMS-VBELN.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
    ELSE.
      IDOC_STATUS-DOCNUM = IDOC_CONTRL-DOCNUM.
      IDOC_STATUS-STATUS = '51'.
      IDOC_STATUS-MSGTY = 'E'.
      IDOC_STATUS-MSGID = 'YM'.
      IDOC_STATUS-MSGNO = '005'.
      IDOC_STATUS-MSGV1 = T_ZSOITEMS-VBELN.
      APPEND IDOC_STATUS.
      CLEAR IDOC_STATUS.
      WORKFLOW_RESULT = C_WF_RESULT_ERROR.
      RETURN_VARIABLES-WF_PARAM = 'Error_Idocs'.
      RETURN_VARIABLES-DOC_NUMBER = IDOC_CONTRL-DOCNUM.
      APPEND RETURN_VARIABLES.
      CLEAR RETURN_VARIABLES.
    ENDIF.
ENDLOOP.
ENDFUNCTION.
Edited by: Cuong Nguyen Cao on Jun 2, 2010 6:51 AM

Conversion Error in Inbound Idoc

Similar Messages

Maybe you are looking for