I’ve finally had some time to work on the punch-out scenarios. If you’re not familiar with what a punch-out is, it basically is a way for suppliers to give buyers real time catalog information without the hassle of catalog file going back and forth. How real time is that? When a buyer is interested in making a purchase a punch-out session is initiated and the suppliers punch-out site comes up. Your site essentially is the catalog. The end result when the buyer is done shopping, a quote sent back to the buyer for them to be able to turn it into a PO. I’ll tackle the quote, or OrderMessage in cxml speak at a later time. For now here are my punch-out scenarios:
Create punch-out session – like the PO scenarios this is the best one to start with as it is the most common and if this one does not work, there is not much point in going on. With it you want to make sure the site comes up and is shoppable.
Inspect punch-out session – want to make sure that nothing can be edited in the cart. No addition, subtractions, or quantity changes. You also want to make sure that the buyer cannot navigate the site in other ways, like browsing products.
Edit punch-out session – want to make sure that items can be added and removed from the cart and that quantities can be changed. This means the site must be navigable.
Create punch-out session with product specified – this is the same as the first scenario, but instead of a generic landing page, you should be directed to the detail page of the product specified. Part of this should be what happens if a product is specified that does not exist.
Again the important part here is that both you and the trading company can feel confident that the system works for the expected scenarios. Since Ariba does not keep track of these documents it can be even more important. If your trading partner cannot even start the buying process they cannot buy your product. Am I missing anything from these scenarios?