VroniPlag Wiki
Assessing the Impact of XML/EDI with Real Option Valuation

von Dr. Shermin Voshmgir

vorherige Seite | zur Übersichtsseite | folgende Seite

Statistik und Sichtungsnachweis dieser Seite findet sich am Artikelende

[1.] Svr/Fragment 061 01 - Diskussion
Zuletzt bearbeitet: 2020-03-20 23:20:29 [[Benutzer:|]]
Fragment, Gesichtet, Norman 1999, SMWFragment, Schutzlevel sysop, Svr, Verschleierung

Typus
Verschleierung
Bearbeiter
Schumann
Gesichtet
Yes.png
Untersuchte Arbeit:
Seite: 61, Zeilen: 1 ff. (completely)
Quelle: Norman 1999
Seite(n): 45, 46, Zeilen: 45: 38 ff.; 46: 1 ff.
A retailer stocks inventory from a major manufacturer. For years this retailer has been ordering merchandise from the manufacturer using a human-readable purchase order such as that in Figure 11 for 1000 fuzzy dice. Now fuzzy dice manufacturer is demanding that the retailer begin using EDI for transactions or surcharge will be added to every order to offset the cost of handling manual transactions. The small retailer can't find a more lenient supplier, so it has little choice.

Svr 061 diss.png

Figure 11: Plain purchase order

Unfortunately, EDI compliance means that the retailer will now have to transmit its purchase orders in a format specified in one of the several standard sets for EDI format, the most widely used being ANSI X12 and UN/EDIFACT. Figure 12 shows part of an ANSI X12 version of the purchase order in Figure 11.

ST*850*12345
BEG*00*SA*3429**981201
N1*BY*Internet Retailer Inc.*91*RET8999
N1*ST*Internet Retailer Inc.
N3*123 Via Way
N4*Milwaukee*WI*53202
PER*OC*John Johnson
PO1**100*EA*1.23*WE*MG*CO633
SE*9*12345

Figure 12: Fragment of ANSI X12 transaction set corresponding to Figure 11

It's possible that the retailer's current accounting software supports EDI transactions, but not likely. It will probably have to either convert to software that [does, purchase software that can make the translation (if available), or contract with a third party to convert the data on an ongoing basis.]

[page 45]

Consider a small, Web-based retailer that stocks inventory from a major manufacturer. For years the company has been ordering merchandise from the manufacturer using a human-readable purchase order such as that in Listing 1, for 1000 fuzzy dice. Now the manufacturer is demanding that the retailer begin using EDI for transactions or else it will add a surcharge to every order to offset the cost of handling manual transactions. The small retailer can’t find a more lenient supplier, so it has little choice.

Listing 1: Plain purchase order

Svr 061 source.png

[page 46]

Unfortunately, EDI compliance means the retailer will now have to transmit its purchase orders in a format specified in one of the several standard sets for EDI format, the most widely used being ANSI X12 and UN/EDIFACT. Listing 2 shows part of an ANSI X12 version of the purchase order in Listing 1. It’s possible that the retailer’s current accounting software supports EDI transactions, but not likely. It will probably have to either convert to software that does, purchase software that can make the translation (if available), or contract with a third party to convert the data on an ongoing basis.

Listing 2: Fragment of ANSI X12 transaction set corresponding to Listing 1

ST*850*12345
BEG*00*SA*3429**981201
N1*BY*Internet Retailer Inc.*91*RET8999
N1*ST*Internet Retailer Inc.
N3*123 Via Way
N4*Milwaukee*WI*53202
PER*OC*John Johnson
PO1**100*EA*1.23*WE*MG*CO633
SE*9*12345

Anmerkungen

The source is not given.

Sichter
(Schumann), SleepyHollow02



vorherige Seite | zur Übersichtsseite | folgende Seite
Letzte Bearbeitung dieser Seite: durch Benutzer:Schumann, Zeitstempel: 20200320232135