Fill Segment E1EDP04 in IDOC_OUTPUT_ORDERS

Hi All,
I am supposed to code for filling the Segment E1EDP04 of ORDERS Message type and ORDERS04 basic type.
I think i will have to do that using an EXIT function module, i guess 002.
I need to know what preriquists do i need to fullfill to get the segment filled.
Also, the procedure for getting the exit FM.Do i have to use any Note?
Thanks,
Yogeeta

I need to send Purchase Order Data through idoc whenever a PO is created or changed?
Use Standard message type ORDERS
So Can I use idoc_output_orders Function module for both PO create as well as change?
Yes
Regards
Shital

Similar Messages

Problem filling segment E1BPADR1 in idoc Salesorder_createfromdat201

Ladies and Gentlemen,
I have a problem with populating segment E1BPADR1 in idoc SALESORDER_CREATEFROMDAT201. My client is already using the idoc to successfully post Inbound Sales orders. Now, they wish to add additional address data to the Sales Order Partner Address screen. The standard partner segment (E1BPPARNR) permits them to fill some data which they are presently filling (i.e. Name 1, Street 1, Country, etc), but they have a requirement to fill additional fields Street2, Street3, etc.
When I add fill segment E1BPADR1, the data in segment E1BPPARNR is removed from the created Sales Order so that the data from segment E1BPPARNR is deleted, and no new data from E1BPADR1 is updated.
Has anyone experienced similar problems, and any ideas on how to get around it? Points rewarded for useable suggestions.
Regards,
Steve

Done

Segment E1EEDPO4 is missing in outbod message type ORDERS05

Hi Gurus,
When I create an Output type for PO using Message type ORDERS05, the segments E1EDP04 is missing in data records. Eventually this segment should carry the tax information. The tax information is very much appeared in Po and it is missing in IDOC. what should I do to make this segment appear in outbound IDOC data records.
Please mention the T codes and steps.
Thanks and regards
Rohini kumar

Hi,
You can use user exits EXIT_SAPLEINM_002 to populate segment E1EDP04 for outbound IDoc ORDERS05.
This segment is not populated in standard FM IDOC_OUTPUT_ORDERS.
Regards,
Ferry Lianto

IDOC Segments-Urgent.

Hello,
I have a IDOC number and in WE02 when I see the segments,
Segment E1EDP04 is coming before E1CUREF.
I want Segment E1EDP04 to come after E1CUREF.
Again How can i use the same IDOC number for debugging
Thanks, madhu...

WE19 will create a new IDoc. This is not what he asked.
To re-process and already processed IDoc you will need to change the status to '64'. Use the Function Module 'IDOC_STATUS_WRITE_TO_DATABASE'.
Then using BD87 you can re-process the IDoc. Don't forget to put a break-point on the processing Function Module though.
Is it a standard IDoc. Is the problem caused by a user exit.

Segment field in Automatic Postings

Hi all of you
Could any suggest me how to fill the segment field in automatic postings like AFAB and AIBU as Document splitting is activated and we dont have assignment the segment in PCtr master data.
Please help me regarding
Thanks
Ramki

We have activated the BAdI also.
I am asking you how the system picks the segment field in AA automatic postings like AIBU/AFAB without any assignment in Asset master. In addl account assignment also there is no segment field.
What is the procedure required to fill segment field in AA automatic postings
Please help me
Thanks & Regards
Ramki

Adding an existing segment in data record of IDOC

Hi All,
I am using basic type ORDERS04 to send IDOC out of SAP system.
Currently its not sending the segment E1EDP04 in the data record.
What should be done to get this segment in the data record of IDOC?
Also, can any one tell me the significance of VIEW when i double click on Message type of a particular partner in WE19.
Thanks,
Yogeeta

What is the message type?
E1EDP04 IDoc: Document Item Taxes
First you need to find out why required segment is not being generated, is there any data missing in document due to which the segment is missing?
If that (missing segment) is sap-standard funtionality and you would like to include the segment in IDoc then you need to implement the user-exit. And to find the correct user-exit you need Message Type.

FM for idoc type DESADV01

Hi,
Which of the following function module is bet fit for IDOC type DESADV01, message type DESADV and processing code SD05.
IDOC_OUTPUT_DESADT
IDOC_OUTPUT_DESADV01
IDOC_OUTPUT_DELVRY (If I use this one as it doesn't have same segments then how data will be populated)
Question 1 I need to make some changes in the function module as need to fill segment data with custom table.
Question 2 Secondly, need to extend the idoc and I guess for extending the idoc it should have user exits.
Question 3. Please provide the user exit if there is any other than IDOC_OUTPUT_DELVRY.
Regards
Rinku
Message was edited by:
Rinku Malik

Hi,
use the FM -> IDOC_OUTPUT_ORDERS
REGARDS,
Nagaraj

Error: LK047 Material movement could not be posted in the system via IDOC

I am trying to create an article document (goods movement doc) for an already created purchase order.
but this is via an IDOC (WMMBXY). after filling the data in WE19, i shoot the idoc in to the system. in we02 i get the following error message: LK047 Material movement could not be posted in the system . Can someone please help.
the following fields are filled:
Segment: E1MBXYH
Document date        20091124
Posting date         20091124
Reference            9999999999
Doc.Header Text      POS/1110
Transaction code     MB01
USNAM                user12
Segment: E1MBXYI
Processing ind.      1
Material             832924
Plant                1110
Movement Type        101
Debit/Credit     +
Currency             EUR
Qty in un.entry      250
Unit of Entry        PAK
Qty OPUn             90
OrdPriceUnit         KG
Purchasing Doc.      9100000141
Item                 1
Profit Center        11090
G/L Account          22706
Movement Type        101
SLED/BBD             20091231

Hello Shankar,
Glad to hear from you!
In your question, please make sure you use leading zeros for the MATNR field. In header segment field E1MBXYH-BKTXT, we use header text. Hope you are using inbound posting function L_IDOC_INPUT_WMMBXY.
Please try with this and it works for us.
Thanks a lot,
Venu

Templates in ABAP

Hi,
I want a brief introduction to templates in ABAP.
I need to write a template which shall generate dynamic code. I am very new to this template concept in ABAP. Could some one please provide me good documents on how to write a template in ABAP or/and provide a simple sample program?
Regards,
Ravi

following is a template for example:
@--Template for generating CDS_READ_SERVICE--
*@ DATA: LT_SEGM TYPE SMMW_CDS_SEGM_TTYP.
*@ DATA: LT_MAPP TYPE SMMW_CDS_MAPP_TTYP.
*@ DATA: WA_SEGM TYPE SMMW_CDS_SEGM.
*@ DATA: WA_MAPP TYPE SMMW_CDS_MAPP.
*@ DATA: LS_HDR TYPE MSB_HEADER.
*@ DATA: LS_MBOINFO TYPE SMMW_CDS_MBO_INFO.
*@ DATA: META_OBJ TYPE SMMW_GUID.
*@ DATA: msg_strname(40) TYPE C.
*@ DATA: memodblbin(40) TYPE C,
*@ memodbltxt(40) TYPE C.
*@ META_OBJ = I_META_OBJECT(32).
@ get MBO structure,version and sw component name
*@ CALL FUNCTION 'MSB_GET_MBO_HEADER_INFO'
*@ EXPORTING
*@ IM_MBO_VERSION_ID = META_OBJ
*@ IMPORTING
*@ EX_MBO_HEADER = LS_HDR
*@ EXCEPTIONS
*@ MISSING_IMPORT_PARAMETER = 1
*@ NO_SUCH_MBO = 2
*@ MORE_THAN_ONE_MBO = 3
*@ OTHERS = 4
*@ 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 MBO information by calling API SMMW_CDS_GET_MBODATA
*@ CALL FUNCTION 'MMW_CDS_GET_MBODATA'
*@ EXPORTING
*@ I_MBO_TRANS = META_OBJ
*@ IMPORTING
*@ SEGM_TAB = LT_SEGM
*@ MAPP_TAB = LT_MAPP
*@ MBO_INFO = LS_MBOINFO
*@ EXCEPTIONS
*@ MBO_ID_IS_INITIAL = 1
*@ PARENT_SEGMENT_NOT_FOUND = 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.
*@ msg_strname = LS_MBOINFO-MESGSTR_NAME.
*@ memodblbin = LS_MBOINFO-BMEMTABLE_NAME.
*@ memodbltxt = LS_MBOINFO-TMEMTABLE_NAME.
 CDS READ SERVICE
 This method has been generated
 Never change it manually, please!!
 Transaction: \LS_HDR-NAME\
 Template : \I_TEMPLATE\
 GenKey : CDS_READ_SERVICE
 Generated on \SY-DATUM\ \SY-UZEIT\
 by \SY-UNAME\
CONSTANTS: LC_INSERT VALUE 'I',
 LC_UPDATE VALUE 'U',
 LC_DELETE VALUE 'D'.
DATA: LT_OBJ_LIST TYPE EXTRACTKEY_TT.
DATA: WA_OBJ_LIST TYPE SMMW_EXTRACTKEY.
DATA: LV_COUNT TYPE INT4.
DATA: RECORDS_NOT_FOUND TYPE BOOL VALUE ' '.
CONSTANTS: lv_sendbits(32) TYPE x VALUE
'FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF'.
*@ IF LS_HDR IS NOT INITIAL.
DATA: MBO_STR TYPE \msg_strname\.
*@ IF LT_SEGM IS NOT INITIAL.
*@ LOOP AT LT_SEGM INTO WA_SEGM.
declaring tables and workareas for segment : \WA_SEGM-SEGM_NAME\
DATA: LT_T\WA_SEGM-TABLENAME\ TYPE TABLE OF \WA_SEGM-TABLENAME\.
DATA: WA_T\WA_SEGM-TABLENAME\ TYPE \WA_SEGM-TABLENAME\.
DATA: WA_S\WA_SEGM-GEN_NUM\ TYPE \WA_SEGM-SEGM_STR\.
*@ ENDLOOP.
copy the extract key table to a local internal table.
LT_OBJ_LIST[] = OBJ_LIST[].
IF LT_OBJ_LIST IS INITIAL.
*...handle log here........
 EXIT.
ELSE.
sort the table to delete adjacent duplicate entries
 SORT LT_OBJ_LIST BY EXTRACTKEY.
delete the duplicate entries from the table before processing
 DELETE ADJACENT DUPLICATES
 FROM LT_OBJ_LIST
 COMPARING EXTRACTKEY.
 DESCRIBE TABLE LT_OBJ_LIST LINES LV_COUNT.
 IF task EQ LC_DELETE OR task EQ LC_UPDATE.
 IF LV_COUNT GT 1.
*.....bulk message is only for task 'I' not for task 'U' or 'D'.
*.....Hadle log here.....
 OBJ_MISS[] = LT_OBJ_LIST[].
 EXIT.
 ENDIF.
 ENDIF.
 IF TASK EQ LC_DELETE.
prepare MBO message for the Extract keys whose task is DELETE
*@ LOOP AT LT_SEGM INTO WA_SEGM WHERE HIERARCHY EQ 1.
@ if the segment is root segment only.
 LOOP AT LT_OBJ_LIST INTO WA_OBJ_LIST.
 WA_S\WA_SEGM-GEN_NUM\-TASK = TASK.
 WA_S\WA_SEGM-GEN_NUM\-\WA_SEGM-KEYFIELD\ =
 WA_OBJ_LIST-EXTRACTKEY.
 WA_S\WA_SEGM-GEN_NUM\-EXTRACTKEY =
 WA_OBJ_LIST-EXTRACTKEY.
 APPEND WA_S\WA_SEGM-GEN_NUM\ TO MBO_STR-\WA_SEGM-SEGM_NAME\.
 ENDLOOP.
*@ ENDLOOP.
task is not 'D'.
 ELSE.
*@ SORT LT_SEGM BY HIERARCHY.
*@ LOOP AT LT_SEGM INTO WA_SEGM.
select statement to fill segment: \WA_SEGM-SEGM_NAME\
*@ IF WA_SEGM-HIERARCHY NE 1.
 IF RECORDS_NOT_FOUND IS INITIAL.
*@ ELSE.
 DESCRIBE TABLE LT_OBJ_LIST LINES LV_COUNT.
*@ ENDIF.
 SELECT * INTO TABLE LT_T\WA_SEGM-TABLENAME\
 FROM \WA_SEGM-TABLENAME\
 FOR ALL ENTRIES IN LT_OBJ_LIST
@ For root segment compare extractkey with synckey
*@ IF WA_SEGM-HIERARCHY = 1.
 WHERE \WA_SEGM-KEYFIELD\ = LT_OBJ_LIST-EXTRACTKEY.
@ For other than root segments compare extractkey with
@ extractkey only.
*@ ELSE.
 WHERE EXTRACTKEY = LT_OBJ_LIST-EXTRACTKEY.
*@ ENDIF.
*@ IF WA_SEGM-HIERARCHY = 1.
 IF SY-SUBRC <> 0.
 all the extractkeys are invalid hence send all to OBJ_MISS.
 OBJ_MISS[] = LT_OBJ_LIST[].
 RECORDS_NOT_FOUND = 'X'.
 ELSEIF LV_COUNT NE SY-DBCNT.
 Not all the keys are invalid.atleast one key is invalid.
*@ LOOP AT LT_MAPP INTO WA_MAPP
*@ WHERE SEGM_NAME = WA_SEGM-SEGM_NAME AND IS_SYNCKEY EQ 'X'.
 LOOP AT LT_OBJ_LIST INTO WA_OBJ_LIST.
 READ TABLE LT_T\WA_SEGM-TABLENAME\
 WITH KEY \WA_MAPP-SFLD_NAME\ = WA_OBJ_LIST-EXTRACTKEY
 TRANSPORTING NO FIELDS.
*@ ENDLOOP.
 IF SY-SUBRC <> 0.
 APPEND WA_OBJ_LIST TO OBJ_MISS.
 ENDIF.
 ENDLOOP.
 ENDIF.
*@ ENDIF.
 process all the records to set the value for task field.
 IF LT_T\WA_SEGM-TABLENAME\ IS NOT INITIAL.
 IF task EQ LC_UPDATE.
 WA_S\WA_SEGM-GEN_NUM\-SENDBITS = lv_sendbits.
 ENDIF.
 WA_S\WA_SEGM-GEN_NUM\-TASK = TASK.
 LOOP AT LT_T\WA_SEGM-TABLENAME\ INTO WA_T\WA_SEGM-TABLENAME\.
 move-corresponding WA_T\WA_SEGM-TABLENAME\
 to WA_S\WA_SEGM-GEN_NUM\.
*@ LOOP AT LT_MAPP INTO WA_MAPP
*@ WHERE SEGM_NAME = WA_SEGM-SEGM_NAME AND IS_MEMO NE SPACE.
 IF wa_t\wa_segm-tablename\-\wa_mapp-sfld_name\ IS NOT INITIAL.
*@ IF WA_MAPP-IS_MEMO EQ 'T'.
 select the text memo content from the db table
 SELECT SINGLE CONTENT
 FROM \memodbltxt\
 INTO WA_S\WA_SEGM-GEN_NUM\-\WA_MAPP-SFLD_NAME\
 WHERE tablename = '\WA_SEGM-TABLENAME\' AND
 tablekey = WA_T\WA_SEGM-TABLENAME\-\WA_SEGM-KEYFIELD\ AND
 tablefield = '\WA_MAPP-SFLD_NAME\'.
*@ ELSEIF WA_MAPP-IS_MEMO EQ 'B'.
 select the binary memo content from the db table
 SELECT SINGLE CONTENT
 FROM \memodblbin\
 INTO WA_S\WA_SEGM-GEN_NUM\-\WA_MAPP-SFLD_NAME\
 WHERE tablename = '\WA_SEGM-TABLENAME\' AND
 tablekey = WA_T\WA_SEGM-TABLENAME\-\WA_SEGM-KEYFIELD\ AND
 tablefield = '\WA_MAPP-SFLD_NAME\'.
*@ ENDIF.
 ENDIF.
*@ ENDLOOP.
 APPEND WA_S\WA_SEGM-GEN_NUM\ TO MBO_STR-\WA_SEGM-SEGM_NAME\.
 ENDLOOP.
 ENDIF. " table LT_T\WA_SEGM-TABLENAME\ not initial.
*@ IF WA_SEGM-HIERARCHY NE 1.
 ENDIF.
*@ ENDIF.
*@ ENDLOOP.
 ENDIF.
ENDIF. " Object list not initial.
*@ LOOP AT LT_SEGM INTO WA_SEGM WHERE HIERARCHY EQ 1.
IF MBO_STR-\WA_SEGM-SEGM_NAME\ IS NOT INITIAL.
 MBO_MESSAGE = MBO_STR.
Filling Header of the MBO message if it is not empty.
 DESCRIBE TABLE MBO_STR-\WA_SEGM-SEGM_NAME\ LINES LV_COUNT.
*@ ENDLOOP.
 CALL FUNCTION 'SYSTEM_UUID_C_CREATE'
 IMPORTING
 uuid = MBO_COMM_HEADER-MESSAGE_ID.
 MBO_COMM_HEADER-SWCV_NAME = '\LS_HDR-SWCV_NAME\'.
 MBO_COMM_HEADER-VERSION = '\LS_HDR-VERSION\'.
 MBO_COMM_HEADER-MBO_NAME = '\LS_HDR-NAME\'.
 GET TIME STAMP FIELD MBO_COMM_HEADER-SEND_TSTMP.
This vale SEND_TSTMP filling involves some problem...
 MBO_COMM_HEADER-SEND_USR = SY-UNAME.
 IF LV_COUNT EQ 1.
 MBO_COMM_HEADER-MESSAGE_TYPE = 'I'.
 READ TABLE OBJ_LIST INDEX 1 INTO WA_OBJ_LIST.
 IF SY-SUBRC = 0.
 MBO_COMM_HEADER-EXTRACT_KEY = WA_OBJ_LIST-EXTRACTKEY.
 ENDIF.
 ELSE.
 MBO_COMM_HEADER-MESSAGE_TYPE = 'B'.
 ENDIF.
ENDIF.
*@ ENDIF.
*@ ENDIF.
I dont understand the notation *@ here...
Why is it used??
Regards,
Ravi

Purchase Order line item tax details not in IDoc ORDERS02

We are on ECC6 and using IDoc ODERS02, when viewing the purchase order in me23n, taxes are visible on the line item under the invoice tab. When we view the same purchase order via the IDoc that was created, the line item taxes are not being displayed in segments E1EDP04 and E1EDP05.
Is there some configuration we need to do to get the taxes info into the IDoc?

Hi Bill,
I think only price elements which have been set to "to be printed" in Customizing will be included into the Idoc.
Just a remark: ORDERS02 is an "historical" Idoc; ORDERS05 is the appropriate one for ECC6 (but this has nothing to do with your problem).
Regards,
John.

Grouping and sum values in XI

Hello,
I 'm working with invoice and I have this source structure as XI input:
Invoice
-- |....
-- |....
-- |Item1
|taxcode=01
|Amount=12
--|Item2
|taxcode=08
|Amount=10
--|Item3
|taxcode=01
|Amount=24
Now my scope is to map these fields to the IDOC segment E1EDP04 grouping by taxcode (MWSKZ taxcode)and putting the sum of the group amount (MWSBT amount).
IDOC:
--|...
--|...
--|E1EDP01
|...
|...
|EIEDP04
|MWSKZ=01
|MWSBT=36
|...
--|E1EDP01
|...
|...
|EIEDP04
|MWSKZ=08
|MWSBT=10
|...
How can I group by a field in XI?
Thank you
Corrado

Hi Corrado,
If You want to do it in graphical mapping then I will do it this way:
1. sort by taxcode
(taxcode) --> split by value (valuechanged) --> formatByExample (Amount, and splitted value) --> sum(amount) --> MWSBT
I can send u a screenshot of something similar if u need.
best regards
Dawid

Line item taxes not showing in IDoc Orders02

We are on ECC6 and using IDoc ODERS02, when viewing the purchase order in me23n, taxes are visible on the line item under the invoice tab. When we view the same purchase order via the IDoc that was created, the line item taxes are not being displayed in segments E1EDP04 and E1EDP05.
Is there some configuration we need to do to get the taxes info into the IDoc?

Hi ,
Those Taxes fields should be selected for the segments you have mentioned .
Check out transaction bd53 ehen you create a Reduced Message type and check the segaments where fields are activatied or not .
Please reward if useful.

INVOICE EDI Inbound IDOC error

Hi,
We have implemented Support pack SAP_APPL SAPKH47027. And now we get
the Following error in IDOC inbound processing message type INVOIC during intercompany billing to post vendor invoices.
Error message: 'Field BSEG-BSCHL (1) (is not an input field)'.
I find that this is due to the OSS note: 960639 that has come along
with this Support pack.
Also SAP has mentioned a corection note to this problem. OSS note:
1032469.
But this Note 1032469 is not clear.
It is mentioned that..
"You explicitly enter the tax amounts in the IDoc
You can enter the tax information either at item level in
segment E1EDP04 or in header segment E1EDK04."
Is SAP suggesting to enter the TAx amounts (E1EDP04-MWSBT)?
And shud the coding be done during the Inbound processing function
module:
IDOC_INPUT_INVOIC_FI or during the outbound processing RSNASTED
(EDI_PROCESSING). We use SAP standard functionality.
Can anybody please explain what SAP has suggested to do techincally.
Regards,
Midhun.

Hi,
I checked both OSS note 960639 & 1032469. I neither find anything in first note ( 960639 ) which could cause this probem nor in the second note ( 1032469 ) which solve this problem. The only way to check is by doing what note 1032469 is saying.
One more thing you can do is debug the code, put the break-pointe message statement and findout where this error message is coming. Then you can check the code to find out the reason for this.
Can you also check if you are getting the same message when you try to enter same data directly in SAP using FB01 or whatever the relavent transaction is.
Regards,
RS

Field BSET-FWSTE (1) is not an input field

We currently have SAP ERP Central Component 5.0 and have recently applied support packs (we are on SAP_APPL - SAPKH50017). Something changed with the inbound function module: IDOC_INPUT_INVOIC_FI
When we have an incoming invoice via an IDoc using function module IDOC_INPUT_INVOIC_FI, we get the error message: 00347 Field BSET-FWSTE (1) is not an input field. Our IDoc does NOT have a tax amount, it has segment #E1EDP04 with values: MWSKZ = E and TXJCD = WI0000000.
If we feed in this Idoc via WE19 in foreground, we can see that this error is only a warning, and can press enter and the IDoc creates the invoice without a problem.
What do we need to change to get this IDoc to create an invoice in the background?

hi Bonnie,
can you run in E mode (stops in case of Error) and se what happens? What is the screen name and number where this problem occurs? If this is in a table control think that instead of BSET-FWSTE(1) it should be BSET-FWSTE(01)
ec

Error in SXMB_MONI as"Copy Sender from Payload: Sender Is Missing in Payloa

Hi Folks,
I am working on file to IDOC scenario. If I am testing in ESR and ID my interface is working fine. But when I am testing end to end I am getting below error. Please find the below error.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error SOAP:mustUnderstand="" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>Copy Sender from Payload: Sender Is Missing in Payload</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error: Copy Sender from Payload: Sender Is Missing in Payload</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Can u ppl please suggest me how to resolve this error.Ur help is highly appreciated.
Thanks,
Swathi

You need to have a S-userid for that....check with senior members within your company....they would be having this S-userid
Some portion from the note:
You are using the Exchange Infrastructure and you use the IDoc adapter to send IDocs. A setting in the IDoc channel
defines that the IDoc sender agreement is to be determined from the payload. The payload is stored in the XI message in the
IDoc tunnel format. If the message has been created, for example, using a Business Process Engine (BPE) process, the IDoc
inbound property may no longer be available in the XI message. This results in the error described above.
TIll you get access to the SAP Note:
In mapping enable the EDI_DC40 segment in your IDOC...fill SEGMENT, SNDPOR, SNDPRT, SNDPRN ....map them as constant
then in IDOC channel check take Apply Control record from payload (or take sender from payload)
Regards,
Abhishek.
Edited by: abhishek salvi on Dec 24, 2010 4:51 PM

Fill Segment E1EDP04 in IDOC_OUTPUT_ORDERS

Similar Messages

Maybe you are looking for