SALESORDER_CREATEFROMDAT2 / SALESORDER_CREATEFROMDAT202

Hi,
This is just requesting a general information / clarification on sales order inbound IDOC.
We are in version ECC 6 and in the process of configuring inbound IDOC. When we had a look on the relevant IDOC version, the SALESORDER_CREATEFROMDAT2 / SALESORDER_CREATEFROMDAT202 seems to be the relevant version. But when we check in the SAP notes or forums I can see lot are mentioned about the IDOC u2013 ORDERS / ORDERS05 and limited for SALESORDER_CREATEFROMDAT2.
I understand that ORDERS05 is using the call transaction method and SALESORDER_CREATEFROMDAT202 is using the BAPI method, just wondering which IDOC to be used for our version and what would be the advantage on a long term basis like SAP support point of view etc.
Also consider we are using heavily customised variant configuration in the sales order.
Regards.

Hi,
I have no experience in this. However as 202 is the latest version, it is always better to go for that version.
I would advise you to look both the versions, find out the difference between them in the segments used, fieds in the segments and the application of additional fields to your need. If you really need those fields which are only in 202, then you can go for it. Otherwise 2 or 202 is not going to make any difference to you for now. At later point of time, if at all you have to add some mroe fields to the segments, the latest version will be of much use to you. Hence my suggestion.

Similar Messages

Texts in IDOC SALESORDER_CREATEFROMDAT2.SALESORDER_CREATEFROMDAT202

Hello,
We are using the IDoc SALESORDER_CREATEFROMDAT2.SALESORDER_CREATEFROMDAT202 for creating Salesorders in our SAP R/3 system. We want to enter texts on header and on item lines in the salesorder with this IDoc. In the IDoc structure there is a segment for text called "E1BPSDTEXT" with different subsegments. I filled these fields with following data:
E1BPSDTEXT
- TEXT_ID 0001
- TEXT_LINE Test Line 1
But when I took a look into the created salesorder, this text didn't appear. Has anyone an idea why this didn't work? Are these the correct fields to get text into a salesorder?
Thanks for help.

Hi Stefan,
Thank you.Your solution was helpful.
Regards,
Dedeepya

Mapping from nested to one table (sales order) XML to IDOC

Hello,
I have to map a xml file to the IDOC SALESORDER_CREATEFROMDAT2.SALESORDER_CREATEFROMDAT202.
How I can map the the longtext from the XML file to the IDOC struktur.
Part of the XML file, there could be n times BPosition with n times longtext. The longtext must be map with a table. I some case its a mapping from nested to mornal table.
 <BPosition>
 <lpos>1</lpos>
 <bbl_sap_nr/>
 <milvonr/>
 <kurztitel/>
 <anzbest/>
 <anzliefer/>
 <kostenpflichtig/>
 <longtext>
 <line>pos1 zeile1</line>
 <line>pos1 zeile 2</line>
 </longtext>
 </BPosition>
thanks for your help.

Hi, I have to map this 1 XML to 1 IDOC
XML:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_Milver xmlns:ns0="http://ccssap.bfi.admin.ch/milver">
 <bestellung>
 <besteller>
 <bestellnr/>
 <auftragdefit/>
 <wempfdebit/>
 <bestelldat/>
 <lieferdat/>
 <anzpos/>
 <language/>
 <adrzeile1/>
 <adrzeile2/>
 <adrzeile3/>
 <adrzeile4/>
 </besteller>
 <Kopf>
 <Lkopf>Kopf1 zeile1</Lkopf>
 <Lkopf>Kopf1 zeile2</Lkopf>
 </Kopf>
 <BPosition>
 <lpos>1</lpos>
 <matnr/>
 <milvonr/>
 <kurztitel/>
 <anzbest/>
 <anzliefer/>
 <kostenpflichtig/>
 <bemerkung>
 <line>pos1 zeile1</line>
 <line>pos1 zeile 2</line>
 </bemerkung>
 </BPosition>
 <BPosition>
 <lpos>2</lpos>
 <matnr/>
 <milvonr/>
 <kurztitel/>
 <anzbest/>
 <anzliefer/>
 <kostenpflichtig/>
 <bemerkung>
 <line>pos2 zeile1</line>
 <line>pos2 zeile 2</line>
 </bemerkung>
 </BPosition>
 </bestellung>
</ns0:MT_Milver>
IDOC:
The Idoc have a segment for the longtext (table).I have to map, lpos, line into E1BPSDTEXT from SALESORDER_CREATEFROMDAT2. Its now more clear?

Mapping Problem. Do I need a UDF?

Hello,
I have the following scenario.
Source File
<ORDER>
<ITEMS>
 <ITEM>
 <NUM>10</NUM>
 <CONDITIONS>
 <CONDITION>
 <TYPE>T1</TYPE>
 <VALUE>V1</VALUE>
 </CONDITION>
 <CONDITION>
 <TYPE>T2</TYPE>
 <VALUE>V2</VALUE>
 </CONDITION>
 </ITEM>
</ITEMS>
</ORDER>
I have to map this to an IDOC with the structure
<E1BPITEM>
<NUM>10</NUM>
</E1BPITEM>
<E1BPCOND>
<NUM>10</NUM>
<TYPE>T1</TYPE>
<VALUE>V1</VALUE>
</E1BPCOND>
<E1BPCOND>
<NUM>10</NUM>
<TYPE>T2</TYPE>
<VALUE>V2</VALUE>
</E1BPCOND>
I am using graphical mapping. everything works well until I have an order with no conditions at all.
in that case in all subsequent orders the NUM fields are mapped incorrectly.
my mapping:
<NUM> ... THIS IS MY PROBLEM
<TYPE> (in context items) -> exists -> createif -> E1BPCOND
<TYPE> (in context items) -> splitbyvalue (each) ->TYPE
<VALUE> (in context items) -> splitbyvalue (each) ->VALUE
Do I need a UDF or can I solve this using graphical mapping? I have never written a UDF that uses Reultlist. what do I need to know?
Thanks,
Yoni

Thanks for the helpful answer. It looks nicer than my graphical mapping but still the same problem. When there is an order with no conditions one SUPPRESS is added to condition type and value queues but not to the NUM queue.
Source XSD:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="com:post:sd:sales" targetNamespace="com:post:sd:sales">
<xsd:element name="sales_new_MT" type="sales_new_DT" />
<xsd:complexType name="sales_new_DT">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
e1cb7e20f38211dcb9b00019bb2d97c0
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="FILE_HEADER">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
2af82de0557311dccef00019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="SYS_CODE" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
2af82de1557311dc87e70019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="HAFK_CASH" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
987d6c00771411dcc5c80019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="HAFK_CH" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
987d6c01771411dcbef00019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="HAFK_CR" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
987d6c02771411dc8ecf0019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="SUM_NO_ORD" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
987d6c03771411dcb4f00019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="WORK_DATE" type="xsd:date">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
987d6c04771411dc8f860019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="MAAZAN" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
987d6c05771411dc8b240019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="SNIF" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
987d6c06771411dcbe960019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ASHNAV" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
987d6c07771411dcc16e0019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ORDERS">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
2af82de4557311dcb4530019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ORDER" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
2af82de5557311dcb61a0019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="SERV_DATE" type="xsd:date" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
2af82de6557311dccabe0019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="PRICE_DATE" type="xsd:date" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
2af82de7557311dca7f20019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="SNIF" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
2af82de8557311dcc78b0019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ASHNAV" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
987d6c08771411dc8b350019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ORDER_ID" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
987d6c09771411dcbfef0019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="USER_ID" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
987d6c0a771411dca75c0019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="INVOICE" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
987d6c0b771411dcc40f0019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ORD_TYPE" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
987d6c0c771411dccc710019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ORD_TEXT" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
987d6c0d771411dcb34c0019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="MAAM_ORDER" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
6d52d3f0ac7811dca1640019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="CUSTOMERS">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
2af82de9557311dca4d70019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="CUSTOMER" minOccurs="0" maxOccurs="10">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
2af82dea557311dc9f370019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="PARTN_ROLE" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
2af82deb557311dc93ef0019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="PARTN_NUMB" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
2af82dec557311dc98400019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="NAME" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
987d6c0e771411dc8c650019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="COUNTRY" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
987d6c0f771411dc9e620019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="CITY" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
987d6c10771411dc856a0019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="POST_CODE1" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
987d6c11771411dcb0840019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="STREET" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
987d6c12771411dc91cd0019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="HOUSE" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
987d6c13771411dc964f0019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="ITEMS">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
2af82ded557311dc94570019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="ITEM" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
2af82dee557311dc9bbd0019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="CONDITIONS" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
ab4c79b0ac7111dc9f0e0019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="CONDITION" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
ab4c79b1ac7111dccbef0019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="COND_TYPE" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
4379b3c0ac7611dc8f8f0019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="COND_VAL" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
4379b3c1ac7611dc80610019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="CNDS" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9fca6e70ce7d11dcb57a0019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="CND" minOccurs="0" maxOccurs="unbounded">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9fca6e71ce7d11dc88aa0019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element name="CNDT" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9fca6e72ce7d11dcb18a0019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="CNDV" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
9fca6e73ce7d11dcb4760019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="MKT_SAP" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
2af82def557311dca2150019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="NUM" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
844eb460c37611dc97ff0019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ITEM_CATEG" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
987d6c14771411dca0a30019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="QTY" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
987d6c15771411dcbf590019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="LEGACY" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
987d6c16771411dcb8e20019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="STOCK" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
6d4040e0ac7911dc8caf0019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="MAAM_ITEM" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
2af82df2557311dc921c0019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="ITEM_TEXT" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
987d6c19771411dc96fa0019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
<xsd:element name="REF_NUMBER" type="xsd:string" minOccurs="0">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
987d6c1a771411dcce450019bb5c48d9
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
Target XSD is IDOC SALESORDER_CREATEFROMDAT2.SALESORDER_CREATEFROMDAT202
with maxoccurs changed for multiple idoc scenario.
sample file (2 orders , first with no conditions and second with 3 conditions):
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<ns0:sales_new_MT xmlns:ns0="com:post:sd:sales">
<FILE_HEADER>
 <WORK_DATE>20080310</WORK_DATE>
 <SYS_CODE>Z02</SYS_CODE>
</FILE_HEADER>
<ORDERS>
 <ORDER>
 <SERV_DATE>20080310</SERV_DATE>
 <SNIF>101</SNIF>
 <ASHNAV>131</ASHNAV>
 <ORDER_ID>20080310101</ORDER_ID>
 <USER_ID>40076416</USER_ID>
 <ORD_TYPE>ZOR1</ORD_TYPE>
 <MAAM_ORDER>A</MAAM_ORDER>
 <CUSTOMERS>
 <CUSTOMER>
 <PARTN_ROLE>AG</PARTN_ROLE>
 <PARTN_NUMB>40000001</PARTN_NUMB>
 </CUSTOMER>
 </CUSTOMERS>
 <ITEMS>
 <ITEM>
 <NUM>10</NUM>
 <MKT_SAP>Z230000163</MKT_SAP>
 <QTY>1</QTY>
 <LEGACY>163</LEGACY>
 <MAAM_ITEM>1</MAAM_ITEM>
 </ITEM>
 </ITEMS>
 </ORDER>
<ORDER>
 <SERV_DATE>20080310</SERV_DATE>
 <SNIF>101</SNIF>
 <ASHNAV>301</ASHNAV>
 <ORDER_ID>20080310101</ORDER_ID>
 <USER_ID>32547747</USER_ID>
 <ORD_TYPE>ZOR1</ORD_TYPE>
 <MAAM_ORDER>A</MAAM_ORDER>
 <CUSTOMERS>
 <CUSTOMER>
 <PARTN_ROLE>AG</PARTN_ROLE>
 <PARTN_NUMB>40000001</PARTN_NUMB>
 </CUSTOMER>
 </CUSTOMERS>
 <ITEMS>
 <ITEM>
 <NUM>10</NUM>
 <MKT_SAP>Z220000060</MKT_SAP>
 <QTY>1</QTY>
 <LEGACY>160</LEGACY>
 <MAAM_ITEM>1</MAAM_ITEM>
 </ITEM>
 <ITEM>
 <NUM>20</NUM>
 <MKT_SAP>Z220000071</MKT_SAP>
 <QTY>1</QTY>
 <LEGACY>171</LEGACY>
 <MAAM_ITEM>1</MAAM_ITEM>
 <CONDITIONS>
 <CONDITION>
 <COND_TYPE>ZST1</COND_TYPE>
 <COND_VAL>433.67</COND_VAL>
 </CONDITION>
 </CONDITIONS>
 </ITEM>
 <ITEM>
 <NUM>30</NUM>
 <MKT_SAP>Z220000074</MKT_SAP>
 <QTY>6</QTY>
 <LEGACY>174</LEGACY>
 <MAAM_ITEM>1</MAAM_ITEM>
 <CONDITIONS>
 <CONDITION>
 <COND_TYPE>ZST1</COND_TYPE>
 <COND_VAL>1296.33</COND_VAL>
 </CONDITION>
 </CONDITIONS>
 </ITEM>
 <ITEM>
 <NUM>40</NUM>
 <MKT_SAP>Z220000075</MKT_SAP>
 <QTY>10</QTY>
 <LEGACY>175</LEGACY>
 <MAAM_ITEM>1</MAAM_ITEM>
 <CONDITIONS>
 <CONDITION>
 <COND_TYPE>ZST1</COND_TYPE>
 <COND_VAL>17221.00</COND_VAL>
 </CONDITION>
 </CONDITIONS>
 </ITEM>
 <ITEM>
 <NUM>50</NUM>
 <MKT_SAP>Z220000076</MKT_SAP>
 <QTY>41</QTY>
 <LEGACY>176</LEGACY>
 <MAAM_ITEM>1</MAAM_ITEM>
 </ITEM>
 </ITEMS>
 </ORDER>
</ORDERS>
</ns0:sales_new_MT>
Thanks,
Yoni

Unable to extend the basic type "SALESORDER_CREATEFROMDAT202"

HI
when iam trying to extend the IDOC basic type "SALESORDER_CREATEFROMDAT202" iam getting an error message "Action is not possiable for generated IDOC types"
To my understanding SALESORDER_CREATEFROMDAT202 is a bapi.So, I guess we can not extend these type of IDOC directly.
Can any one can help me how to copy the BAPI interface and extend it....
or any other solution for this......
can any one can help me reg this.....

I will answer my question!
This is the proble of version we are useing!
the extenction is possiable in sap 4.6 version.
but it is not possiable in ecc6.
So follow the steps i have done
created a new basic type "ZSALESORDER_CREATEFROMDAT202"
where icopy the basic type "SALESORDER_CREATEFROMDAT202" to it
Then i extened the IDOC "ZSALESORDER_CREATEFROMDAT202"
and added the new segments.
FInally while assiging the basic type to extended IDOC given basic type as "SALESORDER_CREATEFROMDAT202"
And assigned to the message type "SALESORDER_CREATEFROMDAT2" to it
then we can use this Structure with
Message type: SALESORDER_CREATEFROMDAT2
Basic type: SALESORDER_CREATEFROMDAT202
Extended:SALESORDER_CREATEFROMDAT202EX
for data picking u can code in the followin function modules:
Function Module for Outbound ALE
ALE_SALESORDER_CREATEFROMDAT2
Function Module for Inbound ALE
IDOC_INPUT_SALESORDER_CREATEFR
There is another method also for this:
create a bapi fm with all the requirements and go to swo1 tc create an object with method as BAPI FM created.then go to TC bdbg and create a bapi ale interface.this will automatically generates the inbound and outbound FM's .Then the idoc will be generated with the added segments...

Unable to Configure Sales Order using SALESORDER_CREATEFROMDAT2

I am using the basic type SALESORDER_CREATEFROMDAT2 02 idoc, created via LSMW, in order to create sales orders. Everything works fine, except for the fact that I cannot set configuration characteristics. The sales order is saved, but when i look at it the value of my characteristic is not set. Can you help me please? Currently I do not know how to generate an idoc of this basic type from an existing order. Knowing how to do this would be a great help.
For my test data, I am only attempting to create one line item (line 10) and configure one characteristic.
Below is a list of the segments being used. I have provided the fields with code for those fields I believe are relevant. I have attempted to process idocs with and without segment E1BPCUPRT. I have also processed idocs with and without the fields E1BPSDITM1-CONFIG_ID, E1BPSDITM1-INST_ID and E1BPSDITM1-MAT_EXT. When these three fields are populated, the order is created but the order line items are dropped. When these three fields are not populated, the order lines created but the characteristic value is not passed to the line item.
Target Structures Used
E1SALESORDER_CREATEFROMDAT2 - Header Segment
 E1BPSDHD1 - Communication Fields: Sales and Distribution Document Header
 E1BPSDHD1X - Checkbox Fields for Sales and Distribution Document Header
 E1BPSDITM - Communication Fields: Sales and Distribution Document Item
 E1BPSDITM1 - Communication Fields: Sales and Distribution Document Item
E1BPSDITM1-CONFIG_ID
Rule Type: Constant
 E1BPSDITM1-CONFIG_ID = '000001'.
E1BPSDITM1-INST_ID
Rule Type: Constant
 E1BPSDITM1-INST_ID = '00000001'.
E1BPSDITM1-MAT_EXT
Rule Type: ABAP Code
 concatenate '0000000000000000000000' E1BPSDITM-MATERIAL into
 E1BPSDITM1-MAT_EXT.
 E1BPSDITMX - Communication Fields: Sales and Distribution Document Item
 E1BPPARNR - Communications Fields: SD Document Partner: WWW
 E1BPSCHDL - Communication Fields for Maintaining SD Doc. Schedule Lines
 E1BPSCHDLX - Checkbox List for Maintaining SD Document Schedule Line
 E1BPCOND - Communication Fields for Maintaining Conditions in the Order
 E1BPCONDX - Communication Fields for Maintaining Conditions in the Order
 E1BPCUCFG - CU: Configuration Data
E1BPCUCFG-POSEX <=== ORDER_ITEM-POSNR
Rule Type: Transfer (MOVE)
 E1BPCUCFG-POSEX = ORDER_ITEM-POSNR.
E1BPCUCFG-CONFIG_ID
Rule Type: Constant
 E1BPCUCFG-CONFIG_ID = '000001'.
E1BPCUCFG-ROOT_ID
Rule Type: Constant
 E1BPCUCFG-ROOT_ID = '00000001'.
E1BPCUCFG-COMPLETE
Rule Type: Constant
 E1BPCUCFG-COMPLETE = 'T'.
E1BPCUCFG-CONSISTENT
Rule Type: Constant
 E1BPCUCFG-CONSISTENT = 'T'.
 E1BPCUINS - Instances of Several Configurations
E1BPCUINS-CONFIG_ID
Rule Type: Constant
 E1BPCUINS-CONFIG_ID = '000001'.
E1BPCUINS-INST_ID
Rule Type: Constant
 E1BPCUINS-INST_ID = '00000001'.
E1BPCUINS-OBJ_TYPE
Rule Type: Constant
 E1BPCUINS-OBJ_TYPE = 'MARA'.
E1BPCUINS-CLASS_TYPE
Rule Type: Constant
 E1BPCUINS-CLASS_TYPE = '300'.
E1BPCUINS-OBJ_KEY
Rule Type: ABAP Code
 * Target Field: E1BPCUINS-OBJ_KEY Object key
 Select single SATNR from MARA into E1BPCUINS-OBJ_KEY
 where BISMT = ORDER_ITEM-BISMT.
E1BPCUINS-QUANTITY <=== ORDER_ITEM-KWMENG
Rule Type: Transfer (MOVE)
 E1BPCUINS-QUANTITY = ORDER_ITEM-KWMENG.
 E1BPCUPRT - Part_of Entries of Several Configurations (Have tried with and without this segment)
E1BPCUPRT-CONFIG_ID
Rule Type: Constant
 E1BPCUPRT-CONFIG_ID = '000001'.
E1BPCUPRT-PARENT_ID
Rule Type: Constant
 E1BPCUPRT-PARENT_ID = '00000001'.
E1BPCUPRT-INST_ID
Rule Type: Constant
 E1BPCUPRT-INST_ID = '00000001'.
E1BPCUPRT-PART_OF_NO
Rule Type: Constant
 E1BPCUPRT-PART_OF_NO = '0010'.
E1BPCUPRT-OBJ_TYPE
Rule Type: Constant
 E1BPCUPRT-OBJ_TYPE = 'MARA'.
E1BPCUPRT-CLASS_TYPE
Rule Type: Constant
 E1BPCUPRT-CLASS_TYPE = '300'.
E1BPCUPRT-OBJ_KEY
Rule Type: ABAP Code
 E1BPCUPRT-OBJ_KEY = E1BPCUINS-OBJ_KEY.
 E1BPCUVAL - Characteristic Values of Several Configurations
E1BPCUVAL-CONFIG_ID
Rule Type: Constant
 E1BPCUVAL-CONFIG_ID = '000001'.
E1BPCUVAL-INST_ID
Rule Type: Constant
 E1BPCUVAL-INST_ID = '00000001'.
E1BPCUVAL-CHARC
Rule Type: ABAP Code
 E1BPCUVAL-CHARC = 'PRG_METRIC'.
E1BPCUVAL-VALUE <=== ORDER_ITEM-ATWRT8
Rule Type: Transfer (MOVE)
 E1BPCUVAL-VALUE = ORDER_ITEM-ATWRT8.
 E1BPCUREF - CU: Reference Order Item / Instance in Configuration
E1BPCUREF-POSEX <=== ORDER_ITEM-POSNR
Rule Type: Transfer (MOVE)
 E1BPCUREF-POSEX = ORDER_ITEM-POSNR.
E1BPCUREF-CONFIG_ID
Rule Type: Constant
 E1BPCUREF-CONFIG_ID = '000001'.
E1BPCUREF-INST_ID
Rule Type: Constant
 E1BPCUREF-INST_ID = '00000001'.
 E1BPSDTEXT - Communication Fields: SD Texts

Hi Paaavan
You can set a break-point include "FV45PFAP_VBAP_BEARBEITEN_VORBE" that is called by both the SAP Standard and BAPI where the data is prepared and checked in the internal table XVBAP. Compare both SAP standard VA01 and your 'Z' program for what may be different in XVBAP.
I think the problem my be with regards to the business_object number that is hardcoded in the standard function module. It has given me issues before and hence I tend to use the function module SD_SALESDOCUMENT_CREATE to create sales documents with.
Regards,
Marius

Should we use ORDER05 or SALESORDER_CREATEFROMDAT2 to place sales orders?

Hello all,
Should we use ORDER05 or SALESORDER_CREATEFROMDAT2 to place sales orders in SAP?
I know ORDERS05 is using call transaction to create it an the other one is using a BAPI.
One was released for version 46C and the other one from 620
It seems as we need to use the second one but I'm not sure the functionality or what is the purpose for this last message type.
My disconcert is just because I was expecting ORDERS06 for new versions...
Thanks in advance.
Jorge Rosa.

You can check OSS Note 550431 - FAQ: BAPI in sales - general questions and Note 550726 - FAQ: BAPIs in sales - restrictions for addition information.
Regards,

Problem in SALESORDER_CREATEFROMDAT2 .

Hi,
I am uploading sales order using BAPI SALESORDER_CREATEFROMDAT2 . How can i upload manual condition type (pricing) , condition rate for each item in this BAPI.
kathir.

Hi create BAPI interface variable like BAPICOND and pass
value according to below code and append in condition table.
WA_CONDITIONS_IN-ITM_NUMBER = <Item no>
WA_CONDITIONS_IN-COND_TYPE = <Cond Type>
WA_CONDITIONS_IN-COND_VALUE = <Cond value>
APPEND WA_CONDITIONS_IN TO INT_CONDITIONS_IN.
CLEAR WA_CONDITIONS_IN.
 WA_CONDITIONS_INX-ITM_NUMBER = LOC_POSNR.
 WA_CONDITIONS_INX-COND_TYPE = WC_X.
 WA_CONDITIONS_INX-COND_VALUE = WC_X.
 APPEND WA_CONDITIONS_INX TO INT_CONDITIONS_INX.
 CLEAR WA_CONDITIONS_INX.
Try This,

IDOC : SALESORDER_CREATEFROMDAT202

Hi everyone,
I am trying to execute the IDOC SALESORDER_CREATEFROMDAT202.
I am getting some dificulties.
I tried to fill the segments but I get an error.
The header segment is E1SALESORDER_CREATEFROMDAT2.
a) How do I fill it : it is not a structure like all the rest of the segments(like E1BPSDHD1,...).
After filling all the data, I called the IDOC_INBOUND_SINGLE function.
The sy-subrc is equal to 0.
But when I go to transaction we05 and check the status of the idoc created, there is a red light.
b) How can I know more information about the erorr ?
Thanks in advance for your help.
Regards.

As stated, go to WE19 and create a template with your basic type SALESORDER_CREATEFROMDAT202. Then, just double click each segment to enter the needed data.
You will also need to populate the control rec (EDIDC rec) by double clicking it. Once you have all the data in each segment, you can click on "Standard Inbound" and process the idoc.
Even if this does not process the first time, after doing this 1x, you will have an idoc number you can use as a copy for re-testing this and the only thing you'll then need to change is whatever value caused your failure.
Also, you can test via the "Inbound Function Module" option and select in debugging mode or in foreground to get more info about your error.

ORDER05 (call transaction) or SALESORDER_CREATEFROMDAT2 (using BAPI)

Hello all,
Should we use ORDER05 or SALESORDER_CREATEFROMDAT2 to place sales orders in SAP?
I know ORDERS05 is using call transaction to create it an the other one is using a BAPI.
One was released for version 46C and the other one from 620
It seems as we need to use the second one but I'm not sure the functionality or what is the purpose for this last message type.
My disconcert is just because I was expecting ORDERS06 for new versions...
Thanks in advance.
Jorge Rosa.
Edited by: Jorge Rosa on Feb 8, 2012 2:46 PM

Hello Jorge,
May be thread in the SD foruns would help you more than database:
http://forums.sdn.sap.com/forum.jspa?forumID=246&start=0
http://forums.sdn.sap.com/forum.jspa?forumID=328&start=0
Regards,
Eduardo Rezende

Material determination wrt SO load using SALESORDER_CREATEFROMDAT2

I'm actually an MM guy looking at an SO load so off my home territory with this one.
When I try loading SOs via LSMW (details as above) with the material set to an 'old' material, then the load fails with message V1 018 Material abc does not exist.
When I try creating an SO manually there are a couple of warning messages VK 157 Material xyz found on the basis of entry abc (reason Old Material) but the material determination is successful and the SO can be saved.
The Condition record looks fine to me, dates OK etc. etc.
Any ideas/past experience of similar issue ?
Thanks,
Nick

JLB,
sorry, I've checked my notes and whatever it was I didn't make a note of it.
Nick

LSMW BAPI Open Sales Order Load - How to update conditions?

Hello gurus,
I was using the BAPI SALESORDER_CREATEFROMDAT2 to upload open sales orders. Wanted to overwrite the default PR00 pricing condition that gets pulled from the customer-material info record, with the price that was existing in the original legacy system when the order was created there. Used the E1BPCOND structure in the Idoc, but since there is no such thing as a E1BPCONDX structure(corresponding to the structure BAPICONDX in the origial BAPI) where you could specify whether the condition should be updated, added or deleted, it adds a second PR00 condition with the legacy system price. The original PR00 condition with the customer-material record price still stays there. Eventhough the order seems to be taking into consideration only the second one I added, to determine the total pricing, I am worried the original sitting there, might cause problems down the document flow. Is there a way to update the existing PR00 condition(rather than adding a new one) on the order, through some flag in the Idoc structure that I am not aware of?
Would greatly appreciate an answer ASAP.
Thanks a lot in advance,
Wayfarer

Thanks and appreciate your taking your time to reply, Gerard, I guess my problem is, we are still on 46C, and the only message type available for this BAPI is SALESORDER_CREATEFROMDAT201. Just called a friend who is on ECC 60 who confirmed that the later version of this message type, SALESORDER_CREATEFROMDAT202 has the E1BPCONDX structure. I don't have that option since on LSMW it automatically defaults to the only message type(and method CREATEFROMDAT2) that is available, when you choose business object BUS2032. Guess I am out of luck, unless you have any other options to suggest.
Thanks,
Wayfarer

Conversion program for the open sales orders

Hi ,
How to proceed for writing a conversion program for open sales order ??
Please share if 've any document or idea.
LSMW object: 0090, Method: 0000
Business Object : BUS2032, Method : CREATEFROMDAT2,
Message Type: SALESORDER_CREATEFROMDAT2
Basic Type: SALESORDER_CREATEFROMDAT202
Regards,
Jyoti Shankar

Dear Saso,
I think, instead using Report: VA05/ VA05N; its better to use Report: VL10C
In this report, you will get all the Sales Orders along with Materials - relevant for open delivery, along with Open Qty. and various other options can be selected from "Change Layout - (Ctrlt+F8)".
Best Regards,
Amit
Note: Don't maintain any Field-Entry (while executing the Report: VL10N; in order to list all Sales Orders. But, if you want to list Sales Orders based upon some criterias, maintain the Field-entries, as reqd.

LSMW Upload SalesOrder Creation:problem in assigning Partner type SH and SP

Hi
I'm trying to upload sales order creation data using LSMW -BAPI Method
Business Object : BUS2032
Method : CREATEFROMDAT2
Message type : SALESORDER_CREATEFROMDAT2
Basic Type : SALESORDER_CREATEFROMDAT202
and I'm passing the following header data
Sales Order Type, Sales organisation, Distribution Channel, Division, Sold To Party, Ship To party,
Purchase order number, PO Date, Requested delivery date, Order Reason, Payment terms, Incoterms part1, Incoterms part2, Document Currency.
and the following item data
MATERIAL NUMBER
Order quantity
Storage Location
Item Category
Item Usage
Reason for Rejection
Plant
Net Weight
Gross Weight
Condition Type
Amount
Internal Order Number
I'm assigning the header data to structure E1BPSDHD1
and Item data to E1BPSDITM,E1BPSDITM1
and Partner data to structure E1BPPARNR.
When I am assigning Partner data to the structure E1BPPARNR, I want to assign both sold-to-party and ship-to-party ,(because I have two source fields of this type) but there is only target field related to the partner data , here I am assigning partner type as SP and partner number as sold-to-party, still there is an unassigned field ship-to-party, for this field I am unable to find a relevant target field so please help me how can I assing These two flat file fields (sold-to-party,ship-to-party)
Looking for further more information : if there is many sold-to-party's and many ship-to-party's how can I go that in this situation i.e maintaining Many to Many relationship using LSMW tool
Thanks in advance
regards
Rajasekhar

Here is what you have to do.
In field mapping, double click on the field PARTN_NUMB (or any field of that structure) in change mode. This opens up the code editor. There just enter the following code. I am assuming you are doing only these fields. But if you are mapping more fields of this structure, you have to map them here.
E1BPPARNR-PARTN_NUMB = ORDERHEADER-KUNAG.
E1BPPARNR-PARTN_ROLE = 'AG'.
E1BPPARNR-ITM_NUMBER = '000000'.
*-- add more field mappings here, if needed
TRANSFER_RECORD.
*-- Now pass the Ship-to record
E1BPPARNR-PARTN_NUMB = ORDERHEADER-KUNWE.
E1BPPARNR-PARTN_ROLE = 'WE'.
E1BPPARNR-ITM_NUMBER = '000000'.
*-- Add more partners if needed by copying the above code.
Remember, you need to do TRANSFER_RECORD only that many times as you have the partners. There will be one 'TRANSFER_RECORD' at the end of this structure, so keep that in mind.
Srinivas

Usage of ALE - idocs generated for BAPIs

Hi
I need to use - the std idocs generated for BUS2032 object - CREATEFROMDAT2 method to store the BAPI call ( BAPI_SALESORDER_CREATEFROMDAT2 )data for those sales orders that could not be created.
If I want to use the SAP delivered BAPI ( BAPI_SALESORDER_CREATEFROMDAT2 ) to call as it within an ABAP program - and then if the call did not go through - then log the data for BAPI into the corresponding idoc with the message type SALESORDER_CREATEFROMDAT2 ( idoc type SALESORDER_CREATEFROMDAT202 ) do I need to move the values from the BAPI structures to the idoc segments programatically ? Or since the idoc is linked to the BAPI - by definition, is there an implicit way to move data to the corresponding idoc segments and save the idoc .
Can anyone out there give me a code sample to do - what I have asked above ?

Hi,
I guess you can use function module ALE_SALESORDER_CREATEFROMDAT2 to create idoc from bapi data. You can pass the entire data in internal tables that you are passing to BAPI into above mentioned function module and then it will create an Idoc for the same. Also populate the receivers in the internal table receiver.
KR Jaideep,

SALESORDER_CREATEFROMDAT2 / SALESORDER_CREATEFROMDAT202

Similar Messages

Maybe you are looking for