Knowledge Base

CGR07-028: Security

tgindrup — Thu, 03 Apr 2008 14:49:38 GMT

The Core Group Recommends that by the end of 2007 all e-PSA transactions will be required to transmitted using RosettaNet security and that the e-PSA deviation from the RosettaNet standards be dropped.

CGR07-027: Increment Schema Version

tgindrup — Thu, 03 Apr 2008 14:48:11 GMT

Move the version of the schema, from the one adopted during the 2006 Core Group P2P meeting (v01.03), to the production version (v01.08) of the Invoice Notification PIP 3C3.

CGR07-025: Cardinality and Certification

tgindrup — Thu, 03 Apr 2008 14:44:18 GMT

As necessary, the ePSA Core Group can modify the cardinality constraints used in ePSA Certification to reduce the requirements on specific fields. This change in cardinality MUST be in conformance with the currently published version of the RosettaNet schema for the give document.

CGR07-024: Schema / DTD Version Control

tgindrup — Thu, 03 Apr 2008 14:38:39 GMT

The only version of the DTD that trading partners are RECOMMENDED to use is the one found on the ePSA-Labs website.

CGR07-023: Comment Field Formatting

tgindrup — Thu, 03 Apr 2008 14:37:23 GMT

No specific formatting of comment fields is recommended because the data contained in the field is outside the scope of the ePSA Standard.

CGR07-022: Global Identifier

tgindrup — Thu, 03 Apr 2008 14:35:55 GMT

Only RosettaNet / ePSA defined terms should be placed in Global fields. Where proprietary / partner specific information (i.e. supplier part numbers) need to be conveyed, the corresponding proprietary or partner specific elements should be used.

CGR07-016: Proprietary Identifier Authority

tgindrup — Thu, 03 Apr 2008 14:33:55 GMT

For trading partners that desire to convey alternative numbering systems as part of the PIP 3A4 Purchase Order suite of transactions, the following Proprietary Identifier Authority values MUST be utilized:· UPIC – means the UPOIC Code· AN – Means an internal account number· ASI – means the ASI code

CGR07-013: Intersection between Ship To Address and Purchase Order Identifier

tgindrup — Thu, 03 Apr 2008 14:31:15 GMT

We recommend that each PIP 3B2 contain a unique intersection between the ship to address and the purchase order identifier. This means there will be one and only one destination address and purchase order number for any given PIP 3B2 document.

CGR07-012: Supplier's Shipping Account Information

tgindrup — Thu, 03 Apr 2008 14:29:50 GMT

We recommend that supplier’s shipping account information not be included in the PIP 3B2 business transaction, but rather be conveyed as part of the trading partner agreement.

CGR07-011: Receiving Partner's Contact Information

tgindrup — Thu, 03 Apr 2008 14:27:47 GMT

It is the consensus of the currently active and participating Core Group members that the Ship To Node contact information should be populated with the shipment destination’s information, with the following exceptions: If the originator of the PIP does not have the destination’s GBI (their DUNS #), this field MUST be populated with the distributor’s GBI (their DUNS #). Additionally, the following elements will have their cardinality modified to be optional Email, Telephone, and GlobalCountryCode. This will necessitate an update to the ePSA Labs Certification Server to test for optional fields.

CGR07-010: Selling Partner's Contact Information

tgindrup — Thu, 03 Apr 2008 14:26:16 GMT

It is the consensus of the currently active and participating Core Group members that the Selling Partner Node contact information should be populated with the supplier’s information. The fields that are contained in the certification document for this PIP are sufficient and adequate to convey information accurately between trading partners.

CGR07-009: Originating Partner's Contact Information

tgindrup — Thu, 03 Apr 2008 14:24:45 GMT

It is the consensus of the currently active and participating Core Group members that the Originating Partner Node contact information should be populated with the supplier’s information. The fields that are contained in the certification document for this PIP are sufficient and adequate to convey information accurately between trading partners.

CGR07-008: Buying Partner's Contact Information

tgindrup — Thu, 03 Apr 2008 14:23:16 GMT

It is the consensus of the currently active and participating Core Group members that the Buying Partner Node contact information should be populated with the distributor’s information. The fields that are contained in the certification document for this PIP are sufficient and adequate to convey information accurately between trading partners.

CGR07-007: Scheduled [Transport] Event - Global Transportation Event Code

tgindrup — Thu, 03 Apr 2008 14:21:43 GMT

It is the recommendation of the ePSA Core Group that the ePSA Business Dictionary for GlobalTransportEventCode be updated as follows:

Dock
Pickup
Ship
Undefined	New term

CGR07-005: Comments

tgindrup — Thu, 03 Apr 2008 14:19:04 GMT

Any additional comments that might help the trading partner understand the status of the order MAY be placed in the comments element at both the Purchase Order level as well as the Line Item level in the XPath location referenced in Section 3.

CGR07-003: Supplier Internal Order Number Location

tgindrup — Thu, 03 Apr 2008 14:17:09 GMT

For suppliers, the supplier internal order reference number associated with the Purchase Order Number is RECOMMENDED to be located at the XPath referenced in Section 3.

CGR07-002: Purchase Order Status Values

tgindrup — Thu, 03 Apr 2008 14:15:14 GMT

Until other PIPs and TPTs (3A5, 3A7, 3A8, 3A9) are adopted and in use by industry firms, the industry terminology status codes are RECOMMENDED to be placed at the line level corresponding to the XPath location referenced in section 3. The industry status codes MUST be selected from the following table:

Industry Line Item Status	Description
In production	Actively being produced
On Hold	General term denoting a stop in the process for any reason
In Proofing	Artwork and Ad-Copy are being proofed
Shipped	Order should move into 3B2 but can overlap if sent the same day

The above list is in addition to the Global Line Item Status Codes as defined by the Message Guideline Reference document for PIP 3A6

CGR07-001: Purchase Order Status Location

tgindrup — Wed, 20 Feb 2008 21:46:12 GMT

How often should a 3A6 be sent

tgindrup — Wed, 20 Jun 2007 20:38:29 GMT

The Distribute Purchase Order Status (PIP 3A6) should be sent according to the following schedule:

If the status can be sent in real time it should be sent in real time. What this means is that if a supplier has the capability to send the order status document as changes in the status occur (i.e. real time) they should do so.
If the status can not be sent in real time, it must be sent at least once a day at a minimum.
Any other schedule is appropriate provided both trading partners agree on the schedule.

The last point provides for as much flexibility as necessary between trading companies.