Mapping : DELVRY03/SHPMNT04 Idoc outbound description

Hi All,
I found usefull descriptions on SAP Support Portal - search for documents,
e.g. Mapping : FI outbound remittance advice.
This Excel file shows which SAP tables,fields are transmitted into which segments, fields of the Idoc and decribes possible qualifiers.
We also need descriptions in our project for (R/3,4.7) :
- DELVRY03 outbound
- SHPMNT04 outbound
Hope somebody knows where to find and download this or can provide something similar to share.
Kind regards,
Barbara

Hi Stefan,
WE60 is only IDOC description, we need a full description of the standard including the SAP tables and fields used to fill the Idocs.
Rgds,
Barbara

Similar Messages

XI Idoc outbound record mapping

Hi,
I created proxy to IDoc interface.
All the data are being converted into IDoc format through IDoc adapter.
Now, I am considering another interface which is for data monitoring.
The interface flow is like below.
1. send data to XI (proxy)
2. mapping proxy to IDoc (IDoc adapter)
3. send a IDoc to R/3 1 (IDoc)
4. mapping IDoc to rfc
5. send a rfc data to R/3 2 (rfc)
In the step 4, I need to map IDoc's control records, created automatically by IDoc adapter, to fields in rfc.
But I have no idea how to use outbound record for mapping.
Please help me to resolve the issue.
Thanks in advance.
Regards,
Andrew

In the step 4, I need to map IDoc's control records, created automatically by IDoc adapter, to fields in rfc.
But I have no idea how to use outbound record for mapping.
>>>>>
I am not sure if you can map the control records created automatically by the IDoc adapter to the RFC. You will have to hardcode them in your mapping (IDOC -> RFC).

Idoc outbound from business connector

Hi,
I'm trying to map values to idoc from business connector(4.6). The flow is
map
transformhierarchytoflat
ale outbound process.
When I test the application, it's showing a null pointer exception . I have doubt in what all values should i give for control records ??
Shall i create a new routing rule for this ?
Any help or suggestion will be of great help .
Thanks in advance.

HI,
You are getting the Null Pointer Exception due to missing of Values in any of the context variables or the fields from mapping on target side.
Please check the data that you are passing may have any null values and whcih are not acceptable. Test the message mapping with test Tab.
The Mandatory control records, such as Sender/ receiver Ports, Partner Profiles etc, you need to pass.
Thanks
Swarup

Convert IDoc outbound to IDoc Abstarct

Hello Friends,
Can any please tell me how to convert IDoc outbound to IDoc Abstarct type so that it can be used in BPM.
Thanks
Sam

Hi Woj,
Below is the xml message displayed.It says No Interface found .But I have all the objects at the right place.
<Trace level="1" type="T">Version 000</Trace>
<Trace level="1" type="T">Message status 000</Trace>
<Trace level="1" type="T">Interface action INIT</Trace>
<Trace level="1" type="T">(must be INIT for a new determination)</Trace>
<Trace level="1" type="T">start CHECK_INTERFACE</Trace>
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface MATMAS.MATMAS04*</Trace>
<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">end CHECK_INTERFACE</Trace>
<Trace level="1" type="T">Set interface action INIT into MAST</Trace>
</Trace>
- <Trace level="1" type="B" name="interface activity determination">
<Trace level="1" type="T">Version 000</Trace>
<Trace level="1" type="T">Message status 000</Trace>
<Trace level="1" type="T">Interface action INIT</Trace>
<Trace level="1" type="T">(must be INIT for a new determination)</Trace>
<Trace level="1" type="T">start CHECK_INTERFACE</Trace>
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface MATMAS.MATMAS04*</Trace>
<Trace level="1" type="T">select interface namespace urn:sap-com:document:sap:idoc:messages</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface MIAbA_MATMAS_Req*</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<Trace level="1" type="T">end CHECK_INTERFACE</Trace>
<Trace level="1" type="T">Set interface action DEL into MAST</Trace>
</Trace>
Also I have mapped IDoc_original_outbound to IDoc_asy_Abs _ED in my message mapping 1:1.I have selected original IDoc (not ED) in the receiver determination.
I don't think we need to explicitly maintain IDoc outbound asy in the MI..? should I..?
Kindly suggest me if you find any solution for this happening.
Please send me if you have any scenario of similar type else please mention the steps to be carried out for this scenario so that I can cross check with your steps.
Thanks alot for your valuable time.
Regards
Sam
Message was edited by: Sam
Guest

Mapping issue in idoc to JDBC scenario

mapping issue in idoc to JDBC scenario
source structure
E1KNB1M
BUKRS = 1000
E1KNB1M
BUKRS= 9000
E1KNB1M
BUKRS= 2000
THE NODE E1KNB1M is repeated many times and the field BUKRS is also repeated with E1KNB1M as above
TARGET field : ISFRANCHISE
if any where value of BUKRS =9000 we have to pass Y to the target filed, else N
if BUKRS = 9000   THEN ISFRANCHISE= Y
               ELSE
            ISFRANCHISE=N
I've done the mapping as below
BUKRS = 9000--> IF THEN Y ELSE N--
> ISFRANCHISE
BUT everry time the target value is N only
pl suggest
rgds
mojib

mapped like this
BUKRS--->SORT---->
                                             EQUALS --------IF---THEN    Y
9000------------------------>                                               ----------------->ISFRANCHISE
                                                              ELSE   N
context of BUKRS set to parent node
its worked
thanks to all for valuable suggestions
rgds
mojib

Mapping to an IDOC using an externally created XSL file

I want to map a message to an IDoc using an ABAP XSLT transform. I am creating the XSLT in an external tool.
I need to use an XSD definition of the IDOC as the target document of the mapping. I can get that in two ways:
1) Get the XSD definition of the IDOC from transaction WE60 and use the menu command 'Documentation -> XML Schema'
2) In the Integration Repository, export the XSD of the imported IDOC.
The problem is, there are significant syntax differences between these versions, and I don't know which is the correct version. For instance, the XSD exported from the Integration Repository has a mandatory attribute 'SEGMENT' for each segment that must be filled to create a valid XML message; this is not the case when the XSD definition is created in WE60.
Can somebody advise which is the correct version to use?

Hi Anthony,
This is really strange...
In both case XSD should be same...can you please tell for which idoc you are generating xsd?
Eventhough if you generate XML Schema using WE60, mandatory attribute 'SEGMENT' for each segment has to be there....this validation would be done while posting idoc. It will check for all mandatory fields.
I have some different thoughts that what wojciech has suggested...
"If were your shoes I would use xsd from integration repository because that's the expected result...."
But final goal is not to achieve mapping but posting idoc with proper data in R/3 system successfully.
Your second question..
"Do I assume then that placing a constant value of 1 in the SEGMENT attribute is just to satisfy the validation of the XML message against the XSD:..?
ummm...I think if you assign constant "1" to segment it will generate that segment while creating idoc. Its mandatory to assign constant value to segment which you want to generate...
"Can I assume that the IDoc adapter will fill the SEGMENT attribute with the correct value?.."
I dont think so Idoc adapter will fill this attribute automatically...you need to assign constant to field segment.
Nilesh

Mandatory fields for mapping in ORDERS idoc.

Hi
I m working on File to idoc scenario for creation of sales order in ECC 6.0 , now I want to know what are the mandatory fields in ORDERS idoc which needs to be populated or else disbaled so that the sales order gets created properly in the ECC 6.0..
Pl let me know the method of finding mandatory field for mapping for any idoc and which fileds of idoc are to be disabled.
Pl help ..
ans will be rewarded .
thanks & rgds
mojib

HI,
U can disable the control record segment and in the IDOC adapter use the option apply control record from payload.
If you have set the Apply Control Record Values from Payload indicator in the receiver IDoc adapter, the following fields are filled from the IDoc-XML payload:
·        MESCOD
·        MESCFT
·        TEST
·        EXPRSS
·        STD
·        STDVRS
·        STDMES
·        SNDSAD
·        SNDLAD
·        RCVSAD
·        RCVLAD
·        REFINT
·        REFGRP
·        REFMES
·        STATUS
·        DIRECT
·        OUTMOD
·        CREDAT
·        CRETIM
read the information in below link:
http://help.sap.com/saphelp_nw70/helpdata/EN/ab/bdb13b00ae793be10000000a11402f/frameset.htm
thnx,
chirag

Mapping issue: FCC: Idoc for each record in file

Hi,
I have file to Idoc scenario.
I receive csv file with multiple records.
The requirement is to create an Idoc for each record.
For eg.
source file
A1,B1,C1
A2,B2,C2
A3,B3,C3
After FCC
<MT>
<TRANS>
<ROW>
<A>A1</A>
B1
<C>C1</C>
</ROW>
<ROW>
<A>A2</A>
B2
<C>C2</C>
</ROW>
<ROW>
<A>A3</A>
B3
<C>C3</C>
</ROW>
</TRANS>
<MT>
I have first tested it with only 1 record to test end to end connectivity. It works as expected and Idoc is posted to target system.
Now when I am trying to send multiple records, I am getting some issues.
Below are the steps that I have taken to process multiple records:
1. Changed the cardinality of ROW (child of RecordSet) from 1 to Unbounded.
2. Changed the occurance of Idoc to Unbounded.
3. Mapped ROW to Idoc root.
I have tested the mapping in IR and it generates multiple IDOCs.
When I send the test file, it fails with error Tag found instead of tag IDOC BEGIN=
I can see the xml message created with multiple ROWs in XI by File adapter in sxmb_moni.
When I do Test Configuration in ID, with the XML message extracted from sxmbmoni, the result that I got was:_
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge"><ns0:Message1></ns0:Message1></ns0:Messages>
This means that idoc was not created while mapping.
But the same sample message works OK in IR!
Pls help where I have missed.
Regards,
Anirudh.

Sudhir,
Thanks for your response.
FCC is working fine. I have taken the XML message in XI created after FCC from csv sample message.
I have tested this message in IR by placing it between
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
<ns0:Message1>
</ns0:Message1>
</ns0:Message>
It is working fine and Idocs are created in mapping in IR.
But the same sample message is creating below output ID!
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge"><ns0:Message1></ns0:Message1></ns0:Messages>
Regards,
Anirudh.

IDoc outbound errors - mail send step in WF to send info-mail to enduser

Hello specialists
I searched quite a lot in the forums now. I found lot of info but nothing regarding my issue.
I need to send an info-mail to the end user creating purchase orders. But only if the idoc (outbound ORDERS) could not be sent (failing for some reason, i.e. if rfc connection fails). This is what I've done to achieve this:
- in WE40 I linked my WF to process code EDIO
- the WF-BATCH user has an email address assigned to it (in SU01)
- the mail sending step in my WF is configured like this:
recipient type = G (organizational object)
Expression = &_WORKITEM.CREATEDBYUSER.ID& (this contains the enduser id)
subject = Test for &WORKITEM.CREATEDBYUSER.ID&
When testing the mail can not be delivered (error SO23).
When setting recipient type to U (E-Mail address) and giving a valid e-mail address, then it works fine (SCOT, etc. is configured and mailing to external systems works). But setting the e-mail address hard coded style in the mail send step is not an option here!
It seems that the send mail step (SELFITEM.SENDTASKDESCRIPTION) always requires a valid e-mail address. Is it not able to handle SAP user id's ?
Thanks in advance for some guideance on this one.
Renaud
Edited by: Renaud Desarzens on Feb 11, 2010 3:00 PM

Hello and thanks for your help.
I was able to solve it like this:
- don't use mail send step
- instead, add new activity with a new task (SELFITEM.SENDTASKDESCRIPTION)
- in the bindings (workflow -> step) set:
B --> &TYPEID&
&_WORKITEM.CREATEDBYUSER.ID& --> &ADDRESSSTRINGS&
Seems that the mail send step doesn't allow TYPEID to be "B" because each time I tried to tweak the generated bindings that way it messed up the recipient type and expression I set before.
Regards
Renaud

Mapping shipment 05 idoc

hi experts,
we have a scenario to map shipment 05 idoc to delivery 05 idoc. there will be one or more handling units in source idoc.for every handling unit in shipment 05 we should map respective article information to seperate delivery 05 idoc. this means foe every e1edl37 segement in source idoc we need to create seperate delivery05 . but the occurence of the imported delivery 05 idoc is 1. so how to map this.. do we need to go for bpm. can anyone please suggest.

Hi,
1)Double Click on the imported IDOC
2)Export the WSDL file to your desktop.
3)Change the max occurrence of the IDOC Segment.
e.g.
Original
<xsd:element name="IDOC" type="CAP_PRIMCOST.CAP_PRIMCOST01" />
Change
<xsd:element name="IDOC" type="CAP_PRIMCOST.CAP_PRIMCOST01" minOccurs="0" maxOccurs="999999999" />
4)Import the new WSDL as an external definition and use it insted of IDOC.
Regards,
Himanshu
Edited by: Himanshu Mohan on Oct 7, 2008 1:55 PM

Message Mapping - JDBC to IDoc

Hi,
I trying to map the resultset from a JDBC adapter (sender) to Inbound IDoc into SAP. I have problems with message mapping and after reading through a number of threads, I followed the following steps:
1. Download the IDoc definition as XSD.
2. Change occurrence of node IDOC to 1..unbounded.
3. Upload changed XSD as external definition and
4. use the external definition in the mapping.
After importing the external XSD definition the IDOC node turned red. How do I map this node, now that it is unbounded?
Example from Message mapping:
MT_ETA_RMX................ZSDETA01
..EtaNode........................IDOC (unbounded = RED)
....CARID.................................BEGIN
...............................................EDI_DC40
...............................................Z1RETA
.................................................SEGMENT
.................................................CARID
Thanks,
Henk

Hendrik,
whichever data record is occuring multiple on your sender JDBC message should be mapped to IDoc segment. It really depends on your JDBC message structure.
If EtaNode is occuring multiple times, and if based on EtaNode an IDoc has to be created, map that to IDOC and if per every CARID one idoc needs to be created, then use CreateIf and exists node functions to IDoc.
regards
SKM

RFC For IDoc outbound processing

I am creating an RFC for BDC for call transaction we19
input as : idoc number
and output:-.. iDoc Outbound processing done
so:-
I go to we19> give iDoc Number (say, some number for ALEREQ01), and execute> click on Outbound processing-->click enter -->enter
in this way, I can process any iDoc from SAP system to outbound.
I want to create RFC for the same.
Problem:-
when i am executing that RFC, and when I check the iDoc status in we05, that iDoc shows status as Idoc ready to dispatch( its in yellow color).. Its not showing green color and not saying that IDoc passed OK
when I try manually ,I see the status green..OK..successfully
Any idea why I am getting this problem??
Is there any problem in my BDC recording?..but when I run that recording for Process, i dont see any problem,it executes successfully.. but when I copy the Code from BDC and make a RFC using that code, its giving problem as mentioned.

Hi Ankit,
Theorotically it should work.... but I'll suggest not to use BDC here. What you can do is,
1. You have Idoc number..Right?
2. Read control record from EDIDC and data record from EDID4.
3. Then call Master_idoc_distribute.
4. This will again distribute the same IDoc with same control and data record as a new one. It will be same as WE19 , but without WE19.
Please check and confirm.
Regards,
Audy.

IDOC Outbound processing using SAP BC

Hello Experts,
I am trying to develop a simple IDOC outbound processing scenario using SAP BC. In this an IDOC from SAP ECC server will be sent to an external webserver via SAP BC, for this i have done all the setup i.e Establishing connection between SAP BC & SAP ECC, ALE settings, creating a new Routing rule, but when i try to run this scenario, i am getting the following error 'IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE' , is there any way to import the IDOC metadata, just like how we do in SAP XI using IDX2. Please Help...
Thanks & Regards,
Amit Naik

Hi Michal,
Following is the error which i am getting :-
2009-03-12 21:56:59 IST com.sap.conn.idoc.IDocMetaDataUnavailableException: (3) IDOC_ERROR_METADATA_UNAVAILABLE: The meta data for the IDoc type "" is unavailable.
 at com.sap.conn.idoc.rt.DefaultIDocDocument.<init>(DefaultIDocDocument.java:132)
 at com.sap.conn.idoc.jco.JCoIDocDocument.<init>(JCoIDocDocument.java:74)
 at com.sap.conn.idoc.jco.JCoIDocDocument.createIDocDocument(JCoIDocDocument.java:117)
 at com.sap.conn.idoc.jco.JCoIDocRuntime.createIDocDocumentList(JCoIDocRuntime.java:83)
 at com.sap.conn.idoc.jco.DefaultJCoIDocServerWorker$IDocDispatcher.handleRequest(DefaultJCoIDocServerWorker.java:88)
 at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:141)
 at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:2621)
 at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2298)
 at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2130)
 at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2012)
 at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:1903)
 at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:258)
 at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:320)
 at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:219)
 at com.wm.util.TimeWrappingProvider$TimeMesuredTask.run(TimeWrappingProvider.java:40)
 at com.wm.pkg.sap.rfc.ListenerThread.run(ListenerThread.java:70)
Thanks & Regards,
Amit

AES filing error - Idoc Outbound Processing: EDI number cannot be compiled

Hi Gurus,
We are configuring the AES filing.
we've done the EDI configI and initally we got the error that EDI partner is not maintained. As per the suggestions from this Forum we've added the cusoms office details in geography tab.
Now when we are trying to process the same, we are getting the error "Idoc Outbound Processing: EDI number cannot be compiled"
All suggestions are welcome.........
Thanks in Advance.

Hi Shiva,
Here goes the solution: you need to maintain the Number of the Number Ranges starting with "10" and this applies only to GTS system as this is HARD-CODED in the Program, apart from 10 any number of the number range will result in an "EDI Number Range compilation" error.
Cheers
Harsha

26 Error during syntax check of IDoc (outbound)

Hi Experts
I am using TPSDLS - Idoc(outbound).
When we view in WE02 : for few of the deliveries it is working fine , but for some it is giving the following error
26 Error during syntax check of IDoc (outbound)
Please any one help me out for the same
Thanks & Regards
Shaveta

Please check the segments for the idocs in error status in WE02. The segments in the idoc should be in the same sequence as defined while creating idoc in WE30.
For eg. taking the case of invoic02 idoc.
Segment E1EDP01 cannot come prior to segment E1EDK01.
As in WE30 it is defined to come after E1EDK01\
Please reward the points if this information is useful.

Mapping : DELVRY03/SHPMNT04 Idoc outbound description

Similar Messages

Maybe you are looking for