How will the papiNet standard integrate with my current environment?
To use the papiNet XML files, your IT system must have
- capability to send and receive xml files over a telecommunications network
- software to handle information contained in the xml files so that it can be made available in the IT systems implemented to support your business processes
More information about xml can be found here
o https://en.wikipedia.org/wiki/XML
o http://www.w3schools.com/xml/
What do we have to purchase to begin using papiNet?
Using the papiNet schemas for implementaion is free of charge.
To use the papiNet xml files, your IT infrastucture must have
- capability to send and receive xml files over a telecommunication newtork
- Software to handle information contained in the xml files so that it can be made available in the IT systems implemented to support your business processes
More information about xml can be found here
o https://en.wikipedia.org/wiki/XML
o http://www.w3schools.com/xml/
What are the costs implementing, how long does it take to implement?
It is not possible to estimate cost or duration of implementations in general.
Cost and duration depend on what information exchange between IT systems and.or organizations you want to automate using papiNet. Implementation projects vary from exchanging information using one papiNet e-Document to orchestrating an integration solution that requires the exchange of several papiNet e-Documents.
Is there an implementation guideline?
Yes, papiNet has published an implementation guide. It is available for download under Materials->papiNet Tools->Implementation Guide
Which version shall I use?
papiNet advises to use the latest version & build available.
You need to consider if you need the namespace or non-namespace version of the schemas
How long will the current version be supported?
papiNet versions and builds as of 2.31 are backwards compatible, meaning that an xml e-document created using based on an earlier build will comply with the schema of a later build
What methods of communication are supported?
Any communication method can be used to communicate papiNet e-Documents.
Some examples include FTP, AS/2, via a VAN, HTTP and others
How do I ensure that my e-Documents are valid?
To validate that your e-Document is valid you can check it against the papiNet xsd schema definition
Do I need to use the papiNet envelope?
You do not need to use the papiNet Envelope. However, it is recommended that it is always used as this makes it possible to clearly define the technical aspects of communicating the e-Document.
The papiNet Envelope also facilitates sending attachments with the papiNet e-Document.
How do I include an attachment to my e-Document?
Using the papiNet Envelope as part of your solution will facilitate sending attachments with the papiNet e-Document.
How do I know that the receiver has processed my e-Document?
In some cases, papiNet has defined pairs of e-Documents to support this. For example
- PurchaseOrder & OrderConfirmation
In other scenarios, papiNet has defined two e-Documents to facilitate this functionality
- BusinessAcceptance, to enable the receiver to reply with a technical confirmation that the e-Documet has been received
- BusinessAcknowledgement, to enable replying with a confirmation that the e-Document has been received into the receiver's business IT system
Where can I get more information on implementing papiNet?
Documentation of the papiNet e-Documents describe some typical use cases.
PapiNet has also documented use case descriptions for specific business areas.
These can be located on the User Group pages with www.papinet.org
-