Duplicating an IDOC conditionally

Hi,
I am working on a scenario where in the requirement is to duplicate an IDOC conditionally.
The scenario:
<b>File <i>>(User Defined Java Function)</i>> IDOC</b>I receive a fixed length file from a Legacy system and I have to generate one IDOC for every record of the file received. Now, in order to populate the fileds of the IDOC, I have written a large java function to conditionally populate the IDOC fields.
In certain cases, say if Condition 'X' is satisfied, I have to generate 2 IDOC's instead of 1.
I hope the above explains my case.
BPM could have been an option, but I am looking at really huge volumes of data (more than 1,00,000) and hence I wanted to avoid BPM.
Any help on this will be appreciated.
Thanks,
Vijai

Vijai , I doubt if you can do this without a BPM, but if you are worried about calling the transformation(message mapping) inside a BPM , you can definitely avoid it , but u still need a BPM to just route it to ur IDOC adapter.
export your idoc to the file system(Tools -> export XSD), change the "occurence" of the IDOC (add minOccurs = "0" maxOccurs = "unbounded" next to the IDOC node), now import it as an External definition(IDOC package).
Now you can map the incoming file to this IDOC package, call this mapping in the interface determination b/w your file sender & bpm receiver. Now in bpm just send this IDOC package out and receive it in your idoc adapter(will splt this idoc package into ind. idocs and sends it to sap)
-Saravana

Similar Messages

IDoc to IDoc - conditional receiver determination issue

Hello All,
We are using XI 3.0 and this is my scenario:
Sender: IDOC from SAP system
Receivers: There are 2 receivers (one SAP and one non sap system).
I want conditional receiver determination based on the idoc field RCVPRN.
Integration Repository: I imported standard SAP IDOC FIDCC2 into IR and it is in "urn:sap-com:document:sap:idoc:messages" namespace of my SWCV. I am not creating data types, message types or message interfaces as I want to use the IDOC type directly as the interface name in Integration directory.
Integration directory: When I am creating receiver determination, I am getting a warning 'Message interface does not exist in any software components installed on this business system'. When I got to condition editor and want to choose the idoc field RCVPRN using XPATH, it is not showing the idoc structure.
In SLD, the correct product is installed on my sender ABAP technical system, and correct SWCV (into which i imported the IDOC) is installed on my business system. I refreshed cache and cleared SLD cache in ID. Still i get the same warning 'Message interface does not exist in any software components installed on this business system'.
How can i solve this issue? Any help is highly appreciated.
Thanks,
Chandra

Hi Chandra,
Can you check whether you have assigned or linked the SWCV with the Business system in SLD.
Just go to SLD and open the SWCV and check if it is linked with the BS od the sender system.
Since the sender is ABAP, you must have created the TS and BS using rz70, then see that that the SWCV is attached to the BS correctly. Under TS add the Product and then the corresponding SWCV.
Also check one thing: are u selecting the correct Communication component, under which the Interface is present.
Lastly if these doesnot work: In Integration Directory, Go to Environment-> Clear SLD Data Cache. Then try once again.
Cheers,
Souvik
Edited by: Souvik Chatterjee on May 16, 2011 3:39 PM

Condition types doubling/tripling/...when sales documents created with reference to other documents

Hi,
When I create a sales order with reference to a Quote, the pricing condition types are duplicating. Same is happening when subsequent documents like Billing, credit memo request and credit memo are created. Particularly, the condition types are doubled/tripled/.... in the subsequent documents. Because of this, pricing net value is calculated wrong. For example, freight charges getting added twice. I searched the forum and found similar issue was discussed at Condition types - Doubling UP raised by forum member Sridhar Vijjhalwar, however there is no solution added in it.
Has any other member came across this issue and resolved?
I have checked the access sequence and exclusive indicators are checked. Copy controls are also checked, looked good and I tested by adding copying type D/G. Checked OSS note also and found one OSS note 1459807 - Invoice has missing/incorrect conditions when created from a sales order.
but it is not solving the problem either. Issue also elevated to SAP for their investigation. Our system is SAP ECC 6.0 - EHP6.
Quote Pricing:
Sales order Pricing:
I appreciate any pointers to resolve the issue.
Regards,

what was the scenario, and how did you replicate?
It is a configuration for a new project (France country), however we found that the same issue popping up for existing business processes also. As for replicating, we just tried the same procedures, the issue is found in subsequent documents.
If you have observed one notable thing is - all the condition types which duplicated were Z Conditions, and the standard conditions were never duplicated at least in my case.
In our case even standard condition types like MWST, SKTO, GRWR, VPRS also shows duplicating.
if you can throw about the business process?
As you have mentioned order created with reference to quote was only the straight forward scenario?
I tested other scenario also, like creating a sales order, then delivery and then billing. In this case in billing document, the condition types are duplicating. If I create a credit memo request against the billing document, then it further duplicating.
I am not sure what is causing this. I initially thought it may be copy control settings pertaining to the new project, however other business documents also has the same issue. Other business are using different document types.
Thanks for your follow-up.
Regards,

Invoice IDoc

Hi,
I have to customize the output for an invoice idoc. I'm not that much into IDocs and also invoices, so maybe
anybody can halp me out of trouble.
When I go to VF02 to show/change an invoice, and then go to the output, I can choose the output type and
send it as an idoc. The things to do now are, to add some values from the position conditions to the idoc.
Right now just some of the conditions are shown in the idoc, but I have to add several ones also.
Is there any place where I can define, which conditions should be shown in the idoc? for example the "total price"
is not shown. Can I define somewhere that this total price will be added to the idoc condition segment?
Thank you for your help!
Torben

Hi Torben,
First of all you should extend the IDOC that you are sending by adding the additional fields you want to send. For that you will need to create segments with the additional fields. Create an extension of the IDOC. Then add the new segment created to the extension. In transaction WE82, add an entry for the message type, idoc type and the extension created. in WE20 assign the extension to the parter profile. Finally, enhance the function module that is populating the IDOC to populate the additional fields of the extension.
Hope this helps.
Vitz.

IDOC - segment Qualifier

Dear all,
Do you know the transaction or an document which give the link between the Qualifier segment of an segment IDOC and the SAP field ?
for example : IDOC ORDERS05
segment E1EDK03
qualifier 002 : wished delivery date in VA01
segment E1EDK02
qualifier 050 : Delivery Order in segment description but correspond to PO number in VA01
I search to fill in the field PO Date but I don't find the qualifer segment.
Could you please help me ?
thanks
Véronique

Hi friends,
i thing your problem will solve.
E1EDK01 : IDoc: Document header general data
Segment definition E2EDK01005 Released since Release 45B , Segment length: 0357
ACTION : Action code for the whole EDI message
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
KZABS : Flag: order acknowledgment required
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 002, Offset : 0066. external length : 000001
CURCY : Currency
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 003, Offset : 0067. external length : 000003
HWAER : EDI local currency
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 004, Offset : 0070. external length : 000003
WKURS : Exchange rate
internal data type : CHAR
Internal length : 000012 characters
Position in segment : 005, Offset : 0073. external length : 000012
ZTERM : Terms of payment key
internal data type : CHAR
Internal length : 000017 characters
Position in segment : 006, Offset : 0085. external length : 000017
KUNDEUINR : VAT Registration Number
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 007, Offset : 0102. external length : 000020
EIGENUINR : VAT Registration Number
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 008, Offset : 0122. external length : 000020
BSART : Document type
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 009, Offset : 0142. external length : 000004
BELNR : IDOC document number
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 010, Offset : 0146. external length : 000035
NTGEW : Net weight
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 011, Offset : 0181. external length : 000018
BRGEW : Net weight
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 012, Offset : 0199. external length : 000018
GEWEI : Weight unit
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 013, Offset : 0217. external length : 000003
FKART_RL : Invoice list type
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 014, Offset : 0220. external length : 000004
ABLAD : Unloading Point
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 015, Offset : 0224. external length : 000025
BSTZD : Purchase order number supplement
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 016, Offset : 0249. external length : 000004
VSART : Shipping Conditions
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 017, Offset : 0253. external length : 000002
VSART_BEZ : Description of the Shipping Type
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 018, Offset : 0255. external length : 000020
RECIPNT_NO : Number of recipient (for control via the ALE model)
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 019, Offset : 0275. external length : 000010
KZAZU : Order Combination Indicator
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 020, Offset : 0285. external length : 000001
AUTLF : Complete delivery defined for each sales order?
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 021, Offset : 0286. external length : 000001
AUGRU : Order reason (reason for the business transaction)
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 022, Offset : 0287. external length : 000003
AUGRU_BEZ : Description
internal data type : CHAR
Internal length : 000040 characters
Position in segment : 023, Offset : 0290. external length : 000040
ABRVW : Usage Indicator
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 024, Offset : 0330. external length : 000003
ABRVW_BEZ : Description
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 025, Offset : 0333. external length : 000020
FKTYP : Billing category
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 026, Offset : 0353. external length : 000001
LIFSK : Delivery block (document header)
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 027, Offset : 0354. external length : 000002
LIFSK_BEZ : Description
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 028, Offset : 0356. external length : 000020
EMPST : Receiving point
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 029, Offset : 0376. external length : 000025
ABTNR : Department number
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 030, Offset : 0401. external length : 000004
DELCO : Agreed delivery time
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 031, Offset : 0405. external length : 000003
WKURS_M : Indirectly quoted exchange rate in an IDoc segment
internal data type : CHAR
Internal length : 000012 characters
Position in segment : 032, Offset : 0408. external length : 000012
E1EDK14 : IDoc: Document Header Organizational Data
Segment definition E2EDK14 Released since Release 30A , Segment length: 0038
QUALF : IDOC qualifer organization
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
ORGID : IDOC organization
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 002, Offset : 0066. external length : 000035
E1EDK03 : IDoc: Document header date segment
Segment definition E2EDK03 Released since Release 30A , Segment length: 0017
IDDAT : Qualifier for IDOC date segment
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
DATUM : IDOC: Date
internal data type : CHAR
Internal length : 000008 characters
Position in segment : 002, Offset : 0066. external length : 000008
UZEIT : IDOC: Time
internal data type : CHAR
Internal length : 000006 characters
Position in segment : 003, Offset : 0074. external length : 000006
E1EDK04 : IDoc: Document header taxes
Segment definition E2EDK04001 Released since Release 40B , Segment length: 0107
MWSKZ : VAT indicator
internal data type : CHAR
Internal length : 000007 characters
Position in segment : 001, Offset : 0063. external length : 000007
MSATZ : VAT rate
internal data type : CHAR
Internal length : 000017 characters
Position in segment : 002, Offset : 0070. external length : 000017
MWSBT : Value added tax amount
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 003, Offset : 0087. external length : 000018
TXJCD : Tax Jurisdiction
internal data type : CHAR
Internal length : 000015 characters
Position in segment : 004, Offset : 0105. external length : 000015
KTEXT : Text Field
internal data type : CHAR
Internal length : 000050 characters
Position in segment : 005, Offset : 0120. external length : 000050
E1EDK05 : IDoc: Document header conditions
Segment definition E2EDK05001 Released since Release 40A , Segment length: 0185
ALCKZ : Surcharge or discount indicator
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
KSCHL : Condition type (coded)
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 002, Offset : 0066. external length : 000004
KOTXT : Condition text
internal data type : CHAR
Internal length : 000080 characters
Position in segment : 003, Offset : 0070. external length : 000080
BETRG : Fixed surcharge/discount on total gross
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 004, Offset : 0150. external length : 000018
KPERC : Condition percentage rate
internal data type : CHAR
Internal length : 000008 characters
Position in segment : 005, Offset : 0168. external length : 000008
KRATE : Condition record per unit
internal data type : CHAR
Internal length : 000015 characters
Position in segment : 006, Offset : 0176. external length : 000015
UPRBS : Price unit
internal data type : CHAR
Internal length : 000009 characters
Position in segment : 007, Offset : 0191. external length : 000009
MEAUN : Unit of measurement
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 008, Offset : 0200. external length : 000003
KOBTR : IDoc condition end amount
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 009, Offset : 0203. external length : 000018
MWSKZ : VAT indicator
internal data type : CHAR
Internal length : 000007 characters
Position in segment : 010, Offset : 0221. external length : 000007
MSATZ : VAT rate
internal data type : CHAR
Internal length : 000017 characters
Position in segment : 011, Offset : 0228. external length : 000017
KOEIN : Currency
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 012, Offset : 0245. external length : 000003
E1EDKA1 : IDoc: Document Header Partner Information
Segment definition E2EDKA1003 Released since Release 45A , Segment length: 0995
PARVW : Partner function (e.g. sold-to party, ship-to party, ...)
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
PARTN : Partner number
internal data type : CHAR
Internal length : 000017 characters
Position in segment : 002, Offset : 0066. external length : 000017
LIFNR : Vendor number at customer location
internal data type : CHAR
Internal length : 000017 characters
Position in segment : 003, Offset : 0083. external length : 000017
NAME1 : Name 1
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 004, Offset : 0100. external length : 000035
NAME2 : Name 2
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 005, Offset : 0135. external length : 000035
NAME3 : Name 3
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 006, Offset : 0170. external length : 000035
NAME4 : Name 4
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 007, Offset : 0205. external length : 000035
STRAS : Street and house number 1
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 008, Offset : 0240. external length : 000035
STRS2 : Street and house number 2
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 009, Offset : 0275. external length : 000035
PFACH : PO Box
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 010, Offset : 0310. external length : 000035
ORT01 : City
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 011, Offset : 0345. external length : 000035
COUNC : County code
internal data type : CHAR
Internal length : 000009 characters
Position in segment : 012, Offset : 0380. external length : 000009
PSTLZ : Postal code
internal data type : CHAR
Internal length : 000009 characters
Position in segment : 013, Offset : 0389. external length : 000009
PSTL2 : P.O. Box postal code
internal data type : CHAR
Internal length : 000009 characters
Position in segment : 014, Offset : 0398. external length : 000009
LAND1 : Country Key
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 015, Offset : 0407. external length : 000003
ABLAD : Unloading Point
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 016, Offset : 0410. external length : 000035
PERNR : Contact person's personnel number
internal data type : CHAR
Internal length : 000030 characters
Position in segment : 017, Offset : 0445. external length : 000030
PARNR : Contact person's number (not personnel number)
internal data type : CHAR
Internal length : 000030 characters
Position in segment : 018, Offset : 0475. external length : 000030
TELF1 : 1st telephone number of contact person
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 019, Offset : 0505. external length : 000025
TELF2 : 2nd telephone number of contact person
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 020, Offset : 0530. external length : 000025
TELBX : Telebox number
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 021, Offset : 0555. external length : 000025
TELFX : Fax number
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 022, Offset : 0580. external length : 000025
TELTX : Teletex number
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 023, Offset : 0605. external length : 000025
TELX1 : Telex number
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 024, Offset : 0630. external length : 000025
SPRAS : Language key
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 025, Offset : 0655. external length : 000001
ANRED : Form of Address
internal data type : CHAR
Internal length : 000015 characters
Position in segment : 026, Offset : 0656. external length : 000015
ORT02 : District
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 027, Offset : 0671. external length : 000035
HAUSN : House number
internal data type : CHAR
Internal length : 000006 characters
Position in segment : 028, Offset : 0706. external length : 000006
STOCK : Floor
internal data type : CHAR
Internal length : 000006 characters
Position in segment : 029, Offset : 0712. external length : 000006
REGIO : Region
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 030, Offset : 0718. external length : 000003
PARGE : Partner's gender
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 031, Offset : 0721. external length : 000001
ISOAL : Country ISO code
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 032, Offset : 0722. external length : 000002
ISONU : Country ISO code
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 033, Offset : 0724. external length : 000002
FCODE : Company key (France)
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 034, Offset : 0726. external length : 000020
IHREZ : Your reference (Partner)
internal data type : CHAR
Internal length : 000030 characters
Position in segment : 035, Offset : 0746. external length : 000030
BNAME : IDoc user name
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 036, Offset : 0776. external length : 000035
PAORG : IDOC organization code
internal data type : CHAR
Internal length : 000030 characters
Position in segment : 037, Offset : 0811. external length : 000030
ORGTX : IDoc organization code text
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 038, Offset : 0841. external length : 000035
PAGRU : IDoc group code
internal data type : CHAR
Internal length : 000030 characters
Position in segment : 039, Offset : 0876. external length : 000030
KNREF : Customer description of partner (plant, storage location)
internal data type : CHAR
Internal length : 000030 characters
Position in segment : 040, Offset : 0906. external length : 000030
ILNNR : Character field, length 70
internal data type : CHAR
Internal length : 000070 characters
Position in segment : 041, Offset : 0936. external length : 000070
PFORT : PO Box city
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 042, Offset : 1006. external length : 000035
SPRAS_ISO : Language according to ISO 639
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 043, Offset : 1041. external length : 000002
TITLE : Title
internal data type : CHAR
Internal length : 000015 characters
Position in segment : 044, Offset : 1043. external length : 000015
E1EDKA3 : IDoc: Document Header Partner Information Additional Data
Segment definition E2EDKA3 Released since Release 30D , Segment length: 0073
QUALP : IDOC Partner identification (e.g.Dun&Bradstreet number)
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
STDPN : Character field, length 70
internal data type : CHAR
Internal length : 000070 characters
Position in segment : 002, Offset : 0066. external length : 000070
E1EDK02 : IDoc: Document header reference data
Segment definition E2EDK02 Released since Release 30A , Segment length: 0058
QUALF : IDOC qualifier reference document
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
BELNR : IDOC document number
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 002, Offset : 0066. external length : 000035
POSNR : Item number
internal data type : CHAR
Internal length : 000006 characters
Position in segment : 003, Offset : 0101. external length : 000006
DATUM : IDOC: Date
internal data type : CHAR
Internal length : 000008 characters
Position in segment : 004, Offset : 0107. external length : 000008
UZEIT : IDOC: Time
internal data type : CHAR
Internal length : 000006 characters
Position in segment : 005, Offset : 0115. external length : 000006
E1EDK17 : IDoc: Document Header Terms of Delivery
Segment definition E2EDK17 Released since Release 30A , Segment length: 0076
QUALF : IDOC qualifier: Terms of delivery
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
LKOND : IDOC delivery condition code
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 002, Offset : 0066. external length : 000003
LKTEXT : IDOC delivery condition text
internal data type : CHAR
Internal length : 000070 characters
Position in segment : 003, Offset : 0069. external length : 000070
E1EDK18 : IDoc: Document Header Terms of Payment
Segment definition E2EDK18 Released since Release 30A , Segment length: 0089
QUALF : IDOC qualifier: Terms of payment
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
TAGE : IDOC Number of days
internal data type : CHAR
Internal length : 000008 characters
Position in segment : 002, Offset : 0066. external length : 000008
PRZNT : IDOC percentage for terms of payment
internal data type : CHAR
Internal length : 000008 characters
Position in segment : 003, Offset : 0074. external length : 000008
ZTERM_TXT : Text line
internal data type : CHAR
Internal length : 000070 characters
Position in segment : 004, Offset : 0082. external length : 000070
E1EDK35 : IDoc: Document Header Additional Data
Segment definition E2EDK35000 Released since Release 45A , Segment length: 0078
QUALZ : Qualifier for IDoc additional data
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
CUSADD : Data Element Type CHAR Length 35
internal data type : CHAR
Internal length : 000035 characters
Position in segment : 002, Offset : 0066. external length : 000035
CUSADD_BEZ : Character field of length 40
internal data type : CHAR
Internal length : 000040 characters
Position in segment : 003, Offset : 0101. external length : 000040
E1EDK36 : IDOC: Doc.header payment cards
Segment definition E2EDK36000 Released since Release 45A , Segment length: 0114
CCINS : Payment cards: Card type
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 001, Offset : 0063. external length : 000004
CCINS_BEZEI : Description
internal data type : CHAR
Internal length : 000020 characters
Position in segment : 002, Offset : 0067. external length : 000020
CCNUM : Payment cards: Card number
internal data type : CHAR
Internal length : 000025 characters
Position in segment : 003, Offset : 0087. external length : 000025
EXDATBI : IDOC: Date
internal data type : CHAR
Internal length : 000008 characters
Position in segment : 004, Offset : 0112. external length : 000008
CCNAME : Payment cards: Name of cardholder
internal data type : CHAR
Internal length : 000040 characters
Position in segment : 005, Offset : 0120. external length : 000040
FAKWR : Maximum amount
internal data type : CURR
Internal length : 000015 characters
000002 decimal places, without sign
Position in segment : 006, Offset : 0160. external length : 000017
E1EDKT1 : IDoc: Document Header Text Identification
Segment definition E2EDKT1002 Released since Release 45A , Segment length: 0089
TDID : Text ID
internal data type : CHAR
Internal length : 000004 characters
Position in segment : 001, Offset : 0063. external length : 000004
TSSPRAS : Language Key
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 002, Offset : 0067. external length : 000003
TSSPRAS_ISO : Language according to ISO 639
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 003, Offset : 0070. external length : 000002
TDOBJECT : Texts: Application Object
internal data type : CHAR
Internal length : 000010 characters
Position in segment : 004, Offset : 0072. external length : 000010
TDOBNAME : Name
internal data type : CHAR
Internal length : 000070 characters
Position in segment : 005, Offset : 0082. external length : 000070
E1EDKT2 : IDoc: Document Header Texts
Segment definition E2EDKT2001 Released since Release 40A , Segment length: 0072
TDLINE : Text line
internal data type : CHAR
Internal length : 000070 characters
Position in segment : 001, Offset : 0063. external length : 000070
TDFORMAT : Tag column
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 002, Offset : 0133. external length : 000002
E1EDP01 : IDoc: Document Item General Data
Segment definition E2EDP01007 Released since Release 640 , Segment length: 0542
POSEX : Item number
internal data type : CHAR
Internal length : 000006 characters
Position in segment : 001, Offset : 0063. external length : 000006
ACTION : Action code for the item
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 002, Offset : 0069. external length : 000003
PSTYP : Item Category
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 003, Offset : 0072. external length : 000001
KZABS : Flag: order acknowledgment required
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 004, Offset : 0073. external length : 000001
MENGE : Quantity
internal data type : CHAR
Internal length : 000015 characters
Position in segment : 005, Offset : 0074. external length : 000015
MENEE : Unit of measure
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 006, Offset : 0089. external length : 000003
BMNG2 : Quantity in price unit
internal data type : CHAR
Internal length : 000015 characters
Position in segment : 007, Offset : 0092. external length : 000015
PMENE : Price Unit of Measure
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 008, Offset : 0107. external length : 000003
ABFTZ : Agreed cumulative quantity
internal data type : CHAR
Internal length : 000007 characters
Position in segment : 009, Offset : 0110. external length : 000007
VPREI : Price (net)
internal data type : CHAR
Internal length : 000015 characters
Position in segment : 010, Offset : 0117. external length : 000015
PEINH : Price unit
internal data type : CHAR
Internal length : 000009 characters
Position in segment : 011, Offset : 0132. external length : 000009
NETWR : Item value (net)
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 012, Offset : 0141. external length : 000018
ANETW : Absolute net value of item
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 013, Offset : 0159. external length : 000018
SKFBP : Amount qualifying for cash discount
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 014, Offset : 0177. external length : 000018
NTGEW : Net weight
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 015, Offset : 0195. external length : 000018
GEWEI : Weight unit
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 016, Offset : 0213. external length : 000003
EINKZ : Flag: More than one schedule line for the item
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 017, Offset : 0216. external length : 000001
CURCY : Currency
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 018, Offset : 0217. external length : 000003
PREIS : Gross price
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 019, Offset : 0220. external length : 000018
MATKL : IDOC material class
internal data type : CHAR
Internal length : 000009 characters
Position in segment : 020, Offset : 0238. external length : 000009
UEPOS : Higher-Level Item in BOM Structures
internal data type : CHAR
Internal length : 000006 characters
Position in segment : 021, Offset : 0247. external length : 000006
GRKOR : Delivery group (items delivered together)
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 022, Offset : 0253. external length : 000003
EVERS : Shipping instructions
internal data type : CHAR
Internal length : 000007 characters
Position in segment : 023, Offset : 0256. external length : 000007
BPUMN : Denominator for Conv. of Order Price Unit into Order Unit
internal data type : DEC
Internal length : 000005 characters
No decimal places, without sign
Position in segment : 024, Offset : 0263. external length : 000006
BPUMZ : Numerator for Conversion of Order Price Unit into Order Unit
internal data type : DEC
Internal length : 000005 characters
No decimal places, without sign
Position in segment : 025, Offset : 0269. external length : 000006
ABGRU : Reason for rejection of quotations and sales orders
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 026, Offset : 0275. external length : 000002
ABGRT : Description
internal data type : CHAR
Internal length : 000040 characters
Position in segment : 027, Offset : 0277. external length : 000040
ANTLF : Maximum number of partial deliveries allowed per item
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 028, Offset : 0317. external length : 000001
FIXMG : Delivery date and quantity fixed
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 029, Offset : 0318. external length : 000001
KZAZU : Order Combination Indicator
internal data type : CHAR
Internal length : 000001 characters
Position in segment : 030, Offset : 0319. external length : 000001
BRGEW : Total weight
internal data type : CHAR
Internal length : 000018 characters
Position in segment : 031, Offset : 0320. external length : 000018

Preventing IDoc duplication

Hi,
Not sure if this question applies to this forum or if it applies to application server issue but we have 1 receiver SAP ECC and 2 SAP ECC senders of same IDocs because we have connected 2 different systems having same data for test purposes. When both the sender systems send the same data and post as IDoc in receiver system, it causes duplication of IDocs with double records. We are using XI as the middle component between the sending and receiving systems.
My question is, is there any way to prevent this from duplicating the IDocs in receiving system? or What is the best way or how to prevent this duplication of IDocs? Is there a standard function module or BAPI to do this check? Or is there any way to prevent this in XI or sending systems? Does anyone have any other ideas that has worked in this situation?
Thanks,
Sangita

>
Sangita S wrote:
> Hi,
>
> Not sure if this question applies to this forum or if it applies to application server issue but we have 1 receiver SAP ECC and 2 SAP ECC senders of same IDocs because we have connected 2 different systems having same data for test purposes. When both the sender systems send the same data and post as IDoc in receiver system, it causes duplication of IDocs with double records. We are using XI as the middle component between the sending and receiving systems.
>
> My question is, is there any way to prevent this from duplicating the IDocs in receiving system? or What is the best way or how to prevent this duplication of IDocs? Is there a standard function module or BAPI to do this check? Or is there any way to prevent this in XI or sending systems? Does anyone have any other ideas that has worked in this situation?
>
> Thanks,
> Sangita
OK , let me sum up your case ,
You have 2 sender systems , which sends the IDOCS
you have 1 receiver system , which receives the IDOC via XI.
Now due to some reason both sender system creates exactly the same IDOC ( which may be correct from technology point of view ) but I do not see valid business reason for that, anyway it seems just an odd scenario , but the issue is you want to filter out of those 2 similar IDOCS only 1 should go to Target system.
If my understanding is correct of above scenario, XI will not be able to distinguish between these 2 IDOCS as duplicate,unless
You use BPM to collect the IDOCs and remove duplicates before pushing it to Receiver system. This solution may seem too much of a work which is just bcos of testing systems.
So easiest way would be to remove the business reason as why both system are triggering the IDOCs or they may be completely valid.
Thanks,

WAK1 ---- How to send Free Goods details to POS

Gurus,
I have created the free goods data and everything works fine.
When I create a whole sales order , I am getting the free goods.
Now I want to send the information to POS . Can anyone help me how to send this
I tried WPMA , but nothing is working.
What are the IDoc configuration for this . and how to send the free goods information as Idoc.
Hope I have explained my query in a understable manner .
Kindly help in this regard
Regards
Raj

Hi Raj,
Basically, I agree with Christian.
Here's my points:
1. IDoc type WPDBBY is the only standard message type for free goods for POS outbound.
    The detail info about free goods is on segement E1WPBB06 : POS Interface: Condition Scale.
2. Assortment list does have condition type of article sales price (in standard IS-Retail it's VKP0 & VKA0), E1WBB07 : Assortment list IDoc: Conditions per unit of measure & E1WBB08 : Assortment list IDoc: Condition value per unit of meas.
    But it doesn't contain any data for free goods.
3. You could maintain SD free goods condition in a Promotion, but this data is not included in IDoc of promotion WPDREB.
    SD free goods condition is applied for sales order processing only.
Regards,
Steven

Zconversion Field

hi I have an IDOC to file scenerio in the source IDOC there is a Zconversion Segment and having two fields for it and target i have around 6 fields
Zconversion segment
Zfield1
zfield 2
target we have a,b,c,d,..
if zfield 1=a then zfield 2 is mapped with a like same process for remaining target fields.but when iam duplicating IDOC the strcture and if i skiped the any field no field is creating in the target strcture
The logic i have written is
if zfield1=a then zfield 2 is sending the data to target and i used remove context split by each value and mapwith default target field
help me when duplicating the IDoc and skip the Zconversion field For some out put field it is not coming

hi priyanks these soure side Zconversion having two elements and target has employee segment having A,B...F fields
as source is an IDOc abapers are using the Zconversion Segment multiple times for the target a,b,c,..F fields for one record
like Zconversion segment has two elements
Zfield1
zfield 2
If zfield 1 input is A then Zfield2 is mapped with Target Side A field
f zfield 1 input is B then Zfield2 is mapped with Target Side B field
same for all fields when i am duplicating the entire IDOC for second record if i missed B input then target side b field is not creating for second record so FCC issue is occuring

Duplicate row

Problem:
In a table duplicate records are there, i want to retive the rows which are duplicated. What is the query to find out the rows containing the duplicate rows and delete the duplicate one?
Thanks
swadhin

delete from emp where
rowid in ( select max(rowid) from emp group by ename having count(1) > 1);This will not work if you have more than two duplicated rows per condition:
SQL> select * from t;
        ID
         1
         1
         1
         1
         2
         2
         3
         3
         4
9 rows selected.
SQL> delete
2    from t
3   where rowid in
4 (select max(rowid) from t group by id having count(*) > 1);
3 rows deleted.
SQL> select * from t;
        ID
         1
         1
         1
         2
         3
         4
6 rows selected.Rgds.

Populating the Conditions segment in PORDCR102-PO create IDOC

Hi Gurus,
Iam populating some fields in the E1BPMEPOCONDHEADER segment of the IDOC PORDCR102. But the condition record is not getting generated in the PO.
Kindly can anyone throw some light on the mandatory fields that needs to be populated in this segment and is there any necessity to populate some other linked segments along with this segment inorder to get the condition record created.
I am populating some fields below :
E1BPMEPOCONDHEADER-COND_TYPE = 'ZA00'.
E1BPMEPOCONDHEADER-COND_VALUE = '12'.
E1BPMEPOCONDHEADER-CURRENCY = 'USD'.
E1BPMEPOCONDHEADER-CURRENCY_ISO = 'USD'.
E1BPMEPOCONDHEADER-COND_UNIT = 'EA'.
E1BPMEPOCONDHEADER-COND_P_UNT = '1'.
E1BPMEPOCONDHEADER-APPLICATIO = 'EF'.
Please help
Thanks
Venkatesh P

you need to pass
CONDITION_NO
ITM_NUMBER
in 1BPMEPOCONDHEADER and 1BPMEPOCONDHEADERX also..

Populating the Conditions segment in PORDCR101-PO create IDOC

Hi ,
Iam populating some fields in the E1BPMEPOCONDITION segment of the IDOC PORDCR101. But the condition record is not getting generated in the transaction ME22N.Kindly can anyone throw some light on the mandatory fields that needs to be populated in this segment and is there any necessity to populate some other linked segments along with this segment inorder to get the condition record created.
Iam passing the below given fields.
E1BPMEPOCOND-ITM_NUMBER
E1BPMEPOCOND-COND_VALUE
E1BPMEPOCOND-CURRENCY
E1BPMEPOCOND-CURRENCY_ISO
E1BPMEPOCOND-COND_UNIT
E1BPMEPOCOND-COND_P_UNT
E1BPMEPOCOND-CHANGE_ID .
Thanks,
Kittu.

hi,
I am having the same requirement i.e file-xi-r3 create po, can any one tell me the necessary steps needed for this. i am new to all this and still learning things, so please help me.
thank you
email [email protected]

How to create additional Line in file based on condition available as part of ZINVOIC02 Idoc segment

Scenario Details:
Receiving Zinvoic02 Idoc in PI. Idoc to file translation creates comma separated file with .csv extn
The logic was kept in such a way that how many E1EDP01 (items) are available in IDoc that many no of records will be created in csv file.
The file logic for some the fields is as below:
No of records
InvNumber
InvDate
CusNumber
LineitemDesc
Tax1Type
Tax1%
for 1st E1EDP01
E1EDK01-BELNR
E1EDK03-DATUM
E1EDK01-PARTN
Populate when E1EDP04/MSKWZ=O2 or O4 with E1EDP19/KTEXT
Hardcode when E1EDP04/MSKWZ=O2 or O4
Sum all E1EDP04 /MSATZ when E1EDP04/MSKWZ=O2 or O4
for 2nd E1EDP01
E1EDK01-BELNR
E1EDK01-DATUM
E1EDK01-PARTN
same as above
same as above
same as above
for 3rd E1EDP01
E1EDK01-BELNR
E1EDK03-DATUM
E1EDK01-PARTN
same as above
same as above
same as above
Additional Line to be created when one or more of E1EDP01 is having E1EDP04/MSKWZ = O3
same as above
same as above
same as above
Hardcode "REIM for USE TAX"
Hardcode ""
Hardcode ""
Now we have got addition requirement to add a new lineitem when tax code is equal to O3 for any of the E1EDP01.
Is it possible to create additional lineitem based on condition. If yes, please share what should be the approach.
How we can create the additional lineitem?
Currently we are using E1EDP01 to do context handling.
The target structure is :
MT_FILE
     INVOICE     0..unbounded
          InvNumber     0..1
          InvDate          0..1
          CusNumber     0..1
          LineitemDesc     0..1
          Tax1Type          0..1
          Tax1%               0..1

Hello,
Please add one extra field in the data structure of the target mapping and let its occurrence be 0..unbounded under the root node 'MT_ADP_Invoice'.
Apply the condition, if tax code MSKWZ (with its context changed to E1EDP01) equalsS to '03', then map it to the newly created target field whose occurrence is 0..unbounded.
This will then create an additional field which is your requirement.
The above is one way.
But if you want to have the same target field name as ADP_File appended for tax field being '03'.
Then in that case you can you two message mapping for one common operational mapping / interface.
In the first message mapping you need to have one target data structure created with the source data structure remaining the same as the one shown by you in scrn shot. Now this target data structure will be similar to the source, except that you need to add one more field at the end(name different from other fields) in target (whose occurrence should be 0..unbounded), and it needs to be mapped to E1EDP01 provided the tax code field MSKWZ(its context changed to E1EDP01) equalsS to constant '03'.
In the second message mapping you need to map the target structure of previous message mapping to the actual required structure. The newly added field should be mapped to ADP_File of your final target structure.
This will then create the same structure as required.
Note : Please change the occurence of ADP_File to 0..unbounded.
Regards,
Souvik

How to see KSCHL (condition type) in IDOC generated from VA02

Hello,
I have a sales order with positions having
Condition type   Amount   Currency Price Unit
ZPR0                100.00     EUR        1
ZPR0                200.00     EUR        1
If I generate an exit Idoc I can see every field from above except for the value of Condition type.
The received systems needs to have such information.
The only whay I found so far is to hard-code 'ZPRO' in the user exit of the receiving system.
Could anyone suggest me better?
Thanx
Christian

Fill the field in the user exit on the sending system. In this way you can pass table values instead of hard coding.

PO outbound message control - Condition record / PO IDOC outbound user exit

Guys,
I have a system with PO outbound message control sending PO idocs to a unique plant that is set up as a customer in the partner profile. I am using a custom message type and RSEOUT00 to send my idocs with custom message type to this plant. This interface works fine. Now my requirement has changed. I need to send PO's to varying plants (depending on the plant in PO item- all items on my POs belong to same plant).
I noticed that i cannot create condition tables with PO type and Plant combination. (SAP Note 457497 .Q-34).
So I have decided to populate all my PO idocs with a generic receiving partner number '9999' and planning to change this somewhere in a user exit. I found an user exit which looks helpful.
EXIT_SAPLEINM_001 . FM
MM06E001 - Enhancement.
But somehow this exit is not triggered in during PO creation ME21N or change Me22N/Me22.
Is this because I am using a custom message type instead of standard message type ? (I still use the process codes Me10/Me11). Would this matter ? When should this user exit trigger (during creation of idocs in status 30 or when i run RSEOUT00 to sweep these idocs in status 30 to status 03) ? Any tips will be useful.
THanks.
Edited by: Shareen Hegde on Jul 21, 2008 10:13 PM

I found a OSS note -Note 457497 (Q&A # 34), which talks about the same . This was my assumption too. I was just confused because I saw plant(WERKS) in the field catalag of the access sequence.
I don't know what header field I can use to map the plant (I agree its a good idea to do this). But I have decided to do it another way. I will change the receiving partner on the control record depending on the plant in an user exit
- EXIT_SAPLEINM_001.
Thanks for your answer , Mahesh.

Mandatory Fields for IDOC ORDERS01 for Pricing Condition EDI1 to trigger

Hi ,
I'm Testing an Inbound ORDRSP using we 19 for Pricing Conditions EDI1. What are the Mandatory Fields for IDOC ORDERS01
Thanks

hello,
I think it's better to execute VA01 to create a sales order; in that way you should have an idea of mandatory fields.
Thanks.

Duplicating an IDOC conditionally

Similar Messages

Maybe you are looking for