| Billing
and Payments Models Index - Current Scenarios to be Recast
into Component Models |
| Business
Documents |
Description |
X12 -
EIDX |
EDIFACT
- EDIFICE (*) |
RosettaNet |
OAGIS 8.0 |
|
Billing and Payment Model
1 (BP1) - Standard Invoice - to be developed |
| Invoice |
To request
payment for goods or services. |
810 |
INVOIC |
3C3 |
Process
Invoice |
| Business
Documents |
Description |
X12 -
EIDX |
EDIFACT
- EDIFICE (*) |
RosettaNet |
OAGIS
8.0 |
|
Billing and Payment Model 2 (BP2) - Standard
Payment Order - to be developed |
| Payment Order |
To convey an
order to make a payment. |
820 |
PAYORD |
None |
tbd |
| Business
Documents |
Description |
X12 -
EIDX |
EDIFACT
- EDIFICE (*) |
RosettaNet |
OAGIS
8.0 |
|
Billing and Payment Model 3 (BP3) - Standard
Payment Advice - to be developed |
| Payment Advice |
To convey confirmation
that a payment has been made. |
820 |
PAYORD |
3C6 |
tbd |
| Business
Documents |
Description |
X12 -
EIDX |
EDIFACT
- EDIFICE (*) |
RosettaNet |
OAGIS
8.0 |
|
Billing and Payments Model 4 (BP4) - Automated
Clearing House (ACH) Payment |
| Automated
clearing house transactions are bank-to-bank exchanges and
out of scope for EIDX. |
| Business
Documents |
Description |
X12 -
EIDX |
EDIFACT-
EDIFICE (*) |
RosettaNet |
OAGIS
8.0 |
|
Billing and Payment Model 5 (BP5) - Standard
Remittance Advice - to be developed |
| Remittance
Advice |
To convey confirmation
that a payment has been made. |
820 |
REMADV |
3C6 |
tbd |
| Business
Documents |
Description |
X12 -
EIDX |
EDIFACT
- EDIFICE (*) |
RosettaNet |
OAGIS
8.0 |
|
Billing and Payment Model 6 (BP6) - Remittance
Advice, CCD Total Only - to be developed |
| Remittance
Advice - CCD Only |
To convey confirmation
that a payment has been made. |
820 |
REMADV |
3C6 |
tbd |
| Business
Documents |
Description |
X12 -
EIDX |
EDIFACT
- EDIFICE (*) |
RosettaNet |
OAGIS
8.0 |
|
Billing and Payments Model 7 (BP7) - Automated
Clearing House (ACH) Transfer |
| Automated
clearing house transactions are bank-to-bank exchanges and
out of scope for EIDX. |
| Business
Documents |
Description |
X12 -
EIDX |
EDIFACT
- EDIFICE (*) |
RosettaNet |
OAGIS
8.0 |
|
Billing
and Payment Model 8 (BP8) - Self-billing Invoice - to be
developed |
| Self-billing
Invoice |
tbd |
tbd |
INVOIC |
3C7 |
tbd |
|
|
| Debits
and Credits Models Index - Current Scenarios to be Recast
into Component Models |
| Business
Documents |
Description |
X12 -
EIDX |
EDIFACT
- EDIFICE (*) |
RosettaNet |
OAGIS
8.0 |
|
Debits and Credits Model 1 (DC1) - Credit
Memo/Advice - to be developed |
| Credit Memo/Advice |
Credit adjustment. |
812 |
Included
in INVOIC |
3C3 |
Show
Credit |
| Business
Documents |
Description |
X12 -
EIDX |
EDIFACT
- EDIFICE (*) |
RosettaNet |
OAGIS
8.0 |
|
Debits and Credits Model 2 (DC2) - Generic
Debit Authorization - to be developed |
| Debit Authorization |
To authorize
a bank to execute a debit transaction. |
828 |
AUTHOR |
tbd |
tbd |
| Cancel Debit
Authorization |
To notify a
bank that the authorization to execute a debit transaction
is revoked. |
829 |
FINCAN |
tbd |
tbd |
|
Debits and Credits Model 3 (DC3) - Generic
Debit Advice - to be developed |
| Debit Advice |
Notifies an
account owner that their account will be or has been debited
for a specified amount of money at a specified date/time, in
settlement of a referenced business transaction. |
824 |
DEBADV |
tbd |
tbd |
| Business
Documents |
Description |
X12 -
EIDX |
EDIFACT
- EDIFICE (*) |
RosettaNet |
OAGIS
8.0 |
|
Debits and Credits Model 4 (DC4) - Automated
Clearing House (ACH) Debit Order |
| Automated
Clearing House transactions are bank-to-bank exchanges and
out of scope for EIDX. |
| Business
Documents |
Description |
X12 -
EIDX |
EDIFACT
- EDIFICE (*) |
RosettaNet |
OAGIS
8.0 |
|
Debits
and Credits Model 5 - Debit Claim Process |
| Debit Claim
Request |
To request
(claim) a debit as authorized. |
844 |
SSDCLM |
5D5 |
None |
| Response to
Debit Claim Request |
To confirm
or deny an SSD claim. |
849 |
SSDRSP |
5D5 |
None |
| Business
Documents |
Description |
X12 -
EIDX |
EDIFACT
- EDIFICE (*) |
RosettaNet |
OAGIS
8.0 |
|
Debits
and Credits Model 6 - Debit Award |
| Debit Award |
Allows a seller
to notify a distributor that it qualifies for and may take
a debit. |
812 |
Included
in INVOIC |
None |
None |
| Business
Documents |
Description |
X12 -
EIDX |
EDIFACT
- EDIFICE (*) |
RosettaNet |
OAGIS
8.0 |
|
Debits
and Credits Model 7 - Credit Claim Process |
| Credit Claim
Notification |
Allows sender
to request that the recipient issue a credit. In Ship-from-Stock
and Debit, allows a seller to notify a distributor that an
SSD debit is being billed-back due to product return. |
812 |
Included
in INVOIC |
None |
None |
| Response to
Credit Claim Notification |
For credit claim
recipient to notify requestor of the disposition of a credit
claim; may be used for all credit claims or on exception basis
when the credit claim could not be processed and reason for
error. |
812 |
None |
None |
None |
| Business
Documents |
Description |
X12 -
EIDX |
EDIFACT
- EDIFICE (*) |
RosettaNet |
OAGIS
8.0 |
|
Debits
and Credits Model 8 - Credit Advice |
| Credit Advice |
For distributor
to notify supplier that a debit is being backed out. |
812 |
None |
None |
None |
| Business
Documents |
Description |
X12 -
EIDX |
EDIFACT
- EDIFICE (*) |
RosettaNet |
OAGIS
8.0 |
|
Debits
and Credits Model 9 - Design Win Claim Process |
| Design Win
Claim |
For distributor
to tell a supplier that criteria for a Design Win incentive
award have been met. |
tbd |
tbd |
5C3 |
None |
| Response to
Design Win Claim |
To confirm
or deny a Design Win claim. |
812 |
None |
5C3, 5C4 n1 |
None |
| |
Note
1: Only one response to the original Design Win Claim
may be sent using PIP5C3. Subsequent responses must be
sent using PIP5C4. |
| Business
Documents |
Description |
X12 -
EIDX |
EDIFACT
- EDIFICE (*) |
RosettaNet |
OAGIS
8.0 |
|
Debits
and Credits Model 10 - Direct Debit Order |
| Direct Debit
Order |
To convey an
order to claim a debit from another account and have it credited
to the requestor's account. |
820 |
DIRDEB |
None |
tbd |
| Generic
Models Index |
| Business
Documents |
Description |
X12 -
EIDX |
EDIFACT
- EDIFICE (*) |
Rosetta
Net |
OAGIS
7.1 |
| Service Segments/
Message Envelopes |
Protocols for
enveloping an electronic message. |
ISA/GS |
SERSEG |
RNIF |
ebXML |
|
Generic
Request/Response Transmission Tracking and Error Handling |
| Message Receipt
Acknowledg-ment |
Signal to indicate
that an electronic transmission has been received; usually
includes information indicating whether received transaction
passed syntactical compliance test. |
997 |
CONTRL |
RNIF |
Confirm
BOD |
| Exception Notice |
Notification
of an exception condition such as a notification that some
business activity is overdue or to report results of an application
system's data content edits of an electronic message. |
814 or 824 |
APERAK |
01A |
tbd |
| Forecast/Planning
Models Index |
| Business
Documents |
Description |
X12 -
EIDX |
EDIFACT
- EDIFICE (*) |
Rosetta-Net |
OAGIS
8.0 |
|
Forecast/Planning
Model 1 (FC1) - Planning Forecast |
| Planning Forecast |
n1
Data
Contents/ Class Diagram |
830
Example
|
DELFOR |
4A4 |
Show
Planning Schedule |
| Response to
Forecast |
n2 |
"830R" |
DELFOR |
4A5 |
Show
Planning Schedule |
| |
Note
1: Used to convey schedules of planned deliveries. Also
called "Net Requirements." Buyer generates
planning/delivery schedule (net rolling forecast) for information
only and capacity or lead time planning purposes, to convey
anticipated demand or run rates; no authorization to build
or ship implied except per trading partner agreement.
Note 2: Used to convey response schedules
of planned deliveries. Forecast recipient provides response for
agreed-upon horizon of the forecasted demand and planned shipments
as outlined in the trading partner agreement. Trading partner
agreement includes conditions for which response is required, e.g.
exceptions-only vs. response to all schedules, respond to all transmissions
vs. respond only when-needed. |
| Business
Documents |
Description |
X12 -
EIDX |
EDIFACT
- EDIFICE (*) |
Rosetta-Net |
OAGIS
7.1 |
| Forecast
Model 2 (FC2) - Material Release Schedule |
| Material Release
Schedule - "Embedded Release" |
Used to convey
firm (released requirements) ("embedded release")
as well as schedules of planned deliveries. |
830
Example |
DELFOR |
4A4 |
tbd |
| Response to
Planned Schedules in Material Release Schedule |
Used to convey
response schedules of planned deliveries (may be exceptions
or response to all schedules). |
"830R" |
DELFOR |
4A5 |
tbd |
| Response to
Firm Schedules in Material Release Schedule |
Used to convey
response schedules of planned deliveries (may be exceptions
or response to all schedules). |
855 |
DELFOR |
tbd |
tbd |
| Business
Documents |
Description |
X12 -
EIDX |
EDIFACT
- EDIFICE (*) |
Rosetta-Net |
OAGIS
7.1 |
| Forecast
Model 3 (FC3) - Consumption (Planned Usage) Forecast |
| Con-sumption
(Planned Usage) Forecast - Supplier-Managed Inventory Forecast |
Used to convey
schedules of planned consumption (usage or sales). Also
called "Gross Requirements". |
830
Example |
DELFOR |
4A3 |
tbd |
| Response to
Con-sumption (Planned Usage) Forecast |
Used to convey
response to schedules of planned consumption (usage or sales)
(may be exceptions or response to all schedules). |
"830R" |
DELFOR |
4A5 |
tbd |
| Business
Documents |
Description |
X12 -
EIDX |
EDIFACT
- EDIFICE (*) |
Rosetta-Net |
OAGIS
7.1 |
| Forecast
Model 4 (FC4) - Replenishment Schedule |
| Replenish-ment
Schedule |
Used in an SMI process
to convey the supplier's plan for replenishing the buyer's
inventory. |
870 |
OSTRPT |
tbd |
tbd |
| Response to
Replenish-ment Schedule |
Used to respond
to supplier's plan for replenishing buyer's inventory. May
be used to report exceptions such as anticipated violation
of minimum and maximum inventory targets. |
tbd |
tbd |
tbd |
tbd |
| Business
Documents |
Description |
X12 -
EIDX |
EDIFACT
- EDIFICE (*) |
Rosetta-Net |
OAGIS
7.1 |
| Forecast
Model 5 (FC5) - Strategic Forecast - to be developed |
| Strategic Forecast |
n3 |
830 |
DELFOR |
4A1 |
tbd |
| Response to
Strategic Forecast |
tbd |
tbd |
tbd |
tbd |
tbd |
| |
Note
3: RosettaNet calls this "Strategic Forecast," CPFR
calls it "Sales Forecast." |
| Inventory
Management Models Index |
| Business
Documents |
Description |
X12 -
EIDX |
EDIFACT
- EDIFICE (*) |
Rosetta-Net |
OAGIS
8.0 |
|
Inventory
Model 1 (INV1) - Report Inventory Levels - Buyer to Seller |
| Inventory Report |
Used to report
inventory levels, inventory movements. |
846 |
INVRPT |
4C1 |
List
Inventory Count or Show Inventory
Count |
| Seller Notification
of Inventory Report |
Notifies seller
that an inventory has been posted to a repository or external
application. |
None |
None |
None |
Show
Inventory Count n1 |
| Buyer Notification
of Inventory Report |
Notifies buyer
that an inventory report has been successfully posted to a
repository or VPN application,
and that that a notification has been sent to the seller. |
None |
None |
None |
None |
| Response to
Inventory Levels Report |
Used to report
errors in the inventory report. |
None |
None |
None |
None |
| |
Note 1: E-mail
notification used; assumes seller does not have an integrated
B2B solution. |
| Business
Documents |
Description |
X12 -
EIDX |
EDIFACT
- EDIFICE (*) |
Rosetta-Net |
OAGIS
8.0 |
| Inventory
Model 2 (INV2) - Report Transfer or Resale with Customer
Detail |
| Sales Report
with Customer Detail |
Sent by a reseller
or distributor to a supplier or manufacturer to report sales
of goods to end customers. |
867 |
SLSRPT |
tbd |
tbd |
| Business
Documents |
Description |
X12 -
EIDX |
EDIFACT
- EDIFICE (*) |
Rosetta-Net |
OAGIS
8.0 |
| Inventory Model
3 (INV3) - Report Consumption or Resale - No Customer Detail |
| Inventory Sales/Activity
Report |
Used primarily
in retail when reference not made to specific end-customer;
allows combined sales and inventory data; allows some granularity
on inventory activity such as quantity on hand, quantity in
transit, quantity sold, beginning and ending balances, additional
demand, etc. |
852 |
INVRPT |
tbd |
tbd |
| Business
Documents |
Description |
X12 -
EIDX |
EDIFACT
- EDIFICE (*) |
Rosetta-Net |
OAGIS
8.0 |
| Inventory
Model 4 (INV4) - Report Inventory Consumption - Buyer to
Seller |
| Report Inventory
Consumption |
Used to report
inventory consumption in order to trigger billing. |
852 |
INVRPT |
4B3 |
tbd |
| Business
Documents |
Description |
X12 -
EIDX |
EDIFACT
- EDIFICE (*) |
Rosetta-Net |
OAGIS
8.0 |
| Inventory
Model 5 (INV5) - Report Availability - Seller to Buyer |
| Request Product
Availability |
tbd |
tbd |
tbd |
tbd |
Show
Product Availability |
| Report Product
Availability |
tbd |
tbd |
INVRPTSD |
4C1 + 2A12 |
Get
Product Availability |
| Business
Documents |
Description |
X12 -
EIDX |
EDIFACT
- EDIFICE (*) |
Rosetta-Net |
OAGIS
8.0 |
| Inventory
Model 6 (INV6) - Report Shipment of Goods - to be developed |
| Ship Notice |
Used by seller
or seller's agent to notify buyer or buyer's agent that goods
have been shipped. |
856 |
DESADV |
3B2 |
Show
Shipment |
| Business
Documents |
Description |
X12 -
EIDX |
EDIFACT
- EDIFICE (*) |
Rosetta-Net |
OAGIS
8.0 |
| Inventory
Model 7 (INV7) - Report Receipt of Goods - to be developed |
| Receipt Advice |
Used by buyer
or buyer's agent to notify seller or seller's agent that shipped
goods have been received. |
861 |
RECADV |
4B2 |
Show
Delivery Receipt |
| Business
Documents |
Description |
X12 -
EIDX |
EDIFACT
- EDIFICE (*) |
Rosetta-Net |
OAGIS
8.0 |
| Inventory
Model 8 (INV8) - Warehouse Stock Transfer |
| Warehouse Inventory
Transfer Shipment Advice |
Used by a depositor
(the warehouse's client) to advise the warehouse that something
is being shipped to them.
The shipment may be from the client's customer or supplier,
or from the depositor's own warehouse. |
943 |
DESADV |
3B2 |
Show
Shipment |
| Warehouse Inventory
Transfer Receipt Advice |
Used by a warehouse
to advise the depositor that inventory shipped to the warehouse
has been received. |
944 |
RECADV |
4C3 |
Acknowledge
Delivery Receipt |
| Business
Documents |
Description |
X12 -
EIDX |
EDIFACT
- EDIFICE (*) |
Rosetta-Net |
OAGIS
8.0 |
| Inventory
Model 9 (INV9)- Warehouse Shipping Order |
| Shipment Order |
Used by a depositor
(the warehouse's client) to advise the warehouse to make a
shipment, confirm a shipment, or modify or cancel a previously
transmitted shipping order.
The shipment order may request that the warehouse ship
to the depositor's customer or supplier, or to the depositor's
own warehouse. |
940 |
ORDERS |
3B12 |
tbd |
| Warehouse Shipment
Notification |
Used by a warehouse
to advise a client that the shipment has been made in response
to a Warehouse Shipping Order. |
945 |
DESADV |
3B12 |
Show
Shipment |
| Warehouse Inventory
Transfer Receipt Advise |
Used by a warehouse
to advise the depositor that inventory shipped to the warehouse
has been received. |
944 |
RECADV |
4C3 |
Acknowledge
Delivery Receipt |
| Business
Documents |
Description |
X12 -
EIDX |
EDIFACT
- EDIFICE (*) |
Rosetta-Net |
OAGIS
8.0 |
Inventory
Model 10 (INV10) - Warehouse Inventory Adjustment |
| Inventory Adjustment |
Used to inform
a warehouse or depositor of a quantity or status change to
inventory records. |
947 |
INVRPT |
4C1 |
List
Inventory Count or Show Inventory
Count |
| Business
Documents |
Description |
X12 -
EIDX |
EDIFACT
- EDIFICE (*) |
Rosetta-Net |
OAGIS
8.0 |
| Inventory
Model 11 (INV11) - Report Inventory Levels - Distributor to
Component Supplier - to be developed |
| tbd |
tbd |
tbd |
tbd |
tbd |
tbd |
| Order
Models Index |
| Business
Documents |
Description |
X12 -
EIDX |
EDIFACT
- EDIFICE (*) |
Rosetta-Net |
OAGIS
8.0 |
|
Order
Model 1 (ORD1) - Traditional Stand-Alone PO, Buyer is Established
Customer |
| Purchase Order
(Discrete) |
Used to convey
a one-time commitment to purchase goods.
Data
Contents/ Class Diagram |
850
Example |
ORDERS |
3A4 n1 |
Process
Purchase Order |
| Seller Notification
of Purchase Order |
Notifies seller
that a purchase order has been posted to a repository or external
application. |
None |
None |
None |
Show
Purchase Order n2 |
| Buyer Notification
of Purchase Order |
Notifies buyer
that a purchase order has been successfully posted to a repository
or VPN application,
and that that a notification has been sent to the seller. |
None |
None |
None |
Show
Purchase Order
n2 |
| PO Response
(a/k/a PO Confirmation) Response |
Used to acknowledge
(confirm acceptance or rejection) of a Purchase Order. |
855, 856,
or 810
n3 n4 |
ORDRSP, DESADV,
or INVOIC |
3A4, 3A7
n1 n3 n5 |
Acknowledge
Purchase Order, Show Shipment,
or Process Invoice |
| Purchase Order
Change |
Used to convey
buyer's requested changes to a Purchase Order. |
860 |
ORDCHG |
3A8 |
Change Purchase
Order |
| PO Change Response |
Seller response
to requested change to Standalone Purchase Order. |
855 or 865
n4 |
ORDRSP |
3A8, 3A7
n6 |
Acknowledge
Purchase Order |
| Seller-Initiated
PO Change |
Seller-requested
changes may be sent to the buyer. |
865 |
ORDRSP |
3A7 n7 |
tbd |
| Acceptance
Response to Seller-Initiated Change Request |
Used when buyer
to respond to seller-initiated PO Change Request which accepts
or counter-proposes seller-initiated changes |
860 |
ORDCHG |
3A8 n8 |
Change Purchase
Order |
| Denial Response
to Seller-Initiated Change Request |
Used when a
buyer is denying (rejecting) a seller-initiated change. |
860 |
ORDCHG
|
3A8 n8
|
Change Purchase
Order |
| Purchase Order
Cancellation |
Used to convey
requested changes to a Purchase Order. Used also for
buyer to respond to seller-initiated PO Change Request which
accepts or counterproposes seller-initiated changes |
860 |
ORDCHG |
3A9 |
Cancel Purchase
Order |
| |
Note 1: PIP requires
that PO Confirmation be used to respond PO.
Note 2: E-mail notification used;
assumes seller does not have an integrated B2B solution.
Note 3: If goods are
shipped immediately, a ship notice or invoice is considered
a de facto order acceptance, and it is not necessary
to send a separate PO response document. However,
in the RosettaNet standard, a PO response is required
regardless.
Note 4: Although the
X12 standard has a separate response transaction for
the 860, the 865, an 855 may be sent in response to
an 860.
Note 5: Only one acknowledgment
to the original PO may be sent using PIP3A4. Subsequent
acknowledgments must be sent using PIP3A7.
Note 6: Only one acknowledgment
to the original PO may be sent using PIP3A4. Subsequent
acknowledgments must be sent using PIP3A7.
Note 7: PIP3A7 does not
require the buyer to send a response to the seller's
proposed change. Trading partners need to agree
on expectations and on whether a non-response should
be treated as an acceptance or a denial. EIDX
recommends that a non-response be treated as a denial,
since many buyers' applications only allow them to
transmit a response if the buyer changes its own data;
in a denial, the buyer is not changing its data.
Note 8: PIP 3A8 requires
that PO Change Confirmation be used with PO Change. So
even when a seller- initiated response using PIP 3A7
is responded to with a 3A8 PO Change, the PIP requires
that the seller must send a 3A8 PO Confirmation, even
though it is redundant. Note 7: Only one acknowledgment
to the original PO may be sent using PIP3A4. Subsequent
acknowledgments must be sent using PIP3A7. |
| Business
Documents |
Description |
X12 -
EIDX |
EDIFACT
- EDIFICE (*) |
Rosetta-Net |
OAGIS
8.0 |
| ORD2
- Blanket Purchase Order, Specified Product, Buyer is Established
Customer |
| Purchase Order
(Blanket) |
Buyer generates
blanket order to convey a long-term commitment to purchase
goods. |
850
Example |
ORDERS BORDERS guideline |
tbd n9 |
tbd n10 |
| Blanket Order
Response |
Seller response
to Blanket Purchase Order or Change to Blanket Purchase Order
with Purchase Order Response/Acknowledgment. |
855 |
ORDRSP |
tbd n9 |
tbd n10 |
| Blanket Order
Change |
Used to convey
buyer's requested changes to a Blanket Purchase Order. |
860 |
ORDCHG |
tbd |
tbd n10 |
| BPO Change
Response |
Seller response
to requested change to Blanket Purchase Order. |
855 or 865
n11 |
ORDRSP |
tbd n9 |
tbd n10 |
| Seller-Initiated
BPO Change |
Seller-requested
changes may be sent to the buyer. |
865 |
ORDRSP |
tbd n9 |
tbd n10 |
| Acceptance
Response to Seller-Initiated Change Request |
Used when buyer
to respond to seller-initiated PO Change Request which accepts
or counter-proposes seller-initiated changes |
860 |
ORDCHG |
tbd n9 |
tbd n10 |
| Denial Response
to Seller-Initiated Change Request |
Used when a
buyer is denying (rejecting) a seller-initiated change. |
860 |
ORDCHG
|
tbd n9
|
tbd n10 |
| Purchase Order
Cancellation |
Used to convey
requested changes to a Purchase Order. Used also for
buyer to respond to seller-initiated PO Change Request which
accepts or counterproposes seller-initiated changes |
860 |
ORDCHG |
3A9 |
Cancel Purchase
Order |
| |
Note
9: PIP3A4 does not satisfy EIDX requirements for Blanket
Order functionality; awaiting release of new PIP3A13 to see
if it satisfies requirements. Unknown if there will be
Blanket Order counterparts for 3A7 and 3A8.
Note 10: Has not been determined if 003_process_po and
related BODs support BPO functionality.
Note 11: Although the X12
standard has a separate response transaction for the 860,
the 865, an 855 may be sent in response to an 860. |
| Business
Documents |
Description |
X12 -
EIDX |
EDIFACT
- EDIFICE (*) |
Rosetta-Net |
OAGIS
8.0 |
| ORD3A
- Release Against Blanket Order Line Item, Buyer-Managed |
| Release Against
Blanket PO |
Buyer generates
discrete, forecast-based release against a blanket Purchase
Order. |
862 or 860 |
DELJIT or ORDCHG |
4D1 |
Sync
Shipment Schedule |
| Response to
Release |
Used to acknowledge
(confirm acceptance or rejection) of a release against a Blanket
Purchas |