Mroczna Przepowiednia / Dar... | Jazz, Soul Blues | Bollywood 2018

XML Orders01

All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.
 74 views
of 9

Please download to get full document.

View again

Description
1 von 10 Who should read this document? This document is for EDI-administrators who will implement this EDI-guide to be able to receive or send XML-IDOC orders from or to Bosch Rexroth AG. Explanation of usage: First of all, the usage of each segment has to be considered, so if a segment is mandatory (M), it has to appear in the data file. It might happen, that a segment itself is optional (O), but the elements wihtin the segment are declared as mandatory. This means, it is not required that t
Share
Tags
Transcript
  1 von 10  Who should read this document? This document is for EDI-administrators who will implement this EDI-guide to be able to receive or send XML-IDOCorders from or to Bosch Rexroth AG. Explanation of usage: First of all, the usage of each segment has to be considered, so if a segment is mandatory (M), it has toappear in the data file.It might happen, that a segment itself is optional (O), but the elements wihtin the segment are declared asmandatory. This means, it is not required that the segment is included, but as soon as the segment is indata file, the mandatory fields must be filled.The same procedure has to be applied to segment groups and segments: A segment group can be optional,while the contained segments are mandatory. In this case all mandatory segments of a segment group hasto apear in the data file, if you decide to use this segment group.The declaration as mandatory of certain segment groups, segments or fields may differ from the description of the standard SAP ORDERS01We have changed the declaration of some elements from optional to mandatory as they are important for our processes.Organizational data such as AG, LF may differ from the examples provided, based on the relevant scenario of a customer or vendor relationship(Incoming ORDERS / outgoing ORDERS) Attention: This message structure is used for both Order messages (ORDERS) and Order Confirmation messages (ORDRSP)!Note that- only MANDATORY (M) segments must contain a value!- each segment/field with MIN > 0 must be created!- with the exception that optional segments (e.g. <E1EDK14 segment=1>) can be completely omitted! If you have questions to this guide, send an e-mail to: [email protected] 2 von 10  tagminmaxO/Mcontent/exampledescription <?xml version= 1.0 encoding= UTF-8 ?> <ORDERS01> 11 <IDOC BEGIN=1> 1-1 <EDI_DC40 SEGMENT = 1> 11M Control record: addressing the message <TABNAM></TABNAM>11EDI_DC40 or empty<MANDT></MANDT>11client<DOCNUM></DOCNUM>11idoc number<DOCREL></DOCREL>11release<STATUS></STATUS>11status of idoc<DIRECT></DIRECT>01O2direction<OUTMOD></OUTMOD>11output mode<EXPRSS></EXPRSS>11overriding in inbound processing<TEST></TEST>11test flag<IDOCTYP></IDOCTYP>11MORDERS01name of basic type<CIMTYP></CIMTYP>11extension<MESTYP></MESTYP>11MEither ORDERS or ORDRSPmessage type<MESCOD></MESCOD>11message code<MESFCT></MESFCT>11message function<STD></STD>11EDI standard, flag<STDVRS></STDVRS>11EDI standard, version<STDMES></STDMES>11message type<SNDPOR></SNDPOR>11sender port<SNDPRT></SNDPRT>11MKUpartner type of sender<SNDPFC></SNDPFC>11MAGpartner funciton of sender<SNDPRN></SNDPRN>11Msender number in target systemsender address<SNDSAD></SNDSAD>11logical address of sender<SNDLAD></SNDLAD>11receiver port<RCVPOR></RCVPOR>11MLIpartner type of recipient<RCVPRT></RCVPRT>11MLFpartner number of recipient<RCVPFC></RCVPFC>11Mrecipient number in own systemrecipient address<RCVPRN></RCVPRN>11logical address of recipient<RCVSAD></RCVSAD>11Msending date (YYYYMMDD)created on<RCVLAD></RCVLAD>11time created<CREDAT></CREDAT>11transmission file<CRETIM></CRETIM>11message group<REFINT></REFINT>11message<REFGRP></REFGRP>11key for external archive<REFMES></REFMES>11serialization<ARCKEY></ARCKEY>11<SERIAL></SERIAL>11 </EDI_DC40><E1EDK01 SEGMENT=1> 11M E1EDK01 : Document header general data <ACTION></ACTION>01 Action code for the whole EDI message<KZABS></KZABS>01 Flag: order acknowledgment required<CURCY></CURCY>11M message currency e. g. EUR Currency<HWAER></HWAER>01 EDI local currency<WKURS></WKURS>01 Exchange rate<ZTERM></ZTERM>01 Terms of payment key<KUNDEUINR></KUNDEUINR>01 VAT registration number<EIGENUINR></EIGENUINR>01 VAT registration number<BSART></BSART>01 Document type<BELNR></BELNR>11M order/order confirmation number IDOC document number<NTGEW></NTGEW>01 Net weight<BRGEW></BRGEW>01 Net weight<GEWEI></GEWEI>01 Weight unit<FKART_RL></FKART_RL>01 Invoice list type<ABLAD></ABLAD>01 Unloading point<BSTZD></BSTZD>01 Purchase order number supplement<VSART></VSART>01 Shipping conditions<VSART_BEZ></VSART_BEZ>01 Description of the shipping type<RECIPNT_NO></RECIPNT_NO>01 Number of recipient (for control via the ALE model)<KZAZU></KZAZU>01 Order combination indicator<AUTLF></AUTLF>01 Complete delivery defined for each sales order?<AUGRU></AUGRU>01 Order reason (reason for the business transaction)<AUGRU_BEZ></AUGRU_BEZ>01 Description<ABRVW></ABRVW>01 Usage indicator<ABRVW_BEZ></ABRVW_BEZ>01 Description<FKTYP></FKTYP>01 Billing category<LIFSK></LIFSK>01 Delivery block (document header)<LIFSK_BEZ></LIFSK_BEZ>01 Description<EMPST></EMPST>01 Receiving point<ABTNR></ABTNR>01 Department number<DELCO></DELCO>01 Agreed delivery time3 von 10  <WKURS_M></WKURS_M>01 Indirectly quoted exchange rate in an IDoc segment </E1EDK01>tagminmaxO/Mcontent/exampledescription<E1EDK14 SEGMENT=1> 0-1O E1EDK14 : Document Header Organizational Data <QUALF></QUALF>11 IDOC qualifer organization<ORGID></ORGID>11 IDOC organization </E1EDK14><E1EDK03 SEGMENT=1> 2-1M E1EDK03 : Document header date segment <IDDAT></IDDAT>11O001 = order date Qualifier for IDOC date segmentM002 = requested delivery dateO011 = creation dateM012 = document dateO013 = quotation date supplier<DATUM></DATUM>11 Date<UZEIT></UZEIT>01 Time </E1EDK03><E1EDK04 SEGMENT=1> 0-1O E1EDK04 : Document header taxes <MWSKZ></MWSKZ>01 VAT indicator<MSATZ></MSATZ>11M VAT rate<MWSBT></MWSBT>11M Value added tax amount<TXJCD></TXJCD>01 Jurisdiction for tax calculation - tax jurisdiction code<KTEXT></KTEXT>01 Text Field </E1EDK04><E1EDK05 SEGMENT=1> 0-1O E1EDK05 : Document header conditions <ALCKZ></ALCKZ>01 Surcharge or discount indicator<KSCHL></KSCHL>01 Condition type (coded)<KOTXT></KOTXT>01 Condition text<BETRG></BETRG>01 Fixed surcharge/discount on total gross<KPERC></KPERC>01 Condition percentage rate<KRATE></KRATE>01 Condition record per unit<UPRBS></UPRBS>01 Price unit<MEAUN></MEAUN>01 Unit of measurement<KOBTR></KOBTR>01 IDoc condition end amount<MWSKZ></MWSKZ>01 VAT indicator<MSATZ></MSATZ>01 VAT rate4 von 10
Related Search
We Need Your Support
Thank you for visiting our website and your interest in our free products and services. We are nonprofit website to share and download documents. To the running of this website, we need your help to support us.

Thanks to everyone for your continued support.

No, Thanks