IDOC Released Issue

This is for IDOC orders05 ECC 6.00. When I am checking the idoc in We30 . It showing E2EDP19002 as not released But When we generate the IDOC , E2EDP19002 is going . But my problem is with the release version as I am sharing the HTML/DTD files with the MW for mapping purpose .
Could anybody throw the light over this ?
Thanks
Samir .

Hi,
Please check the customization of that IDOC, have u selected Immediate Processing?
Regards,

Similar Messages

HI can anybody   facing IDOC'S ISSUE

HI can anybody   facing IDOC'S ISSUE
SEND IT TO ME
I WILL SOLVE   FOR YOU
THANKS AND REGARDS
RAJU

hi there,
I am trying to load finsta into SAP from the middle ware GXS and all the ports in them looks good when I go to we02 to view the status, it gives error 51. the message says "Error during insert in table FEBKO". There are no more details of this error.
i Tried comparing FEBKO-AZIDT and FEBKO-WVTIM to make sure both are respectively unique
I have deleted this entries from FEBKO by running RFEBKA96 and then we tried to resend/reprocess the IDOC
but still persisting with the same error message 51,
the status on the idoc shud be 0 inorder to process that right.
even when we changed the time why is it giving us the error message 51.
can you put some light on to it please...
points will be assigned.
thanks
Jay

ECC6.0 upgrade issue with IDoc release

Hi experts,
we are in the process of upgrading our ECC environment from 5.0 to 6.0. We have quite a few interfaces which use ORDERS/Invoice Idocs in customised form. In ECC5.0 environment, we had developed a Z segment in the ORDERS Idoc and the segment release was set as 640. Everything worked fine in ECC5.0.
In upgraded environment, SAP has released new version of some segments. one of those is E1EDP01. This segment has 2 new versions in ECC6.0 environment - 007 and 008. This change in the version changes the data in the IDoc and hence interface goes in error at the EDI provider.
We have tried to use 640 as the IDoc segment release in the partner profile of the IDocs. This still gives us an issue because the 007 version of the segment E1EDP01 has release 620 and hence the Idoc picks up 007 version instead of 006 version as desired. When we change the partner profile with Segment release in the IDoc type as 46C, it gives us an issue in the Z segment saying that the IDoc segment is not released in 46C and the Idoc goes in error.
has any one faces such situation in the past? if yes, please throw some light.
Thanks in advance.

Hello,
Iam new to SAP. Thars why i cant understand well to do upgrade,
Then i found out some notes from internet about Upgrade : SAP Note Number 857904 (upgrade from Release 6. To 7.0).
In that notes,
Actually i would like to know about some key words (for example : ASSIGNING, REPLACE, TRANSFER. ) which how to work in the Release 7.0
Always i have some objets in 4.6C.
Ex 01: READ DATASET p_dataset INTO wa_record
Ex 02 : TRANSFER i_crhu TO p_crhd
LOOP AT i_crhd.
*disable controls in crhd
    PERFORM f_disable_crhd.
    TRANSFER i_crhd TO p_crhd.
    IF sy-subrc NE 0.
      MESSAGE a045.        "Error when transfering data to error file
    ENDIF.
ENDLOOP.
CLEAR i_crhd.
CLOSE DATASET p_crhd.
IF sy-subrc NE 0.
    MESSAGE a039.                      "Error at close dataset
ENDIF.
OPEN DATASET v_crhd FOR OUTPUT IN TEXT MODE.
And then i have some FM (ex : WS_UPLOAD , WS_DOWNLOAD)
So I have changed the code for WS_UPLOAD by GUI_UPLOAD
                              and WS_DOWNLOAD by GUI_DOWNLOAD
now my problem is to know about some key word which how to work in ECC6 (for example ASSIGNING, REPLACE, TRANSFER. )
thanks in advance
Rathy

IDOC Monitoring issue - job BPM_DATA_COLLECTION* not running.

Hi all,
We are facing an issue with BPM "IDOC Monitoring" (under application monitoring), which we have setup to monitor Inbound and Outbound Idocs in 2 separate R/3 systems.
In one system it works fine, and measured values are returned each time the monitor is set to run according to the specified schedule.
However, for another R/3 system, the monitor has never run, even though the settings are identical in the monitoring setup.
From reading the Interfaces Monitoring Setup guide, I found that this monitor depends on a job called BPM_DATA_COLLECTION* which runs in the monitored system. In the system where monitoring is functioning correctly, I can see this job is completing successfully at the time the monitor is set to run. All I find is completed jobs - no scheduled or released jobs present.
However, for the system where the monitoring is not functioning, I found that this job is not running, but that the job is sitting in scheduled status instead.
When I tested manually running the job in this system, it ran successfully, and in Solution Manager the monitor brought back the measured value, so the monitor only ran successfully when I manually ran the job in the monitored system.
I read notes 1321015 & 1339657 relating to IDOC monitoring. 1321015 appears to be more relevant, yet it does not exactly describe my issue - it mentions the job BPM_DATA_COLLECTION* failing rather than just remaining in scheduled status which is what I see.
Anyone else see this issue before?
On a more general point - the standard BPM Setup guide doesn't really go into much detail on IDOC Monitoring, and makes no mention of what is happening in the background, i.e. the job BPM_DATA_COLLECTION* being created and run as per schedule. This info is found in a separate document "Interface Monitoring Setup Guide".
Is there any single document which describes fully what happens both in the Solution Manager and the Monitored systems when BPM is activated? For example, to describe which monitors require jobs to be run, which monitors require additional setup in monitored system, etc? A document such as this which describes exactly the process flow for each monitor would be very useful in troubleshooting issues going forward.
Thanks,
John

Hello John,
most probably the user assigned to the corresponding RFC READ connection that connects SolMan with the backend system doesn't have proper authorization to release a job. That's why it is only created/scheduled but not released. Verify if the RFC user on the backend has the latest CSMREG profile assigned according to SAP note 455356.
You can also check if the latest ST-PI support package is installed on your backend system as the ST-PI usualy contain the latest definition of CSMREG.
Best Regards
Volker

PR Overall release issue

PR release strategy issue comes when Line items in PR added by two different persons, PR Release strategy(overall release) not getting triggered.
Release strategy is working fine if i create PR with only one user id.
Both id's maintained in classification.
Is this sap standard behavior??
Created PR 4201001933 line item 10. using User ID - 20061704
Triggered correct release strategy TD QH.
Added line item 20 using user Id - 345045 --- (release startegy gone)
classification Maintained for TD QH

We have a similar equirement since we have cost center as one of the characteristics in PR overall release strategy.
In our case we agreed with Business that the CC in the first PR line item will decide the release strategy. (Or the first CC of thefirst line item in case of multiple account assignment.) We wrote a small piece of code to achieve this, to enter that CC in ceban-kostl.
If your business requirement permits, you may follow this strategy, where user id of the first line item will derive release strategy.
Regards.
Satish Patankar.

Big File to IDOC - performance issue

Hi All,
I am trying to create scenario where I have a file with aproximately 10 000 rows. From each row I am creating one IDOC and want to send it to R/3. Interface looks fine - it is working, but it is killing XI box for some time and u cant access it.
Full scenario look like this
File -> BPM (for 1:n) -> IDOC
I tried to find some solutions for doing the workload smaller by splitting file to less lines (500rows per file) but then file adapter picks up all file and processed them in parallel. So this is new scenario:
BigFile -> XI -> File -> BPM(1:n) -> IDOC
I tried to put second file sender communication channel as EOIO but looks like this does not work - or messages from queue are processed to fast. When one message starts BPM another file message start to be processed.
Do You have any ideas on how to make it more responsive and less performance impact?
thanks in advance.
Dawid

Hi ;
Since mappings are processed by the J2EE Engine, the maximum available Java heap may be a limit-ing factor for the maximum document size the XI mapping service is able to process. Tests have shown that processing of XSLT mappings consumes up to 20 times the source document size (using identity mapping). The maximum available Java heap for 32bit JVMs is platform-dependent. Using 64bit JVM platforms is an option here.
Current maximum heap sizes 32bit
OS
Maximum heap (GB)
Linux
2
Windows
1.2 1.4
The Java heap is limited by the heap limit of the process (may be limited by address space because operating system code or libraries may also be loaded within the same address space). Also, Java internal memory areas such as the permanent space for loading Java classes must fit into the same address space.
Java VM tuning is one of the most crucial tuning steps, especially for more complex scenarios. For information about setting baseline JVM parameters, see SAP Note 723909. You must also take plat-form-specific parameters into account (for example, JIT compiler settings). The impact of Garbage Collection (GC) behavior especially may become a critical issue. Overall GC times for the J2EE appli-cation should be well below 5%. For more information about GC behavior and settings, see also SAP Note 552522.
Specific to XI is the fact that you sometimes need to process large documents for mapping or when using signatures. This can lead to excessive memory usage on the Java side. Therefore, you must observe Garbage Collection and the available Java heap in order to evaluate performance and pre-vent OutOfMemory exceptions. Since XI mapping is processed by stateless session beans that are called using a JCo interface, this may lead to a reduction of parallel JCo server threads within the JCo RFC Provider service of a J2EE server node (you can compensate for this by adding J2EE server nodes).
Mudit

Idoc sender issue

Hi,
I have an issue in Idoc sender scenario.
The flow is Idoc to BPM to Flat file.
Idoc is triggered from R/3 system via RFC port. It enters XI which is visible in Moni. But data is not there.
Which transaction to use to trace Idoc in XI?
I can see the Idoc successfully sent in we02 from R/3 system. But no data in Moni in main message or attachment.
Regards,
Anirudh.

Hi
Go through following ALE step, check whether you missed any of these steps:
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)
     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 6)
     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.
Step 7)
     Not mandatory.
     Goto BD64.
     Click on Create model view.
     Add message type.
Regards
Sami

IDOC creation issue at XI side - File to IDOC

Hi Everybody,
I am working on a File to IDOC scenario (XI 3.0).
We have to create Orders in the R/3 System using this Interface.
Mapping used is Java.
I am using 2 Classes : Group and SendIdoc one below the other in the Interface Mapping:
Firstly by using Group Class I am Grouping the Records in the file and then creating the IDOCs by using the next class(SendIdoc).
In the production environment if we drop like 20 files at a time in the source NFS folder the number of IDOCs created are wrong.
Say for example, for the first file dropped expected IDOCs are 10 but only 8 are created in SXMB_MONI .However in the input payload (in SXMB_MONI) the entire text file is read.
When we put the files sequentially say one after the other is processed, the number of IDOCs created are fine.
This is very strange problem.
I tried changing the polling interval of the channel but was of no help.
Any parameters we need to set in the channel or XI system to overcome this issue?
Can someone help me out on this?
Helpful answers will be rewarded points.
Thanks & Regards,
RK

Hi ,
When you placing files sequentially its working fine menas there is no problem with Java Code,one morething use synchronize methods or thread programming in Java maps is not advisable.
as per my knowledge File adapter picking up the recodrs when its giving inout to Java map some thing misisng....
for one file you need to create multiple IDocs try use QOS EOIO or if its not working then try to use record set per message one like that,let me know.
Regards,
Raj

Idoc flatfile to IDOC xml issue with new PI7.11 module SAP_XI_IDOC/IDOCFlat

Hi,
I am trying to develop a scenario as mentioned in the blog using the new module available in PI7.1,but I am getting this error
"Error: com.sap.conn.idoc.IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "ORDERS05" is unavailable."
I have made every configuration correct and IDOC meta data available in both SAP R3 and PI,but it is still complaning about the meta data does not exist.
Blog: http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/13743%3Fpage%3Dlast%26x-order%3Ddate
did anybody face issue with the new module available "SAP_XI_IDOC/IDOCFlatToXmlConvertor",please help me or give me mre information why I am getting this meta data error.
Thank you,
Sri

Hi Sri,
To Convert IDOC Flat file into IDOC xml from the given blog, the IDOC flat file should be present in standard format like:
E2EDK01005                    0000047110815000000000001.........
E2EDKA1003                    0000047110815000000000002.........
E2EDKA1003                    0000047110815000000000003..........
E2EDKA1003                    0000047110815000000000004........
The Flat file have relationship as IDOC Number "000004711081500000" and segment sequence "0000001".
If your flat file is not in this formate so i don't think that module is able to convert into IDOC xml. and if your file is already in this format then it may be issue with destinations which are created in NWA.
Thanks
Harish

Idoc related issues

Hi
We have designed an alv report that will display idoc details for FINSTA01 idoc.
On clicking release button on the alv output.
I have to work on the following requirement.
"Map FINSTA01 to PEXR2001 to create idoc. Show the report with new idoc no and old idoc no"
Is there any function module to map the above idocs? How we will do that. Please give me details.After mapping how can I generate a new PEXR2001 idoc programmatically.
Regards,
Sucheta.

Hi
I have used the following code for this functionality. Please suggest where I am wrong.
CALL FUNCTION 'IDOC_READ_COMPLETELY' "To read the segments of finst01 idoc
EXPORTING
 DOCUMENT_NUMBER = tb_output-idoc
IMPORTING
 IDOC_CONTROL = wa_edidc
NUMBER_OF_DATA_RECORDS =
NUMBER_OF_STATUS_RECORDS =
TABLES
INT_EDIDS =
 INT_EDIDD = tb_edidd
EXCEPTIONS
 DOCUMENT_NOT_EXIST = 1
 DOCUMENT_NUMBER_INVALID = 2
 OTHERS = 3
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
 * Get data from the Idoc segments
data: wa_edidd like line of tb_edidd.
data: wa_Z1EXNA12 type Z1EXNA12, wa_Z1EXNA13 type Z1EXNA13, wa_Z1EXNA14 type Z1EXNA14,
 wa_Z1EXNA15 type Z1EXNA15, wa_Z1EXNA16 type Z1EXNA16, wa_E1IDKU1 type E1IDKU1,
 wa_E1EDK03 type E1EDK03, wa_E1EDK02 type E1EDK02,
 WA_E1IDT01 type E1IDT01 , wa_E1IDB02 type E1IDB02, wa_E1EDKA1 type E1EDKA1,
 wa_E1IDPU1 type E1IDPU1 , wa_E1IDKU7 type E1IDKU7.
 LOOP AT tb_edidd INTO wa_edidd.
 CASE wa_edidd-segnam.
 WHEN 'E1IDKU1'.
 wa_E1IDKU1 = wa_edidd-sdata.
 WHEN 'E1EDK03'.
 wa_E1EDK03 = wa_edidd-sdata.
 WHEN 'E1EDK02'.
 wa_E1EDK02 = wa_edidd-sdata.
 WHEN 'E1IDT01'.
 wa_E1IDT01 = wa_edidd-sdata.
 WHEN 'E1IDB02'.
 wa_E1IDB02 = wa_edidd-sdata.
 WHEN 'E1EDKA1'.
 wa_E1EDKA1 = wa_edidd-sdata.
 WHEN 'E1IDPU1'.
 wa_E1IDPU1 = wa_edidd-sdata.
 WHEN 'E1IDKU7'.
 wa_E1IDKU7 = wa_edidd-sdata.
 WHEN 'Z1EXNA12'.
 wa_Z1EXNA12 = wa_edidd-sdata.
 when 'Z1EXNA13'.
 wa_Z1EXNA13 = wa_edidd-sdata.
 when 'Z1EXNA14'.
 wa_Z1EXNA14 = wa_edidd-sdata.
 when 'Z1EXNA15'.
 wa_Z1EXNA15 = wa_edidd-sdata.
 when 'Z1EXNA16'.
 wa_Z1EXNA16 = wa_edidd-sdata.
 endcase.
 clear wa_edidd.
 endloop.
 data: tb_idoc_contrl type standard table of edidc with header line,
 tb_idoc_data type standard table of edidd with header line,
 tb_idoc_status type standard table of BDIDOCSTAT with header line,
 tb_ret_var type standard table of BDWFRETVAR with header line,
 tb_serial_info type standard table of BDI_SER with header line.
 clear wa_edidd.
 loop at tb_idoc_data.
 tb_idoc_data-DOCNUM = wa_edidc-docnum.
 tb_idoc_data-segnam = 'E1IDKU1'.
 wa_E1IDKU1-BGMTYP = 'PEX'.
 wa_E1IDKU1-BGMNAME = 'REMADV'.
 tb_idoc_data-sdata = wa_E1IDKU1.
 append tb_idoc_data.
 tb_idoc_data-DOCNUM = wa_edidc-docnum.
 tb_idoc_data-segnam = 'E1EDK03'.
 tb_idoc_data-sdata = wa_E1EDK03.
 append tb_idoc_data.
 tb_idoc_data-DOCNUM = wa_edidc-docnum.
 tb_idoc_data-segnam = 'E1EDK02'.
 tb_idoc_data-sdata = wa_E1EDK02.
 append tb_idoc_data.
 tb_idoc_data-DOCNUM = wa_edidc-docnum.
 tb_idoc_data-segnam = 'E1IDK02'.
 tb_idoc_data-E1IDK02 = wa_E1IDK02.
 append tb_idoc_data.
 tb_idoc_data-DOCNUM = wa_edidc-docnum.
 tb_idoc_data-segnam = 'E1IDT01'.
 tb_idoc_data-sdata = wa_E1IDT01.
 append tb_idoc_data.
 tb_idoc_data-DOCNUM = wa_edidc-docnum.
 tb_idoc_data-segnam = 'E1IDB02'.
 tb_idoc_data-sdata = wa_E1IDB02.
 append tb_idoc_data.
 tb_idoc_data-DOCNUM = wa_edidc-docnum.
 tb_idoc_data-segnam = 'E1EDKA1'.
 tb_idoc_data-sdata = wa_E1EDKA1.
 append tb_idoc_data.
 tb_idoc_data-DOCNUM = wa_edidc-docnum.
 tb_idoc_data-segnam = 'E1IDPU1'.
 wa_E1IDPU1-DOCNAME = 'PEX'.
 tb_idoc_data-sdata = wa_E1IDPU1.
 append tb_idoc_data.
 tb_idoc_data-DOCNUM = wa_edidc-docnum.
 tb_idoc_data-segnam = 'E1IDKU7'.
 tb_idoc_data-sdata = wa_E1IDKU7.
 append tb_idoc_data.
 tb_idoc_data-DOCNUM = wa_edidc-docnum.
 tb_idoc_data-segnam = 'Z1EXNA12'.
 tb_idoc_data-sdata = wa_Z1EXNA12.
 append tb_idoc_data.
 tb_idoc_data-DOCNUM = wa_edidc-docnum.
 tb_idoc_data-segnam = 'Z1EXNA13'.
 tb_idoc_data-sdata = wa_Z1EXNA13.
 append tb_idoc_data.
 tb_idoc_data-DOCNUM = wa_edidc-docnum.
 tb_idoc_data-segnam = 'Z1EXNA14'.
 tb_idoc_data-sdata = wa_Z1EXNA14.
 append tb_idoc_data.
 tb_idoc_data-DOCNUM = wa_edidc-docnum.
 tb_idoc_data-segnam = 'Z1EXNA15'.
 tb_idoc_data-sdata = wa_Z1EXNA15.
 append tb_idoc_data.
 tb_idoc_data-DOCNUM = wa_edidc-docnum.
 tb_idoc_data-segnam = 'Z1EXNA16'.
 tb_idoc_data-sdata = wa_Z1EXNA16.
 append tb_idoc_data.
 endloop.
 move wa_edidc to tb_idoc_contrl.
 wa_edidc-DOCTYP = 'PEXR2NA1'.
 wa_edidc-MESTYP = 'REMADV'.
 wa_edidc-IDOCTP = 'PEXR2002'.
 wa_edidc-cimtyp = 'PEXR2NA1'.
DATA: W_DOCNUM TYPE EDIDC-DOCNUM.
 CALL FUNCTION 'IDOC_WRITE_AND_START_INBOUND'
 EXPORTING
 I_EDIDC = WA_EDIDC
 DO_COMMIT = 'X'
 IMPORTING
 DOCNUM = W_DOCNUM
 ERROR_BEFORE_CALL_APPLICATION =
 TABLES
 I_EDIDD = TB_IDOC_DATA
 EXCEPTIONS
 IDOC_NOT_SAVED = 1
 OTHERS = 2
 IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 ENDIF.
data: tb_status type table of BDIDOCSTAT with header line.
append wa_edidc to tb_idoc_contrl.
CALL FUNCTION 'IDOC_INPUT_REMADV'
EXPORTING
 INPUT_METHOD = 'A'
 MASS_PROCESSING = ' '
IMPORTING
WORKFLOW_RESULT =
APPLICATION_VARIABLE =
IN_UPDATE_TASK =
CALL_TRANSACTION_DONE =
TABLES
 IDOC_CONTRL = tb_idoc_contrl
 IDOC_DATA = TB_IDOC_DATA
 IDOC_STATUS = tb_idoc_status
 RETURN_VARIABLES = tb_ret_var
 SERIALIZATION_INFO = tb_serial_info
EXCEPTIONS
WRONG_FUNCTION_CALLED = 1
OTHERS = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
 endif.
The problem is tb_ret_var is returning nothing. When I am testing the newly generated idoc w_docnum of 'IDOC_WRITE_AND_START_INBOUND' fm in we19 it is generating a new idoc no. But the status of that idoc is 56. I am not getting the payment advice no.
Please suggest what to do next
regards
Sucheta

IDOC mapping issue (calculation using parent and child fields)

We are mapping an IDOC to a file for output to a third party. The IDOC has many segments, some of which are embedded. This is where I'm having the issue. I am trying to perform a calculation on a field from the parent node (E1EDP01-MENGE) with the field from the child node (E1EDP05-KRATE) to determine the total tax for that line (qty X rate).
Issue: The mapping that is in place is using the same MENGE value for all calculations, even where the E1EDP01 segment is not a parent of the E1EDP05 segment.
Please review the screen prints and explain how I can correctly group the E1EDP05 child segments rate field (KRATE) with the corresponding parent segment E1EDP01 quantity (MENGE).
Example:
Parent segment, E1EDP01 / Child segment E1EDP05 (There are many E1EDP05 segments for 1 E1EDP01 segment)
E1EDP01 (parent node)
E1EDP05 (child node)
Target structure
ITEM (parent) --->E1EDP01 is mapped at node level
-->ITEM_DATA --->E1EDP01 is mapped at node level
-->ITEM_TAX --->E1EDP01 is mapped at node level
 -->(fields for item_tax)
 -->Record type
 -->Invoice number
 -->Line total
 -->etc...
I am mapping (E1EDP01-MENGE) for calculation with (E1EDP05-KRATE) to determine tax at the line item level. I have the context set at each Node, E1EDP01 for MENGE and E1EDP05 for KRATE. I was using CopyValue, but this was using the frist occurence of MENGE for all line items.
mapping example
*I am using MENGE (Copy_Value) then multiplying by KRATE to get the line item total. This was causing the same MENGE (because of Copy_Value) for all line items.
E1EDP01-MENGE|Copy_Value|MULT--->TAX_ITEM-LINE_TOTAL
E1EDP05-KRATE|
I removed the CopyValue and now I'm getting the following error:
Cannot produce target element /ns0:MT_DTN_INVOICE1/INVOICE/ITEM/ITEM_TAX[3]/LINE_TOTAL. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
How can I map this so the child records (E1EDP05) are grouped with the correct parent records (E1EDP01)?
Thanks in advance!
Michael

Check this blog:
/people/claus.wallacher/blog/2006/04/17/replication-of-nodes-using-the-graphical-mapping-tool
Regards
Stefan

File - XI - Idoc : mapping issue

Hello gurus,
I have a mapping issue:
I have a mapping between FICABillingNotification to FKK_EBS_DOC_TREE
Some fields are mapped one to one, others a mapped to constants.
But for some reason i don't know, not all fields get the right value.
For example:
Working:
Constant 1 --> BEGIN
Constant LS --> RCVPRT (Receiver Partner Type)
Not working:
Constant FILE-->RCVPOR (Receiver Port)
I had an other value the first time i tried it, but now i changed it to FILE but this value is not used by the mapping.
Any help would be welcome
Thanks
Thomas
Edited by: Thomas Pary on May 28, 2008 3:36 PM

This was allready done (sorry i didn't answered that question).
But Ok now i see, that for this RCVPOR the value of the constant "FILE" is mapped, and i can see it in the payload in SXMB_MONI after the mapping. But it isn't populated to the IDoc field :-s
Another problem is, that like the one said above, some of my values are not mapped :
<FICAExternalBilling>
--<DocumentHeader> mapped to EF1KK_EBS_DOC_HEADER
<BillFromId>25001254</BillFromId> mapped to REF_DOC_NUMBER
<PostingDate>20080520</PostingDate> mapped to POST_DATE
<DocumentDate>20080520</DocumentDate> mapped to DOC_DATE
<OriginTypeId>IV</OriginTypeId> mapped to EXT_DOC_TYPE
<ObjectType/>
<ObjectKey/>
<PendingCommitmentGroupID/>
<InvoiceReferenceID/>
<DisputeDocumentReferenceID/>
--</DocumentHeader>
The value of OriginTypeId is not mapped, but the value of DocumentDate and PostingDate are mapped.

File to Idoc - EOF issue.

Hi,
   I am working on file to IDoc scenario. But facing a problem...
   The source file contains ..EOF.. as a last line in the file. Actually, there is no need to map it to any of the field in IDOC. Just I have created a element in the source data type and ignoring it...
But I am getting this following error message...
    Conversion of file content to XML failed at position 0: java.lang.Exception: ERROR consistency check in recordset structure validation (line no. 43: missing structure(s) in last recordset
Please help me to resolve this issue...
Thanks in advance!!!
Regards,
Vivek LR

Hi,
R u using content conversion in file adapter.Check ur content conversion parameter it is not able to convert the file to XML structure.
wat do u mean by "I have created a element in the source data type and ignoring it... " I think u r not mapping it in mapping right?
chirag

File To IDOC Scenario issue

Hello Friends,
I am facing an issue during File To IDOC Scenario.
Sender side: Text file
It contains data:
name,surname,7894561230 i.e. phone no.
My sendor data type is also desined in same way.
I am facing given below wrror in SXMB_MONI.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_mm_file_to_idoc_</SAP:P1>
<SAP:P2>java.lang.NullPointerException</SAP:P2>
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>java.lang.NullPointerException thrown during application mapping com/sap/xi/tf/_mm_file_to_idoc_:</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
In sendor file adaptor I am using 'File' as message protocol.
Should I have to use 'File content Conversion'.
I tested message mapping. It is working fine.
Kindly suggest me for above error. How I can resolve it?
Regards,
Narendra

It contains data:
name,surname,7894561230 i.e. phone no.
java.lang.NullPointerException thrown during application mapping com/sap/xi/tf/_mm_file_to_idocc
In sendor file adaptor I am using 'File' as message protocol.
Should I have to use 'File content Conversion'
can you tell in what format is your source structure? I mean is it an XML or a CSV file?
If it is a CSV file then you need FCC....but then in this case the error should have been thrown by the channel itself and the message wont have come till mapping step....
If your source file is really in csv format then apply FCC....many blogs, references are readily available on SDN.
Regards,
Abhishek.

IDoc Performance Issue

Hi,
I have strange issue in the IDoc deliviry to the R3 systems.
We have a IDoc created every 30 minutes and the deliviried to R3 systems.
Because of some systems issues 2 IDocs that were created at 30 minutes interval was delivired to the R3 system at the same time, which should not happen.This has caused a data conflict.
Is there any mechaninm that can be incorporated to avoid dispatching of 2 or more Idocs of same type at the same time.

Hi
At Idoc delivary use time stamp to Idoc name. Use the system time.
Thnks
Venkat Anil

IDOC Released Issue

Similar Messages

Maybe you are looking for